Skip to content

Latest commit

 

History

History
23 lines (17 loc) · 1.13 KB

directory_structure.md

File metadata and controls

23 lines (17 loc) · 1.13 KB
Raw

Directory Structures

PlaceOS Core and PlaceOS Driver Spec Runner make the assumption that the working directory is one level up from the drivers directory.

An example deployment structure:

  • Working directory: /home/placeos/core
  • Executable: /home/placeos/core/bin/core
  • Driver repositories: /home/placeos/repositories
    • PlaceOS Drivers: /home/placeos/repositories/drivers
  • Driver executables: /home/placeos/core/bin/drivers
    • Samsung driver: /home/placeos/core/bin/drivers/353b53_samsung_display_md_series_cr

However when developing the structure will look more like:

  • Working directory: /home/placeos/drivers
  • Driver repository: /home/placeos/drivers
  • Driver executables: /home/placeos/drivers/bin/drivers
    • Samsung driver: /home/placeos/core/bin/drivers/353b53_samsung_display_md_series_cr

The primary difference between production and development is PlaceOS Core. In a production environment, PlaceOS Core handles cloning repositories, installing packages, and building Drivers as required.