@jordanurbs @girish fixed, had to run

git config --global http.version HTTP/1.1

and then switch back

@gerben thanks, I have tried to fix it in the latest release.

Yeah I've often found the GitHub Pages app clunky and hard to use. Add in the features of Surfer and I really don't see a need to have GitHub Pages on here. But yeah check out Surfer for sure.

@gerben said in Performance:

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).

@girish Ohh, I didn't know that.. it looks so official, logo and all.. I found it weird as it's not quite fully self-hosting..

can we make it work with GitLab/Gitea/Gogs?

@girish said in SSH Key?:

I think we just implemented it that way for initial prototyping.

Makes sense!

@girish It worked! Need to change some of the jekyll code around to transition from github to this, but looks good!

@girish Works, thanks you!

@will If you already have a basic site setup (using HTML) just push that to the ghpages app, no need for jekyll.

Otherwise see https://cloudron.io/documentation/apps/githubpages/

If you want, maybe easier - You can upload static HTML to the LAMP app too. under the /app/data/public folder.

@yusf That query for credentials each time can get annoying very quickly.. For now, you can setup this netrc file. Please see https://cloudron.io/documentation/apps/githubpages/#publishing-pages . Coming release, we are looking into ssh based push that will bypass this non-stop password querying.

Thanks, that resolved my issue.