💾 Archived View for gerikson.com › gemlog › tek › Running-Molly-Brown.gmi captured on 2022-03-01 at 15:13:24. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
A couple of days ago I learned that the server I used for my gemsite had been updated to address a serious security issues.
Despite my best efforts and help from others, I did not manage to update to the latest version.
I decided to use another server: Molly Brown. Why I had not chosen it before escapes me. There were lots of servers to choose from.
I followed the instructions here:
As I already had a user and home dir for gemini, I modified the config file for my setup, plonked the binary in the right place, gave it the correct permissions and started it to check for errors.
You can either log messages and errors to a file, or to STDOUT: set the target to ‘-’ in that case.
A weird detail is that normal log messages are in the format YYYY-MM-DD, while errors are in the format YYYY/MM/DD. Maybe this is for filtering purposes.
I then modified the included systemd unit file to point to my location, enabled it and started it.
M-B had no problem dealing with the certs I’d already installed, which was a sticking point for gemserv.
I dabbled in CGI earlier but got spooked by not being 100% sure my server was secure. I feel slightly better about M-B so might enable it again.
────────────────────────────────────────────
→ more posts in the ‹tek› category
About this category: “technical stuff”
Copyright © 2018 - 2022 Gustaf Erikson
[This Page Viewed Best In Any Gemini Client]