💫 Rebranding to embassyOS (#1851)

* name change to embassyOS

* filename change

* motd ASCII update

* some leftovers
This commit is contained in:
Mariusz Kogen
2022-10-03 20:13:48 +02:00
committed by GitHub
parent 719cd5512c
commit 2000a8f3ed
24 changed files with 52 additions and 52 deletions

View File

@@ -1,4 +1,4 @@
# EmbassyOS Backend
# embassyOS Backend
- Requirements:
- [Install Rust](https://rustup.rs)
@@ -12,9 +12,9 @@
## Structure
The EmbassyOS backend is broken up into 4 different binaries:
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
- 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
@@ -25,7 +25,7 @@ See [here](/backend/Cargo.toml) 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.
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