Open JoelProminic opened 1 year ago
Dmytro has the install working with: tell genesis install superhumanportal
TODO:
install
action. I see an update
action, but I need to talk to Dmytro about how this works. This is not critical for Super.Human.Installer, since it should only install once, but it would be convenient for testing or long-term servers.We have the initial implementation working for this with v0.1.4, but I'm going to bump this to the next release to continue working on refinements to this design. This installer is not directly connected to the source code in this project, anyway.
I'm not sure about what version number we are talking about but as I have mention the place where we should retrieve version number is in /javascript/bin/js-release/resources/version.xml
. FYI @dpastov
XML is quite simple:
<?xml version="1.0" encoding="utf-8"?>
<root>
<version>0.1.5-SNAPSHOT</version>
<build>2023-05-05T07:36:55Z</build>
</root>
This xml is being created during every build.
I need to update my agent to build the database to instead create a copy of the database on the Genesis server. No changes are required for this issue on the Super.Human.Portal side, so I'll remove this from the milestone
We would like to setup a Genesis addin to install Super.Human.Portal as a web interface in Super.Human.Installer.
This installation will have two components:
Web Interface
This is available at: https://github.com/Moonshine-IDE/Super.Human.Portal/releases/latest/download/Super.Human.Portal.zip
If you need a version number for the file, I can add it.
It should be installed into
domino/html/Super.Human.Portal
on the server. The zip file will unzip as js-release, which should be placed in this directory.For confirmation/testing, the interface will be available at
/Super.Human.Portal/js-release/index.html
Backend Database
The current plan is to deploy the prepared database to the Genesis server (dm-pni-1). For now, I have placed the files at
/root/Super.Human.Portal
, but let me know if you need them moved.I have a couple options for the files:
Super.Human.Portal-0.0.1.nsf # a file with the version number in the name (Super.Human.Portal-[VERSION].nsf Super.Human.Portal.nsf # a fixed file without the version Super.Human.Portal-version.properties # a Java Properties file with version parameters
For now, the properties file only has a VERSION property: [root@dm-pni-1 Super.Human.Portal]# cat Super.Human.Portal-version.properties VERSION=0.0.1
Note that these files were uploaded manually for now, but I intend to add an agent to generate them.