Files
start-os/backend
Matt Hill 46222e9352 Feat/marketplace show links (#2105)
* closes #2084, rearranges marketplace show, app show, and donation link for Start9

* use url query param if present when fetching license and instructions

* remove log

* chore: Add some checking

* chore: Update something about validation

* chore: Update to use correct default

Co-authored-by: BluJ <mogulslayer@gmail.com>
2023-03-07 19:09:10 -07:00
..
2023-03-07 19:09:10 -07:00
2023-03-07 19:09:10 -07:00
2022-01-21 20:35:52 -07:00
2022-11-29 09:43:54 -07:00
2022-01-21 20:35:52 -07:00
2022-11-29 09:43:54 -07:00
2022-01-21 20:35:52 -07:00
2022-01-21 20:35:52 -07:00

embassyOS Backend

Structure

The embassyOS backend is broken up into 4 different binaries:

  • embassyd: This is the main workhorse of embassyOS - any new functionality you want will likely go here
  • embassy-init: This is the component responsible for allowing you to set up your device, and handles system initialization on startup
  • embassy-cli: This is a CLI tool that will allow you to issue commands to embassyd and control it similarly to the UI
  • embassy-sdk: This is a CLI tool that aids in building and packaging services you wish to deploy to the Embassy

Finally there is a library embassy that supports all four of these tools.

See here for details.

Building

You can build the entire operating system image using make from the root of the embassyOS project. This will subsequently invoke the build scripts above to actually create the requisite binaries and put them onto the final operating system image.

Questions

If you have questions about how various pieces of the backend system work. Open an issue and tag the following people

  • dr-bonez