32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
General overview
|
|
-
|
|
|
|
For the use of the admin console, start with 'npm run start' the UI frontend.
|
|
To see/modify the initial login credentials check the /config/config.json file.
|
|
|
|
WITHOUT SETTING THE CONFIG FILE, THE SERVER WILL NOT WORK AS INTENDED!
|
|
(click on the 'Reset UC' when first configuring the server to bring the
|
|
UC at the initial state)
|
|
|
|
Because the client and CEO apps are dependent on the Central Unit (UC), we strongly
|
|
suggest you to make backup at a regular interval in case of hardware failing you will
|
|
only have to deploy the server with the configurations already existing.
|
|
|
|
Important aspects:
|
|
-
|
|
|
|
- The starting/stopping of the UC is handled by this 'Admin Console'. The server will not
|
|
work if the server which servers as the 'Admin Console' is not running.
|
|
- The main server will run at the port 5000, so make sure to configure your routers to
|
|
enable routing to the server;
|
|
- The client and CEO backup system of their applications will need access at ports 5001 and 5002,
|
|
so also make sure to open those ports as well;
|
|
- If the CEO wants to change the email address linked to the account, his password will be changed
|
|
to a low-risk password, so make sure after any release to specify the account information;
|
|
- Make sure that all the ports configurations are respected to have all the applications work properly
|
|
|
|
Closing thoughts
|
|
-
|
|
|
|
We really hope that you will enjoy our application and for any issues, feel free to contact us at
|
|
'username@ourdomain.com' for troubleshooting and other problems. |