How aniollidon/palamblock works
Project Type and Purpose
• The project is a full-stack solution focused on a browser extension – “PalamBlock Extension” – that integrates with a backend service. The README links to the Chrome web store and provides installation instructions for Windows (and likely other OS versions via palamOS and palamOS-linux). This indicates that the software not only implements a browser extension for content blocking/control but also provides server-side administration and possibly OS-level integration.
Analyzing the File Structure
• Browser Extension (PalamBlock):
– The “PalamBlock” directory contains typical extension components: manifest.json, background.js, various HTML pages (popup.html, login.html, blocked.html), associated JS scripts, and CSS/image assets.
– This component is responsible for client-side tasks (e.g., communicating with the server, enforcing content filters).
• Server/Backend (palamSRV):
– The “palamSRV” folder resembles a Node.js backend with clearly defined directories for controllers, services, and routes. The controllers (e.g., adminController.js, alumneController.js) and services (e.g., adminService.js, normaService.js) suggest an MVC (Model-View-Controller) or service-oriented architecture.
– Additionally, there are subdirectories for versioned routes (v1) which include admin pages, several HTML/CSS/JS bundles for the admin interface (inside src/v1/admin), and WebSocket endpoints (ws-admin, ws-cast, ws-extention, ws-os). This separation may indicate both RESTful and real-time interactions between the browser extension, admin interface, and other clients.
• OS Integration (palamOS and palamOS-linux):
– These directories suggest that there’s additional code for deeper system integration, likely providing the mechanisms for Windows registration or native integration in different operating systems.
• Other Files:
– A .gitmodules file hints at submodules for external dependencies that could be part of the overall system ecosystem.