Not sure I fully understand the target setup you intend to have. But to enable CORS on the github pages app is only really useful if some code running in another domain would call the REST API of the github pages app, which I am not sure it even has. But I might be misunderstanding here. If CORS is indeed needed, then the app coder (github pages) would need to support responding those pre-flight OPTIONS check queries by the browser.

Yes, it's only jekyll. Not an expert on next.js but I think it also needs a backend right ? If so, you have to create a custom package - https://docs.cloudron.io/packaging/tutorial/

@robi said in SSH Key?: Have you used the same key pair elsewhere? In every one of the multitude of attempts to get this straight, I have generated a set of completely unique and new key-pairs, even rotating between different formats and implementations of the cryptography used by ssh sessions (RSA, PEM, OpenSSH, ECDSA, etc.). Nothing seems to be sticking. @BrutalBirdie said in SSH Key?: I just did a fresh setup and could not reproduce your issue. I thank you for taking your time to try that out and see if you could replicate the problem. I have done a reinstall as well - just to see if I had borked something in the first installation - but I'm still encountering the same issues. I wish that I could spy over your shoulder or something while you perform a working setup, to see where I am going wrong. I have consulted with the docs that you've linked to, and I am still unsure of what the exact cause of the problem is. Anyway, thank you all for the time you have dedicated to this matter. I wish that I could simply mark this problem as SOLVED, but the actual takeaway here - is that I had to implement the HTTP transfer methodology, even though it is less secure and is discouraged as a solution. If I DO MANGE to figure it out, then I will update this thread accordingly so that others are not left wondering about this as well.

@girish Thanks!

Ah, thanks! I’m just getting started with Git/Github, so wasn’t aware of that.

Solved by upgrading macOS git to latest version as suggested here.

@girish ,yes I assume its git pages compatible ,infact the code which I uploaded was taken from github previously ,the website was built using nextjs

@girish unfortunately no. i've sent you an email

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

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