Post AY1LRnrPr3O0z7GdbU by snikket_im@fosstodon.org
 (DIR) More posts by snikket_im@fosstodon.org
 (DIR) Post #AY1LOkJAbcgz6An7U8 by tony@toot.hoyle.me.uk
       2023-07-24T12:49:22Z
       
       1 likes, 1 repeats
       
       @neil @dino @snikket_im Looks good.. night take a look.Ugh.. Docker.
       
 (DIR) Post #AY1LQR4F768o0HcBIO by snikket_im@fosstodon.org
       2023-07-24T13:21:05Z
       
       1 likes, 1 repeats
       
       @neil You don't need to do anything - everything Snikket needs to chug along happily is alread set up for you inside the container (this is why we use docker: https://snikket.org/faq/#q-can-i-set-up-snikket-without-docker ).If anything does go wrong, we have a helpful community support chat: https://snikket.org/contact/And if you're the kind of person that simply needs to use OS packages and set up cron jobs, our sister project @prosodyim has you covered 🙂@tony
       
 (DIR) Post #AY1LRGYTgRd5gp9Y0G by tony@toot.hoyle.me.uk
       2023-07-24T12:57:05Z
       
       1 likes, 1 repeats
       
       @neil @dino @snikket_im That's the problem.. it ends up an unfixable black box.  For distribution really appimage/flatpak are better as docker screws around with firewall and networking.. unless you're developing microservice architectures it's overkill.
       
 (DIR) Post #AY1LRnrPr3O0z7GdbU by snikket_im@fosstodon.org
       2023-07-24T13:24:16Z
       
       1 likes, 1 repeats
       
       @tony Docker can indeed be annoying when it comes to networking! Snikket doesn't use any of Docker's network stack and uses "host" networking the same way normal packages would (so your usual firewall will still apply, IPv6 still works, and performance isn't degraded).In the future we're looking at official podman support which has a number of benefits over docker.@neil