Files
start-os/frontend
Aiden McClelland 6ad9a5952e Feature/multi platform (#1866)
* wip

* wip

* wip

* wip

* wip

* wip

* remove debian dir

* lazy env and git hash

* remove env and git hash on clean

* don't leave project dir

* use docker for native builds

* start9 rust

* correctly mount registry

* remove systemd config

* switch to /usr/bin

* disable sound for now

* wip

* change disk list

* multi-arch images

* multi-arch system images

* default aarch64

* edition 2021

* dynamic wifi interface name

* use wifi interface from config

* bugfixes

* add beep based sound

* wip

* wip

* wip

* separate out raspberry pi specific files

* fixes

* use new initramfs always

* switch journald conf to sed script

* fixes

* fix permissions

* talking about kernel modules not scripts

* fix

* fix

* switch to MBR

* install to /usr/lib

* fixes

* fixes

* fixes

* fixes

* add media config to cfg path

* fixes

* fixes

* fixes

* raspi image fixes

* fix test

* fix workflow

* sync boot partition

* gahhhhh
2022-11-29 09:43:54 -07:00
..
2022-07-21 15:18:44 -06:00
2022-10-03 12:13:48 -06:00

embassyOS Frontend

embassyOS has three user interfaces and a shared library, all written in Ionic/Angular/Typescript using an Angular workspace environment:

  1. ui: the main user interface
  2. setup-wizard: used to facilitate initial setup
  3. diagnostic-ui: used to display certain diagnostic information in the event embassyOS fails to initialize
  4. marketplace: abstracted ui elements to search for, list and display details for packages and their dependencies
  5. shared: contains components, types, and functions shared amongst all of the UIs.

Development Environment Setup

Check your versions

node --version
v16.10.0

npm --version
v8.0.0

Running locally with mocks

  1. Clone the repository
git clone https://github.com/Start9Labs/embassy-os.git
cd embassy-os
git submodule update --init --recursive
cd frontend
npm ci
npm run build:deps
  1. Copy config-sample.json and its contents to a new file config.json.
cp config-sample.json config.json

By default, "useMocks" is set to true. Valid values for "maskAs" are tor and lan.

  1. Start the development server(s)
npm run start:ui
npm run start:setup-wizard
npm run start:diagnostic-ui

Running locally with proxied backend

This section enables you to run a local frontend with a remote backend (eg. hosted on a live Embassy). It assumes you have completed Step 1 and Step 2 in the section above

  1. Set useMocks: false in config.json

  2. Create a proxy configuration file from the sample:

cp proxy.conf-sample.json proxy.conf.json
  1. Change the target address to desired IP address in proxy.conf.json

  2. Start the development server

npm run start:ui:proxy