Allow custom repo name for *.org pages & add design.codeberg.org #51

Merged
hw merged 1 commit from momar/build-deploy-gitea:feature/design-resources into master 2021-03-06 18:41:20 +01:00
Image
Member
No description provided.
Image
Member

How does this work?

How does this work?
Image
Author
Member

It's not as awesome as it sounds, it just allows the mapping of fonts.codeberg.org not just to codeberg-fonts/pages but to Codeberg/Fonts, so we can restructure the Codeberg-internal pages repositories (like pages, get-it-on etc.) a bit, and uses that to expose the Codeberg/Design repo at design.codeberg.org.

It's not as awesome as it sounds, it just allows the mapping of `fonts.codeberg.org` not just to `codeberg-fonts/pages` but to `Codeberg/Fonts`, so we can restructure the Codeberg-internal pages repositories (like pages, get-it-on etc.) a bit, and uses that to expose the `Codeberg/Design` repo at design.codeberg.org.
Image
Member

cool, will move this around asap

cool, will move this around asap
Image
Author
Member

Any update on this? 🙃

Any update on this? 🙃
Image hw merged commit 8c1c45ef81 into master 2021-03-06 18:41:19 +01:00
Image
Member

merged to master, deployed to https://codeberg-test.org

merged to master, deployed to https://codeberg-test.org
Image
Author
Member

Thanks! I'm not a member of the Codeberg org on test, could you migrate the Design repo to the test server?

Thanks! I'm not a member of the Codeberg org on test, could you migrate the Design repo to the test server?
Image
Owner

... or be more generous with the rights on the testing instance, might come in handy from time to time 😉

... or be more generous with the rights on the testing instance, might come in handy from time to time 😉
Image
Member

Thanks! I'm not a member of the Codeberg org on test, could you migrate the Design repo to the test server?

;) now you are

> Thanks! I'm not a member of the Codeberg org on test, could you migrate the Design repo to the test server? ;) now you are
Image
Author
Member

Oh, thank you! 🙃

It is deployed, however I found out that the repo names actually have to be lowercase in $subdomain_repo, and that the page still has the wrong content type (and thus doesn't display) due to #50 / #52.

Do you want to correct the upper-/lowercase typo directly on master or shall I fix it on my branch & create a new PR?

Oh, thank you! 🙃 It is deployed, however I found out that the repo names actually have to be lowercase in `$subdomain_repo`, and that the page still has the wrong content type (and thus doesn't display) due to #50 / #52. Do you want to correct the upper-/lowercase typo directly on master or shall I fix it on my branch & create a new PR?
Image
Author
Member

I have added another commit that fixes said typo, so you can cherry-pick it

I have added another commit that fixes said typo, so you can cherry-pick it
Sign in to join this conversation.
No description provided.