This commit is contained in:
@@ -185,46 +185,63 @@ Install types:
|
||||
|
||||
TODO: NEXT:
|
||||
|
||||
|
||||
Test a clean server install and be *certain* NOT to start AyaNova in shell, do it all as a service so that we are certain all the reqs and permissions are good
|
||||
(i.e. running it manually and rendering triggers dl of chromium as root which is not a proper test)
|
||||
May need to create *all* the folders up front and grant permissions first before first run
|
||||
|
||||
## LINUX INSTALL
|
||||
|
||||
TODO: Maybe just install chromium in order to get the reqs *then* attempt to print, try with clean server again
|
||||
Server service definition file
|
||||
sudo nano /etc/systemd/system/ayanova.service
|
||||
|
||||
sudo apt-get install chromium-browser
|
||||
|
||||
-----
|
||||
[Unit]
|
||||
Description=AyaNova server
|
||||
|
||||
[Service]
|
||||
WorkingDirectory=/var/ayanova
|
||||
ExecStart=/usr/bin/dotnet /var/ayanova/AyaNova.dll
|
||||
Restart=always
|
||||
# Restart service after 10 seconds if the dotnet service crashes:
|
||||
RestartSec=10
|
||||
KillSignal=SIGINT
|
||||
SyslogIdentifier=ayanova-server
|
||||
User=www-data
|
||||
Environment=ASPNETCORE_ENVIRONMENT=Production
|
||||
Environment=DOTNET_PRINT_TELEMETRY_MESSAGE=false
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
-----
|
||||
|
||||
sudo systemctl enable ayanova.service
|
||||
sudo systemctl start ayanova.service
|
||||
sudo systemctl status ayanova.service
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
CHROMIUM Error:
|
||||
ldd ./var/ayanova/.local-chromium/Linux-884014/chrome-linux/chrome | grep not
|
||||
install the chromium reqs:
|
||||
|
||||
test@devtest:/var/ayanova$ ldd ./.local-chromium/Linux-884014/chrome-linux/chrome | grep not
|
||||
libatk-1.0.so.0 => not found
|
||||
libatk-bridge-2.0.so.0 => not found
|
||||
libcups.so.2 => not found
|
||||
libxkbcommon.so.0 => not found
|
||||
sudo apt-get install -yq gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 \
|
||||
libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 \
|
||||
libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 \
|
||||
libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 libgbm1 \
|
||||
ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
|
||||
|
||||
libXcomposite.so.1 => not found
|
||||
libXdamage.so.1 => not found
|
||||
libXfixes.so.3 => not found
|
||||
libXrandr.so.2 => not found
|
||||
libgbm.so.1 => not found
|
||||
libpango-1.0.so.0 => not found
|
||||
libcairo.so.2 => not found
|
||||
libatspi.so.0 => not found
|
||||
libxshmfence.so.1 => not found
|
||||
If this works, do it *before* run ayanova and auto dl chromium should be tested and put in that order
|
||||
|
||||
|
||||
Rights issues, running as www-data user/group
|
||||
Needs writeable to data folder so change ownership from root to www-data:
|
||||
sudo chown -vR :www-data /var/ayanova/data
|
||||
Add read write rights to all folders in /var/ayanova/data to group owners
|
||||
sudo chmod -R g+rw /var/ayanova/data
|
||||
|
||||
|
||||
libXcomposite.so.1 => not found
|
||||
libXdamage.so.1 => not found
|
||||
libXfixes.so.3 => not found
|
||||
libXrandr.so.2 => not found
|
||||
libgbm.so.1 => not found
|
||||
libpango-1.0.so.0 => not found
|
||||
libcairo.so.2 => not found
|
||||
libxshmfence.so.1 => not found
|
||||
|
||||
|
||||
## DOCS
|
||||
@@ -521,11 +538,16 @@ todo: 3 Schedule form reporting?
|
||||
|_____/|______|_| \_\ \/ |______|_| \_\
|
||||
|
||||
|
||||
todo: 1 When there is a rendering issue with chromium browser startup the server *must* log that to the server log, right now it just half-ass reports it back to the client only
|
||||
this is because it was written expecting any error was a template error not a starting chromium error so need to look there in the exception handler
|
||||
would rather not log report template issues to the server log but anything else structural should be
|
||||
|
||||
todo: 1 Test with expired key, can superuser login and no one else?? **CRITICAL**
|
||||
Awaiting a raven license key generator first, currently do not have one, 404's in rockfish!!
|
||||
|
||||
|
||||
todo: 1 investigate: noticed when rebooting linux server I need to login again which I didn't expect, it should still work as long as the token is unchanged
|
||||
is this due to randomization of jwt secret or something?
|
||||
try in windows and confirm
|
||||
|
||||
todo:1.5 Joyce case 3931 test restore of 4alarm data
|
||||
actually, try it here first with small amount of data then try the huge one
|
||||
|
||||
Reference in New Issue
Block a user