3 ms·

they provide ready to be deployed Docker images https://hub.docker.com/_/ghost/ https://hub.docker.com/_/ghost/

• zimpenfish 4y ago
  Although, to throw some historically anecdotal salt into the fire, I was kinda forced to switch from Ghost to Hugo when firstly, the migration to v1.0 (late 2017) using the Docker images was a right old faff and secondly, a few months later (early 2018), said Docker image managed to wedge itself into an inoperable mess.
  • ushakov 4y ago
    yeah, but just like with everything else you self-host - requires maintenance
  • neurostimulant 4y ago
    > said Docker image managed to wedge itself into an inoperable mess Can you elaborate on the issue you encountered? Most issues I've seen in the wild related to docker deployments is due to not specifying a version tag on the docker image, which means docker will pull the image with the `latest` tag. Fast forward a few years, when you need to restart the container, and for some reason you pull the `latest` image again (either accidentally or automatically by your container system), the new version is now too far ahead from your previous system and break spectacularly when run with your existing data. Some apps even attempt to migrate the data, but failed and leave the data in corrupted state so you can't go back to the previous version.
    • zimpenfish 4y ago
      > Can you elaborate on the issue you encountered? Alas, no, I didn't keep detailed notes at the time (2018) because I was too busy trying to recover my blog from the disaster. > Fast forward a few years [...] the new version is now too far ahead It was 6 months after the migration to v1 and 5 months before v2 came out.