Move off k8s onto dokku

[fire]

Context and Problem Statement

What’s the hardest part of promoting vsekai?

What’s the hardest part of communicating updates and stuff?

Describe the proposed option and how it helps to overcome the problem or limitation

We don't update our website because kubernetes is too hard for us.

So my plan is to try running uro in dokku to replace kubernetes.

• Platform as a service dokku https://dokku.com/docs/getting-started/install/docker/
• Postgresql for the database
• Caddy for the web server
• Elixir for the server programming
• Object store https://github.com/V-Sekai-fire/dokku-objectstore-seaweedfs (want to migrate to seaweedfs)
  • Temporary artifacts expiry
• Expose the site https://github.com/andrew-womeldorf/dokku-tailscale
• Uses chroot or cgroups. https://hexdocs.pm/alcove/readme.html to run operating system tasks
• Route the web rest apis

[fire]

Todo: Update manuals with a copy of this. https://github.com/V-Sekai/manuals

[fire]

If we change our mind dokku runs on bare metal, docker, kubernetes, cloud and vagrant.