We need a way to be in more control over the uptime of the forum. As an example, search has been broken for several hours now, and other systems are affected too, and there doesn't appear to be any way to get a hold of @KajMagnus.
Please note, we're happy to keep supporting the platform financially, this is not about cost, but about being in control of uptime.
I have set up a self hosted Ubuntu server now - by the way congrats on making those steps so easy to follow! Great installation experience.
How would we go about migrating the Talkyard-hosted server to our own server? I know this is likely a semi big operation, but this would be important to us to get done to ensure stability.
- CChristian Scheuer @chrscheuer
I'm trying to build the "to-talkyard" node.js, but it seems broken. When running "yarn build" in the "to-talkyard" directory I'm getting all sorts of missing dependencies.
It feels like this hasn't been properly tested on a fresh git repo / fresh installation.- CChristian Scheuer @chrscheuer
Got it building. You need to run "yarn" in the main talkyard directory first.
What I'm not entirely sure about is if the "site-export-json" format is supported by the "to-talkyard" script for importing the data.
Otherwise, I'd appreciate if @KajMagnus could help with the transfer of our data to a self-hosted forum perhaps by making a direct export from the database.
- CChristian Scheuer @chrscheuer
I just noticed there's an
/-/import-site-jsonendpoint. Unfortunately, our exported JSON is approx. 150 MB in size, and it appears we can't send so large payloads to the import-site-json endpoint.- CChristian Scheuer @chrscheuer
Even when modifying the environment variable in the docker-compose.yml to accept large payloads, I'm still receiving
<h1>Bad Request</h1> <p id="detail"> For request 'POST /-/import-site-json?deleteOldSite=true' [Request Entity Too Large] </p>- CChristian Scheuer @chrscheuer
Hm, I may have managed to bump enough limits to make this work, but it's been running for over an hour now so not sure if it's still just busy importing or if it's failing/failed.
- CChristian Scheuer @chrscheuer
Hm it broke down due to lack of memory (I had 8 GB RAM allocated). @KajMagnus I'm hoping you can help do a more raw site import/export with the direct database contents to make this process easier.
- CChristian Scheuer @chrscheuer
A related question: What's the current resources the TY production server uses (vCPU, RAM, disk type/size)? Just so we can make sure to at least provide the same config.
KajMagnus in terms of still supporting TY financially (which we want to do, we want to support your great work here) yet hosting ourselves, please be in touch over email (I sent you an email about the urgent problem earlier).
In reply tochrscheuer⬆:KajMagnus @KajMagnus2022-04-15 06:17:12.900ZI'll help you with this, I'll write more a bit later, probably in a PM, and then even later we / I can post an update here at Ty .io
- CChristian Scheuer @chrscheuer
Thank you so much for all the help!
To anybody else reading this in the future - Magnus helped us doing the full migration and spent hours and hours over a weekend to get everything up and running. Outstanding level of support!
KajMagnus @KajMagnus2022-04-19 06:23:11.015ZThanks :- ) (Now, with some scripts and procedures written for this, the next time someone wants to migrate to self hosted, that'll be simpler. And eventually, some day in the distant future, automatic so one just clicks a button and gets a database & uploads dump, and a how-to readme, in an encrypted
.tar.gz)