Switching over to a static build #64

Open
opened 2023-03-28 08:33:10 +00:00 by decentral1se · 2 comments
Owner

This would give us the advantage that if the CI/CD is passing then we know all the scripts work instead of them silently failing in the docker environment. We'll also have linkable logs instead of stuff in our terminals only accessible via abra.

In order to retain regular update, we can schedule a cron in the Drone UI to re-run the CI/CD.

If we can make this work then the site won't keep flapping because there will be no dev hugo server running, just nginx hosting some files that are periodically updated in the background via CI. This will quiet the noisy monitoring notifications we get on autonomic side as well due to small site updates.

- Convert https://git.autonomic.zone/ruangrupa/lumbung.space/src/branch/main/compose.yml to only use Nginx and expose a volume where we can transfer the required static files to - Convert https://git.autonomic.zone/ruangrupa/lumbung.space/src/branch/main/.drone.yml to build the site and run scripts and then copy the files over to the Nginx volume This would give us the advantage that if the CI/CD is passing then we know all the scripts work instead of them silently failing in the docker environment. We'll also have linkable logs instead of stuff in our terminals only accessible via `abra`. In order to retain regular update, we can schedule a cron in the Drone UI to re-run the CI/CD. If we can make this work then the site won't keep flapping because there will be no dev hugo server running, just nginx hosting some files that are periodically updated in the background via CI. This will quiet the noisy monitoring notifications we get on autonomic side as well due to small site updates.
Owner

moving away from the development server is always a good idea. Do we have budget for this? If so I say a big yes!

moving away from the development server is always a good idea. Do we have budget for this? If so I say a big yes!
Author
Owner

Update: we had a meet to work on this. We kind of came to the conclusion that we shouldn't touch it right now. It is a complicated deployment but also it satisfies this "git push and deploy" approach for others hacking on the site which has reduced barriers to getting things live. This has its drawbacks ofc (live stack traces) but for now, maybe this is fine. It is stable. When Kotec gets onboarded, maybe there willl be a change in direction but that is up to them.

Update: we had a meet to work on this. We kind of came to the conclusion that we shouldn't touch it right now. It is a complicated deployment but also it satisfies this "git push and deploy" approach for others hacking on the site which has reduced barriers to getting things live. This has its drawbacks ofc (live stack traces) but for now, maybe this is fine. It is stable. When Kotec gets onboarded, maybe there willl be a change in direction but that is up to them.
Sign in to join this conversation.
No Milestone
No project
No Assignees
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: ruangrupa/lumbung.space#64
No description provided.