1f4b25faee
Added directory cleanup logic to remove ./app/extensions before generating new extension files. This prevents old/stale/removed extensions from remaining in subsequent builds. Changes: - Added fs.rmSync to remove extensions directory if it exists - Cleanup happens at the start of generateExtensionFiles() - Directory is recreated during generation process - Logs cleanup action for visibility This ensures each build starts with a clean slate and only includes currently installed extensions.
Fleetbase Console
⭐️ Overview
The Fleetbase Console, a vital component of the Fleetbase Platform, serves as the graphical user interface that facilitates interaction with all Fleetbase extensions. It's architecturally designed to be lightweight, primarily employing Ember Engines for its operational foundation. Ember Engines, a scalable development paradigm for ambitious web applications, allow the Console to dynamically load and manage extensions, ensuring a streamlined and efficient user experience.
The responsibilities of the Console are kept minimalistic to maintain its performance and agility. The Console's key responsibilities encompass administration management, configuration of organization and user settings, and establishing a robust connection to the Fleetbase extensions repository. In its administrative capacity, it provides an intuitive interface for configuring the Fleetbas instance.
Lastly, the Console plays a pivotal role in connecting to the Fleetbase extensions repository. This provides the flexibility to add, update, or remove extensions as per the organizational needs and preferences, all while ensuring the seamless operation and integrity of the Fleetbase Platform.