sfb1451/rdm.sfb1451.de
2
0
Fork 1
Code Issues 1 Pull requests 1 Packages Activity Actions

Switch to forgejo deployment #6

New issue
Open
opened 2025-03-07 15:47:18 +00:00 by msz · 4 comments
msz commented 2025-03-07 15:47:18 +00:00
Owner
Copy link

Currently, the website sources are hosted both here and on jugit. The website is published from jugit (gitlab CI job writing to a deploy branch, which is pulled onto INM-7 infra). As part of our migration to Forgejo, it could be a good idea to start publishing from our Forgejo instance.

If I understood our lab meeting discussion correctly, that would involve:

  • add a forgejo workflow like the one for abcd-j -- @msz opened a PR to do this
  • move the repository from the sfb1451 org to the www org (as far as I understood this is not mandatory, but preferred to keep things tidy) - @mih can do this
  • set up things in the background so that the sfb subdomain points to where forgejo puts things -- @mih can make it happen
  • (wishlist) allow me to merge changes into the default branch of the migrated repository (currently trunk) -- @mih can do this
  • (wishlist) add a new hugo image which could be used, and include the version in the name so that it is obvious which version it is; I would personally suggest the community image of the latest base version, which is currently docker://hugomods/hugo:base-0.145.0 -- @mih can do this
    • edit: this is not necessary, a job that runs-on: docker could declare an image to be pulled; however there is no need to do that right now as we are not missing features; psyinf-hugo-site-build currently uses hugomods/hugo:0.131.0

For the time being, I am happy to keep the trunk branch pushed into both clones, so that the old deployment still works. And I build the website locally on 0.145, 0.131 also seems to work, so the new version is not mandatory but would be very nice to have.

Currently, the website sources are hosted both here and on jugit. The website is published from jugit (gitlab CI job writing to a deploy branch, which is pulled onto INM-7 infra). As part of our migration to Forgejo, it could be a good idea to start publishing from our Forgejo instance. If I understood our lab meeting discussion correctly, that would involve: - [x] add a forgejo workflow [like the one for abcd-j](https://hub.psychoinformatics.de/www/www.abcd-j.de/src/branch/main/.forgejo/workflows/deploy.yml) -- @msz opened a PR to do this - [x] move the repository from the sfb1451 org to the www org (as far as I understood this is not mandatory, but preferred to keep things tidy) - @mih can do this - [ ] set up things in the background so that the sfb subdomain points to where forgejo puts things -- @mih can make it happen - [x] (wishlist) allow me to merge changes into the default branch of the migrated repository (currently `trunk`) -- @mih can do this - [ ] (wishlist) add a new hugo image which could be used, and include the version in the name so that it is obvious which version it is; I would personally suggest the community image of the latest base version, which is currently docker://hugomods/hugo:base-0.145.0 -- @mih can do this - edit: this is not necessary, a job that `runs-on: docker` could declare an image to be pulled; however there is no need to do that right now as we are not missing features; psyinf-hugo-site-build currently uses hugomods/hugo:0.131.0 For the time being, I am happy to keep the `trunk` branch pushed into both clones, so that the old deployment still works. And I build the website locally on 0.145, 0.131 also seems to work, so the new version is not mandatory but would be very nice to have.
msz commented 2025-04-28 13:18:29 +00:00
Author
Owner
Copy link

@mih -- I hope you're OK with assigning the issue to you, since most of the tasks are administrative ones which I cannot do. I think now is as good a time time to do this as any other. Please let me know how you would like to proceed.

@mih -- I hope you're OK with assigning the issue to you, since most of the tasks are administrative ones which I cannot do. I think now is as good a time time to do this as any other. Please let me know how you would like to proceed.
mih commented 2025-04-29 13:17:57 +00:00
Owner
Copy link

https://hub.psychoinformatics.de/www/rdm.sfb1451.de is now a pull mirror from which the deployment can be done. It needs the workflow merged.

https://hub.psychoinformatics.de/www/rdm.sfb1451.de is now a pull mirror from which the deployment can be done. It needs the workflow merged.
mih commented 2025-04-29 13:21:46 +00:00
Owner
Copy link

Auto-deployment requirements are in place. Once the workflow is merged and the repo synced to www. A deployment action should succeed. Once that is done, the DNS can be repointed.

Auto-deployment requirements are in place. Once the workflow is merged and the repo synced to `www`. A deployment action should succeed. Once that is done, the DNS can be repointed.
mih removed their assignment 2025-04-29 13:21:57 +00:00
msz commented 2025-07-15 15:42:32 +00:00
Author
Owner
Copy link

@mih wrote in #6 (comment):

Auto-deployment requirements are in place. Once the workflow is merged and the repo synced to www. A deployment action should succeed. Once that is done, the DNS can be repointed.

This did not happen - possibly because Forgejo Actions are not enabled for www. Where should they be enabled - here or there (I think there)? I can not do this in www.

@mih wrote in https://hub.psychoinformatics.de/sfb1451/rdm.sfb1451.de/issues/6#issuecomment-3812: > Auto-deployment requirements are in place. Once the workflow is merged and the repo synced to `www`. A deployment action should succeed. Once that is done, the DNS can be repointed. This did not happen - possibly because Forgejo Actions are not enabled for `www`. Where should they be enabled - here or there (I think there)? I can not do this in `www`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
trunk
june-updates
proof-of-principle-reusable-docs
forgejodeploy
publish
master
catalog-dataset-first
tabby
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
mih
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sfb1451/rdm.sfb1451.de#6
No description provided.