Comment on Best way to dockerize a static website?

• jj4211@lemmy.world ⁨8⁩ ⁨months⁩ ago

  But it you already have an nginx or other web server otherwise required to start up (which is in all likelihood the case), you don’t need any more auto startup, the “reverse proxy” already started can just serve it. I would say that container orchestration versioning can be helpful in some scenarios, but a simple git repository for a static website is way more useful since it’s got the right tooling to annotate changes very specifically on demand.

  That reverse proxy is ultimately also a static file server. There’s really no value in spinning up more web servers for a strictly static site.

  Folks have gone overboard assuming docker or similar should wrap every little thing. It sometimes adds complexity without making anything simpler. It can simplify some scenarios, but adding a static site to a webserver is not a scenario that enjoys any benefit.

  source

  • sudneo@lemmy.world ⁨8⁩ ⁨months⁩ ago

    It really depends, if your setup is docker based (as OP’s seems to be), adding something outside is not a good solution. I am talking for example about traefik or caddy with docker plugin.

    By versioning I meant that when you do a push to master, you can have a release which produces a new image. This makes it IMHO simpler than having just git and local files.

    I really don’t see the complexity added, I do gain isolation (sure, static sites have tiny attack surfaces), easy portability (if I want to move machine it’s one command), neat organization (no local fs paths to manage essentially), and the overhead is a 3 lines Dockerfile and a couple of MB needed to duplicate a webserver binary. Of course it is a matter of preference, but I don’t see the cons honestly.

    source
• smileyhead@discuss.tchncs.de ⁨8⁩ ⁨months⁩ ago

  Serving static app in Caddy:

  sudo apt install caddy sudo systemctl enable --now caddy

  Then in /etc/caddy/Caddyfile:

  example.com {
     root * /var/www/html
     file_server
  }
  

  That’s all, really.

  source

  • sudneo@lemmy.world ⁨8⁩ ⁨months⁩ ago

    If there is already another reverse proxy, doing this IMHO is worse than just running a container and adding one more rule in the proxy (if needed, with traefik it’s not for example). I also build all my servers with IaC and a repeatable setup, so installing stuff manually breaks the model (I want to be able to migrate server with minimal manual action, as I had to do it already twice…).

    The job is simple either way, I would say it mostly depends on which ecosystem someone is buying into and what secondary requirements one has.

    source