Docker Flarum. Disadvantages?

Oton

Hello. I'm testing a docker flarum deployed in Hetzner cloud. I'm seeing this is different than the regular version. I can't see some files, like config.php, index.php, site.php... Or at least I can't find them.

I need to used Bash to install the extensions in a different way. And also I see there are several builds made by different users...

So, I'm wondering. What are the pros & cons of the docker version? There are some incompatibilities with the different flarum updates and extensions with the current different builds?

What would happen if the build I use, is discontinued in the future? I couldn't update anymore?

Thank you.

luceos

Oton What would happen if the build I use, is discontinued in the future? I couldn't update anymore?

You can always take your composer.json and database dump and install Flarum the usual way. There's hardly ever any risk no matter the installation method you use. Unless it's managed hosting like FreeFlarum or Blomstra; in that case you rely on the terms of use (both parties have extremely fair exporting terms though).

Oton What are the pros & cons of the docker version?

A lot can be said on this topic, here's a few things:

Docker in itself is an advanced way of hosting. Using a docker image allows for easier horizontal scaling (more machines instead of larger ones).
Using Docker makes things more complex, because you need to interact with the virtualised machine instead of the host machine. Eg, you have to run commands inside the docker engine.
Hosting an application is never easy, although it might seem like that. After installation you always have the responsibility of spam prevention, security updates etc. You might as well add docker to that 🙂