Skip to content

Build Archive

Real-world DevOps from a Node.js developer's homelab

  • Home
  • Topics
    • Containers & Kubernetes
    • CI/CD & Delivery
    • Infrastructure as Code
    • Observability & Performance
    • Cloud & Scalability
    • Architecture & Methods
    • Automation & Tooling
  • About
  • Contact

Category: Infrastructure as Code

Terraform, Ansible, GitOps and the practice of managing infrastructure through versioned, testable code.

  • Home
  • Infrastructure as Code
Infrastructure as Code

Provisioning Proxmox Containers with Terraform: Two Real Breaks Before It Worked

12 de August de 2026 Cristóbal

I don’t run Terraform against my Proxmox box day to day — my containers get created directly with pct, and that’s honestly the right tool

Read More
Infrastructure as Code

Infrastructure as Code in Practice: Terraform, Ansible, and GitOps for Delivery Pipelines

9 de April de 202614 de July de 2026 Cristóbal

Introduction When I first started managing my Proxmox homelab alongside production Node.js services, I quickly realized that clicking through dashboards to provision VMs was a

Read More
Infrastructure as Code

Terraform, Ansible, and Crossplane: The “Everything as Code” Stack Explained

3 de April de 202614 de July de 2026 Cristóbal

I’ve been running a Proxmox homelab for a couple of years now, and the single biggest quality-of-life improvement came not from buying better hardware, but

Read More
  • Architecture & Methods
  • Automation & Tooling
  • CI/CD & Delivery
  • Cloud & Scalability
  • Containers & Kubernetes
  • Infrastructure as Code
  • Observability & Performance
  • Privacy Policy
  • Cookie Policy
  • Terms and Conditions
  • Disclaimer
  • Legal Notice
  • Contact
© 2026 Build Archive. All rights reserved.
Manage Consent

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}