Files
start-os/backend
BluJ 9366dbb96e wip: Starting down the bind for the effects
todo: complete a ip todo

chore: Fix the result type on something

todo: Address returning

chore: JS with callbacks

chore: Add in the chown and permissions

chore: Add in the binds and unbinds in
2023-07-06 15:07:53 -06:00
..
2023-03-08 19:30:46 -07:00
2022-01-21 20:35:52 -07:00
2023-06-28 13:37:26 -06:00
2023-07-06 15:07:53 -06:00
2023-06-11 15:04:59 -06:00
2022-01-21 20:35:52 -07:00
2023-05-11 16:48:52 -06:00
2022-01-21 20:35:52 -07:00
2023-03-08 19:30:46 -07:00
2022-01-21 20:35:52 -07:00

StartOS Backend

Structure

The StartOS backend is broken up into 4 different binaries:

  • embassyd: This is the main workhorse of StartOS - 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 StartOS

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 StartOS 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