1
0
This commit is contained in:
2025-06-17 10:49:47 +00:00
parent 725b2b5669
commit fe2fda7804

View File

@ -16,7 +16,7 @@
</div>
<center><p>On Solving All Of The Problems At The Same Time</p></center>
<p>I fixed the clinical issue with <a href="https://github.com/ergochat/ergo">Ergo</a> the exact way you're supposed to, by being lucky! I made a backup of Ergo, got a copy of Ergo 2.16.0 - the latest version, of which I had an earlier experimental version. I simply copied over my configuration & database and magically the issue was fixed and the database was recovered from the abyss of "who the hell knows" to a mainline release. Automation of upgrades is technically done on the server, but not for Ergo as it's not in any release and the database format could change at any time meaning upgrading is more involved than downloading the package and restarting the daemon.</p>
<p>I had to fix one issue with Ergo, it lacked the proper certs for a new domain it was supposed to be on. Egor on the IRC told me the proper fix faster than I could read the manual and it was solved as follows. I'm not a fan of YAML, but this wasn't unpleasant past not being my expectation.</p>
<p>I had to fix one issue with Ergo, it lacked the proper certs for a new domain it was supposed to be on. Egor on the IRC told me the proper fix faster than I could read the manual and it was solved as follows. I'm not a fan of <a href="https://www.google.com/search?q=satan">YAML</a>, but this wasn't unpleasant past not being my expectation.</p>
<code>
server:
name: xolatile.top