Conversation

Notices

1. Embed this notice
   Truxnell (truxnell@fedi.voltaicforge.com)'s status on Friday, 27-Jan-2023 06:51:22 JST Truxnell

   • Alex Gleason
   @alex I'm running rebased/soapbox in my homelab k8s cluster like a madman - just wondering your stance on your docker containers in gitlab?
   Feels like the community instructions/focus is on a traditional install and I wasn't sure if there was much focus/interest on the dockers you have in the repo, or if they were even more for dev testing over usage.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Friday, 27-Jan-2023 06:51:20 JST Alex Gleason

     in reply to

     @truxnell One of the goals for Q1 is new website and documentation, and we’ll definitely have a section for Docker.

     The reason the source install is the focus is because Soapbox is mostly run by large communities who need the ability to hotfix code in a VM and easily pull code from external branches, etc. As it gets more adoption by single-user instances and self-hosters, Docker is increasingly important.

   • Embed this notice
     ?? أحمد ?? (ahmad@bassam.social)'s status on Friday, 27-Jan-2023 07:06:28 JST ?? أحمد ??

     in reply to

     • Alex Gleason
     Hopefully the installing from source will stay available as the main method. Docker is easy but it's hard to keep up with and it get catastrophic over time if not configured precisely to not remove all of your data on restart. Moving Docker to a new host can be a thing that you really don't want to do.
     Source code is just perfect.
     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Friday, 27-Jan-2023 07:06:51 JST Alex Gleason

     in reply to

     • ?? أحمد ??

     @ahmad @truxnell They are both legitimate and supported ways, depending on your needs and what you’re trying to do.

   • Embed this notice
     Truxnell (truxnell@fedi.voltaicforge.com)'s status on Friday, 27-Jan-2023 07:31:55 JST Truxnell

     in reply to

     • Alex Gleason
     • ?? أحمد ??
     100% agree, Id never want a project to stop supporting a 'from source' install (and also agree it should be the first supported approach). I've used Docker for years at home selfhosting but Id never want any project to ONLY support docker, its just one approach with its own set of pros/cons.
     Alex Gleason likes this.
   • Embed this notice
     Truxnell (truxnell@fedi.voltaicforge.com)'s status on Friday, 27-Jan-2023 07:32:30 JST Truxnell

     in reply to

     • Alex Gleason
     Awesome. I understand single-user instances aren't the primary focus - but upgraded docs for docker will be great. I think I've figured it out by reading the docker code & fiddling a bit, but my currently soapbox install is just unzipped in the container which isn't perfect from a upgrading/robustness point of view
     
     I assume the best practise would be
     * run 1 instance of rebased stricly as an api backed with a DB
     * run 1-x instances of soapbox pointed to the API container depending on traffic/High Availability desires. (with the usual load balancer/ingress in front of them)
     This would allow me to review/merge upgrade PR's as new docker tags become available independently for both streams and avoids (most) downtime when updating
     Alex Gleason likes this.