That worked like a breeze.
When I ran the AppImage, once it was done, it didn't go back to a prompt. It wasn't clear that it had finished installing and executing. As soon as I connected to 127.0.0.1, it came right up in Chromium, and I saw that an update from citserver in the terminal window. I never got any configuration input. It just ran the script and brought the Citadel up... so, no option to select ports or create the initial admin.
I'm not sure if I'm describing it clearly. It wasn't apparent to me that the script had finished and it was returning logging to me in the terminal session.
If I hit ctrl-C in the terminal window, it reloads, too...
Another Ctrl-C and it seemed like it was shutting down, and now when I try to open the browser, the service can't be reached.
Is that expected behavior now? Do you run AppImage in a terminal every time to bring it up? Going to try to reboot the Pi right now to see if it autolaunches after install.
All righty then! It's time for round 2 of testing the Citadel appimage.
64-bit x86: https://easyinstall.citadel.org/Citadel-x86_64.AppImage
32-bit ARM: https://easyinstall.citadel.org/Citadel-armhf.AppImage
(A note on the ARM build: the Raspberry Pi OS is 32-bit, even on 64-bit hardware.
If anyone is running 64-bit Ubuntu, go ahead and try it, let me know how it works.)
Once again, the installation process is as follows:
1. Download the x86-64 or ARM image
2. mkdir /usr/local/citadel
(or make a copy of your existing database, if it's on the same CPU type as your test machine)
3. Make the appimage executable, and run it.
WebCit ought to be working properly this time, HTTP on port 80 and HTTPS on port 443. All of the other services will come up on their default ports., and as always, you can change or disable them at runtime.
Once we go through a few rounds of testing, I will be adding all the typical bells and whistles, such as setup and diagnostic tools, the ability to run with any data directory, etc. Looking forward to hearing your test results.
