Hostea
/
july-mvp
3
2
Fork 0
Code Issues 6 Pull Requests Projects Releases Wiki Activity

Operations : static website #23

New Issue
Closed
opened 2022-03-15 05:02:34 +00:00 by realaravinth · 8 comments
realaravinth commented 2022-03-15 05:02:34 +00:00 (Migrated from git.batsense.net)
There is no content yet.
dachary commented 2022-04-08 15:21:45 +00:00
Owner

Implemented pages playbook for Enough and deploy to serve the main branch of https://gitea.hostea.org/Hostea/website (to be switched to the branch that has HTML instead) at https://hostea.org and https://www.hostea.org

The configuration was pushed to the private Enough repository of hostea.org.

Implemented [pages playbook for Enough](https://lab.enough.community/main/infrastructure/-/merge_requests/527) and deploy to serve the main branch of https://gitea.hostea.org/Hostea/website (to be switched to the branch that has HTML instead) at https://hostea.org and https://www.hostea.org The configuration [was pushed to the private Enough repository of hostea.org](https://gitea.hostea.org/Hostea/enough/commit/03b172c703dc4e9383b93ec32510699ca2e75c2b).
🚀 1
dachary added spent time 2022-04-08 15:21:52 +00:00
5h
realaravinth added spent time 2022-04-09 06:11:11 +00:00
1h
realaravinth commented 2022-04-09 06:11:15 +00:00

Tasks accomplished:

  1. Tagged Docker image and preparing for freezing and tagging v0.1.0.
  2. Pages didn't apply branch changes earlier(user deploys master and then switches to pages branch, Pages didn't deploy pages post change). This behavior is now fixed, deployment branch changes are now applied during both initialization and repository udpates.
## Tasks accomplished: 1. [Tagged Docker image and preparing for freezing and tagging v0.1.0.](https://gitea.hostea.org/Hostea/pages/commit/609373786c749f94dded7534ff94ca5abbb2a2f6) 2. Pages didn't apply branch changes earlier(user deploys `master` and then switches to `pages` branch, Pages didn't deploy `pages` post change). [This behavior is now fixed, deployment branch changes are now applied during both initialization and repository udpates.](https://gitea.hostea.org/Hostea/pages/commit/325d110e9a33d88e83af95191c75b67a3dad4eb3)
realaravinth added spent time 2022-04-09 14:09:33 +00:00
4h
realaravinth commented 2022-04-09 14:14:29 +00:00

Tasks accomplished

  • Scripts to build and commit to user-provided branch(pages in our case)
  • Scripts to call Pages webhook to pull changes from repository
  • Tried setting up CI for auto-deploy, but it is more complex task than I thought:
    GitHub CI has write access to repositories through auto-injected secrets. So users are able to commit and push to repositories from within the CI environment. In order for pages to deploy files from the repository, Woodpecker will have to be configured to commit and push to Gitea, while avoiding circular CI triggers(Woodpecker push shouldn't trigger another CI run).

    See CI failure build logs.
## Tasks accomplished - Scripts to build and commit to user-provided branch(`pages` in our case) - Scripts to call Pages webhook to pull changes from repository - Tried setting up CI for auto-deploy, but it is more complex task than I thought: GitHub CI has write access to repositories through auto-injected secrets. So users are able to commit and push to repositories from within the CI environment. In order for pages to deploy files from the repository, Woodpecker will have to be configured to commit and push to Gitea, while avoiding circular CI triggers(Woodpecker push shouldn't trigger another CI run).<br /> See [CI failure build logs](https://woodpecker.hostea.org/Hostea/website/build/8/3).
👍 1
realaravinth commented 2022-04-09 14:21:17 +00:00

This setup is too complex and tedious to pass on to the user, will have to create a Woodpecker plugin to abstract the process.

This setup is too complex and tedious to pass on to the user, will have to create a Woodpecker plugin to abstract the process.
dachary commented 2022-04-09 14:21:31 +00:00
Owner

I think to remember you can restrict woodpecker jobs to push events on particular branches. So if you push to another branch it does not keep going.

I think to remember you can restrict woodpecker jobs to push events on particular branches. So if you push to another branch it does not keep going.
realaravinth commented 2022-04-09 14:23:34 +00:00

I think to remember you can restrict woodpecker jobs to push events on particular branches. So if you push to another branch it does not keep going.

True, but it is something that doesn't happen by default. From UX perspective, I think we should provide default gaurds against pages triggering CI.

> I think to remember you can restrict woodpecker jobs to push events on particular branches. So if you push to another branch it does not keep going. True, but it is something that doesn't happen by default. From UX perspective, I think we should provide default gaurds against `pages` triggering CI.
👍 1
dachary commented 2022-04-09 14:29:24 +00:00
Owner

For my own education I read the adding secret documentation and saw you added one for the CI of website.

image

For my own education I read the [adding secret documentation](https://woodpecker-ci.org/docs/usage/secrets#adding-secrets) and saw you [added one](https://woodpecker.hostea.org/Hostea/website/settings#secrets) for the CI of [website](https://gitea.hostea.org/Hostea/website). ![image](/attachments/cee1c4dd-6fd3-4555-9ce0-297d709c7d7e)
image.png
40 KiB
👍 1
dachary added spent time 2022-04-09 14:30:18 +00:00
15min
dachary commented 2022-05-16 11:49:15 +00:00
Owner

Complete and working as intended.

Complete and working as intended.
🚀 1
dachary changed title from Operations : website to Operations : static website 2022-05-16 11:52:20 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels   
User Research

User Research   
backend

devops / backend   
billing
   
frontend

frontend / website   
gitpad
   
operations
   
post-mvp

was unable to implement during mvp time period, but needs to be implemented after MVP deadline   
priority-1

Highest priority   
priority-2

Second from top priority level   
priority-3

Lowest priority   
shared hosting
No Label
User Research
backend
billing
frontend
gitpad
operations
post-mvp
priority-1
priority-2
priority-3
shared hosting
Milestone
Clear milestone
No items
No Milestone
MVP
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Total Time Spent: 10 hours 15 minutes
dachary
5 hours 15 minutes
realaravinth
5 hours
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: Hostea/july-mvp#23
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?