This post describes my lessons learned after 10 years running production environments in sizes ranging from "just getting started" to a "Series F" company wi...

cross-posted from: https://lemmy.world/post/21065836

Hi friends, as promised, I’m back with my second post. I’ll be hanging around in the comments for any questions!

In this post, I take a look at a typical deployment process, how long each part of it takes, and then I present a simple alternative that I use which is much faster and perfect for hobbit software.

  • MajorHavoc@programming.dev
    5·
    2 years ago

    This is great stuff.

    My comment from the peanut gallery today is just that there’s no law that CI/CD can’t be kept under control and run in ten seconds.

    Given the choice between a slow out of control CI/CD mess, or a shell script, I too will take the shell script every time.

    But I am living my best life today, and have a simple shell script in my CI/CD pipeline.

    • sloppy_diffuser@sh.itjust.worksEnglish
      3·
      2 years ago

      For our lower environments we use rsync like the author but skip the pipeline altogether. The servers have a watch script to restart when files are rsynced. We then have a local watch script that rsyncs on file changes.

      Relatively instant deploy (2-5s) whenever a file is saved.