IaC

This section covers Infrastructure as Code (IaC) for Files.com. Use it to manage configuration through code and version control. Use it to make changes repeatable, reviewable, and automatable.

When To Use IaC

Use IaC when you need consistent environments. This includes dev, test, and production.

Use IaC when multiple people manage configuration. Code review reduces misconfiguration risk.

Use IaC when you run many sites. Automation reduces manual setup time.

What You Manage With IaC

IaC manages Files.com configuration as declared resources. Your code becomes the source of truth.

This usually includes users, groups, permissions, and integrations. It can include folder structure.

The exact coverage depends on the tool and provider version.

Supported Tools

Files.com supports IaC with Terraform and OpenTofu. Both use similar workflows.

Start with Terraform if your organization standardizes on it.

Use OpenTofu if you standardize on OpenTofu.

Typical Workflow

Define desired state in code. Store that code in version control.

Plan changes before applying them. Review the plan output with stakeholders.

Apply changes from an automated pipeline or controlled workstation.

How IaC Fits With Other Automation

IaC is for configuration lifecycle. It is not for file movement workflows.

Use Automations to react to file events.

Use SDK & APIs for custom runtime behavior.

Next Steps

Pick a tool and follow the setup page. Then apply the first small change.

Use patterns like variables and iteration for scalable config.