@girish I created a 404.html both in the file manager and in the git repo---nothing.
@robi checked I took a look in the file manager & terminal and there were no clues as to why the repo was there but the files were not
I did find a workable solution: I ended up cloning the repo into /app/data/ and then renaming the directory to 'website' and now it's live again.
I seem to have to pull manually from the app's terminal though, and can't just push to the 'page' remote from my local machine. Is there a git command I can use in the /app/data/website directory to have it stay synced to the 'page' remote like the cloudron app should be doing anyway?
@girish Thanks for the sanity check. There does seem to have been something wrong with my jekyll site creation. Trying again, it works as advertised...!? I can see a remote: => jekyll build line in the git-push output.
IIRC I did attempt this more than once earlier, and I'm not sure what was wrong.
Anyway, hopefully this thread may nevertheless be helpful for someone else getting started on this.
We might indeed try use such a CDN if it turns out to be needed (probably not cloudflare, to not centralise the web too much). Ideally people would all just get our site via peer-to-peer delivery instead.
Totally agreed. We self-host pretty much everything (other than the servers itself). Though I suggested Cloudflare, I was really nudging you towards maybe using a CDN since CDN has it's use cases. People have suggested BunnyCDN as well. That said, we don't use CDN ourselves, even for https://cloudron.io and https://docs.cloudron.io. It's served from surfer. This is mostly for ideological reasons, we are willing to give up on some speed and not centralize (we used to have it on AWS Cloudfront before).