admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-11-30 21:38:24 +00:00
parent 3db34d1a9e
commit d1fea2dd7e
1 changed files with 14 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
ayanova/devdocs/todo.txt
View File

@@ -185,6 +185,7 @@ User types and complexity:
Shared power users with external access Shared power users with external access
Zip file install for power users, archive with manual guidance Zip file install for power users, archive with manual guidance
need to figure out how to support certs in ayanova etc as nginx is shit on windows need to figure out how to support certs in ayanova etc as nginx is shit on windows
this is IIS territory I think as it supports and is supported
Linux direct to the docker solution initially, later can see about a tar archive and bare metal running it Linux direct to the docker solution initially, later can see about a tar archive and bare metal running it
@@ -208,25 +209,23 @@ With launcher, inno only needs to drop files and put desktop icon
WHERE ITS AT: WHERE ITS AT:
Outstanding: Everything starts and runs, actually working! Opens three windows though and so it's not ideal.
More ideal would be a single launcher window that controls all and starts aya and pg inside it's own window / hidden which means not usnig shell execute I guess?
Start postgres not working yet..... see command line window
launch browser to AyaNova folder
Issues:
closing server doesn't close pg, need to issue pgctl stop I guess
not yet launch browser to AyaNova folder
closing launcher closes all closing launcher closes all
Should server be hidden or redirect to launcher it's stdio? Once this is all working, is there a way to then hide it all inside the launcher with redirect and stuff??
Can everything redirect to launcher and just hide them fully?
SINGLE USER STANDALONE ("dummy" / beta testers version)
- configure command line options (in installer) Not intended for reconfiguration, just a standalone way to get up and running immediately
- re-configure / view command line options after install Can be used on a lan, not intended for outside access
- check for postgres server / select exsting postgres server
- Install standalone postgres server
SINGLE USER STANDALONE (beta testers version)
Contains everything needed to run, launches with a desktop icon that starts sql then ayanova, then launches a browser to connect Contains everything needed to run, launches with a desktop icon that starts sql then ayanova, then launches a browser to connect
Can modify the settings or leave as default Can modify the settings or leave as default
requires launcher program requires launcher program
@@ -237,8 +236,8 @@ Contains only AyaNova server itself, requires separate install of postgres
prompts for postgres server location if it doesn't find it then won't install (or at least says crucial error) prompts for postgres server location if it doesn't find it then won't install (or at least says crucial error)
EXTERNALLY ACCESSIBLE EXTERNALLY ACCESSIBLE
Not directly accessible, needs nginx Not directly accessible, needs or IIS??
maybe it's a pre-requisite or maybe the lan install is the same one as this one but user needs nginx to connect remotely (IIS is well documented way to host a .net core app then it's like nginx and handles certs etc)