Automize it7/7/2023 ![]() I’m gonna move these into the script and update the README to point to the script. At the moment, it seems that we have some documented steps in our README.md. This is the heart of this trick: we are creating a single, reliable source of truth for deployments!Ī trick is to search for keywords, such as “Deploy”. My task is less daunting, and yet critical: collect the steps needed to deploy the software, and put them in the script. But before we dive into the actual automation, it would be nice to know what exactly should be automated. Now, everything is ready to do the actual deployment work. The behavior hasn’t changed, but now I have a playground to do more! 3) Collect existing knowledge It now takes a few seconds since ts-node has to compile the TypeScript file and run the logic, but that’s OK for my needs. I run the command again to test it’s still working. I will declare this command in the top-level package.json as if it was already working! Thus, I know the intuitive command would be something like yarn deploy. This project is a TypeScript one and the team is using Yarn. Well, having a single command to deploy the software would be sweet. What ideal behavior would the team ideally have? The first step is to think about the habit you want to create. Something that will give you the most bang for your buck. Something you can realistically do within 1h, even if you aren’t a Docker expert. Hopefully, I know a trick to get over that analysis paralysis situation!Ī technique that will help us break the status quo. And it seems to be an all-or-nothing situation: how good would a deployment script be if it doesn’t deploy the whole thing? ![]() Some may be really hard to automate in the first place. ![]() There may be a LOT of steps involved-some you may not even be aware of. I should fix that!īut wait, automating the deployments would be ideal… but is it realistic? And I think I’m the only one who actually knows all of the steps. Deploying the backend involves a few manual steps-not too much, but just enough to be subtle. Deployments are still depending on that one person who knows it all. You have other things to do, and all of this work feels overwhelming! You thought about automating the deployment process, but you are not a Docker expert.
0 Comments
Leave a Reply. |