support for git hosting static pages. #561

New Issue

Open

opened 2023-07-14 02:59:20 +02:00 by vimto · 2 comments

vimto commented

2023-07-14 02:59:20 +02:00

Hello, first of all - thank you!
I prefer to use Disroot services, so instead of Codeberg, the obvious choice is you, but whilst both of you are powered by Forgejo, it seems that only Codeberg have pages (like Github have), is this supported here? if not, that would be amazing! and (whilst not my own intention) would definately make you a top choice for indieweb bloggers to host with. I know that gitea didn't support pages, but Codeberg achieved that via pages-server, whilst I am unsure if Forgejo supports pages, Codeberg continue to use pages-server since changing to Forgejo, perhaps that can help you serve pages like they do!
Once again, thank you!

Hello, first of all - thank you! I prefer to use Disroot services, so instead of Codeberg, the obvious choice is you, but whilst both of you are powered by Forgejo, it seems that only Codeberg have [pages](https://codeberg.page/) (like Github have), is this supported here? if not, that would be amazing! and (whilst not my own intention) would definately make you a top choice for indieweb bloggers to host with. I know that gitea didn't support pages, but Codeberg achieved that via [pages-server](https://codeberg.org/Codeberg/pages-server), whilst I am unsure if Forgejo supports pages, Codeberg continue to use [pages-server](https://codeberg.org/Codeberg/pages-server) since changing to Forgejo, perhaps that can help you serve pages like they do! Once again, thank you!

👍 1

meaz commented

2023-07-14 07:57:09 +02:00

Owner

@muppeth if I get this correctly, that would mean add a CNAME for each user, right?

ccx commented

2023-07-25 21:26:20 +02:00

I don't think CNAME is necessary, just wildcard A/AAAA record should suffice.
But given my experience with Google SafeBrowsing you really want separate second level domain for user HTML/JS content. They don't really care for anything more granular than that and even getting the offending URL from them can be a chore.

I don't think CNAME is necessary, just wildcard A/AAAA record should suffice. But given my experience with Google SafeBrowsing you really want separate second level domain for user HTML/JS content. They don't really care for anything more granular than that and even getting the offending URL from them can be a chore.