Files
start-os/backend
J M 35b220d7a5 Feat/long running (#1676)
* feat: Start the long running container

* feat: Long running docker, running, stoping, and uninstalling

* feat: Just make the folders that we would like to mount.

* fix: Uninstall not working

* chore: remove some logging

* feat: Smarter cleanup

* feat: Wait for start

* wip: Need to kill

* chore: Remove the bad tracing

* feat: Stopping the long running processes without killing the long
running

* Mino Feat: Change the Manifest To have a new type (#1736)

* Add build-essential to README.md (#1716)

Update README.md

* write image to sparse-aware archive format (#1709)

* fix: Add modification to the max_user_watches (#1695)

* fix: Add modification to the max_user_watches

* chore: Move to initialization

* [Feat] follow logs (#1714)

* tail logs

* add cli

* add FE

* abstract http to shared

* batch new logs

* file download for logs

* fix modal error when no config

Co-authored-by: Chris Guida <chrisguida@users.noreply.github.com>
Co-authored-by: Aiden McClelland <me@drbonez.dev>
Co-authored-by: Matt Hill <matthewonthemoon@gmail.com>
Co-authored-by: BluJ <mogulslayer@gmail.com>

* Update README.md (#1728)

* fix build for patch-db client for consistency (#1722)

* fix cli install (#1720)

* highlight instructions if not viewed (#1731)

* wip:

* [ ] Fix the build (dependencies:634 map for option)

* fix: Cargo build

* fix: Long running wasn't starting

* fix: uninstall works

Co-authored-by: Chris Guida <chrisguida@users.noreply.github.com>
Co-authored-by: Aiden McClelland <3732071+dr-bonez@users.noreply.github.com>
Co-authored-by: Aiden McClelland <me@drbonez.dev>
Co-authored-by: Matt Hill <matthewonthemoon@gmail.com>
Co-authored-by: Lucy C <12953208+elvece@users.noreply.github.com>
Co-authored-by: Matt Hill <MattDHill@users.noreply.github.com>

* chore: Fix a dbg!

* chore: Make the commands of the docker-inject do inject instead of exec

* chore: Fix compile mistake

* chore: Change to use simpler

Co-authored-by: Chris Guida <chrisguida@users.noreply.github.com>
Co-authored-by: Aiden McClelland <3732071+dr-bonez@users.noreply.github.com>
Co-authored-by: Aiden McClelland <me@drbonez.dev>
Co-authored-by: Matt Hill <matthewonthemoon@gmail.com>
Co-authored-by: Lucy C <12953208+elvece@users.noreply.github.com>
Co-authored-by: Matt Hill <MattDHill@users.noreply.github.com>
2022-11-29 09:43:54 -07:00
..
2022-09-01 10:32:01 -06:00
2022-11-29 09:43:54 -07:00
2022-01-21 20:35:52 -07:00
2022-10-11 12:15:42 -06:00
2022-10-11 12:15:42 -06:00
2022-01-21 20:35:52 -07:00
2022-10-03 12:13:48 -06:00
2022-01-21 20:35:52 -07:00
2022-09-01 10:32:01 -06:00
2022-01-21 20:35:52 -07:00

embassyOS Backend

  • Requirements:
  • Scripts (run withing the ./backend directory)
    • build-prod.sh - compiles a release build of the artifacts for running on ARM64
    • build-dev.sh - compiles a development build of the artifacts for running on ARM64
  • A Linux computer or VM

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
  • ProofOfKeags