this post was submitted on 20 May 2024
26 points (90.6% liked)

Programming

17366 readers
135 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] DirigibleProtein@aussie.zone 3 points 5 months ago (1 children)

If anything goes wrong with the deploy script, such as failing tests, no harm will be done because the script exits upon the first error encountered.

How do you clean up? Once the deploy script is fixed, how do you know what’s been done and what needs redoing?

Have you considered ansible/puppet/chef/salt — environments dedicated to deployment and cleanup, with idempotency to allow for fixing and repeating the deployment, across multiple operating systems and versions?

[–] Aijan@programming.dev 4 points 5 months ago

Cleanup can be as simple as deleting the latest deployment directory, if the script gets that far. The article is about using built-in Linux tools for 'easy' application deployments. One can also use dedicated tools, as you suggested, to further automate the deployment process.