In the past you would stand up and hand-configure all of the hardware that would run your software. This is a way to define the hardware configuration in software and apply it automatically. Advantages of this approach include increased scalability, reproducibility, and being able to use version control.
Plus, it is idempotent, which means you don’t have to change it before pushing it to an existing infrastructure. If you do change it, the infrastructure will be updated to match. It ends the need for custom deployment scripts.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Infrastructure as Code
In the past you would stand up and hand-configure all of the hardware that would run your software. This is a way to define the hardware configuration in software and apply it automatically. Advantages of this approach include increased scalability, reproducibility, and being able to use version control.
Plus, it is idempotent, which means you don’t have to change it before pushing it to an existing infrastructure. If you do change it, the infrastructure will be updated to match. It ends the need for custom deployment scripts.