Futureporn February 2024 Sprint #97

New Issue

CJ_Clippy · 2024-01-11T12:00:08Z

CJ_Clippy commented

2024-01-11 12:00:08 +00:00

Refactor dev env for docker compose
Fix vod player's fullscreen button
Multiple vtubers
Uploads
automation -- uploads moderation flow
automation -- identify & fix vod issues
Fix pager button on https://futureporn.net/latest-vods/1
Feb 2024 Deployment changes

* [x] Refactor dev env for docker compose * [x] Fix vod player's fullscreen button * [x] Multiple vtubers * [x] Uploads * [ ] automation -- uploads moderation flow * [ ] automation -- identify & fix vod issues * [x] Fix pager button on https://futureporn.net/latest-vods/1 * [x] [Feb 2024 Deployment changes](https://gitea.futureporn.net/futureporn/pm/issues/105)

CJ_Clippy added the

Sprint

label 2024-01-11 12:00:08 +00:00

CJ_Clippy self-assigned this 2024-01-11 12:06:09 +00:00

CJ_Clippy pinned this 2024-01-11 12:06:14 +00:00

CJ_Clippy changed title from ~~Futureporn January 2024 Sprint~~ to Futureporn February 2024 Sprint

2024-01-25 05:47:13 +00:00

CJ_Clippy added the due date 2024-02-15

2024-01-25 05:47:25 +00:00

CJ_Clippy commented

2024-02-26 20:06:07 +00:00

Deployment changes are cancelled because Kubernetes is adding too much complexity for me handle right now.

CJ_Clippy commented

2024-02-27 19:47:19 +00:00

Today I improved the packages/next Docker build for dokku deployment. Encountered a blocker-- environment variables aren't passed to the docker container as it builds on the remote. Investigating a way to work around

CJ_Clippy commented

2024-03-05 03:59:51 +00:00

Deployment changes are un-cancelled because I think it's the best way forward at this moment. "Keep Calm and Devops On"

Mainly the thing pushing me forward is some shortcomings in dokku. dokku lacks configurations as code. dokku's app secrets are individually handled on the remote host which requires SSH-ing in and setting environment variables. This is an ad-hoc operation which isn't a good practice when it comes to large scale applications.

For comparison, secrets in kubernetes are set on the operator's computer, and then the secret variable names are referenced in yaml configuration files and kubectl(?) takes care of deploying the secret to the pod.

This is the "livestock, not pets" argument which is a cornerstone of systems that scale.

Dokku doesn't scale beyond one remote host, either. Futureporn must scale! I must say goodbye to dokku and endure the pain of learning a new way of doing things.

Deployment changes are un-cancelled because I think it's the best way forward at this moment. "Keep Calm and Devops On" Mainly the thing pushing me forward is some shortcomings in dokku. dokku lacks configurations as code. dokku's app secrets are individually handled on the remote host which requires SSH-ing in and setting environment variables. This is an ad-hoc operation which isn't a good practice when it comes to large scale applications. For comparison, secrets in kubernetes are set on the operator's computer, and then the secret variable names are referenced in yaml configuration files and kubectl(?) takes care of deploying the secret to the pod. This is the "livestock, not pets" argument which is a cornerstone of systems that scale. Dokku doesn't scale beyond one remote host, either. Futureporn must scale! I must say goodbye to dokku and endure the pain of learning a new way of doing things.

CJ_Clippy closed this issue

2024-04-16 14:37:45 +00:00

CJ_Clippy unpinned this 2024-04-16 14:37:51 +00:00

Sign in to join this conversation.