You don't need to learn BigConfig, your agent can operate it for you.
Deploying non-trivial software is possible in English without writing a single line of code — try it yourself with the plan.md below.
You don't need a "greenfield" project to see immediate value. BigConfig meets you where you are, automating legacy provisioning without the "rip and replace" headache. Ask your agent to convert your existing DevOps project to a BigConfig package.
Escape the "Kubernetes tax". You shouldn't have to manage a complex K8s cluster just because a vendor distributed a tool via Helm. BigConfig empowers you to build packages tailored to your specific stack, giving you total sovereignty over your architecture.
Stop over-provisioning infrastructure just to meet rigid software requirements. BigConfig lets you package applications to fit your existing environment—not the other way around.
Describe the deployment in plain English. Your agent refines the plan,
writes a single bb.edn, and runs it.
You need to create a project to deploy a web application.
This project contains only the `bb.edn` file.
The `bb.edn` contains the dependency https://github.com/amiorin/once
You can download https://github.com/amiorin/once to see how it works.
https://github.com/amiorin/once is built on top of https://github.com/amiorin/big-config
You can download https://github.com/amiorin/big-config to see how it works.
All the options should be defined in the `bb.edn`.
Only the package task should be created.
Only io.github.amiorin.once.package should be required in `bb.edn`
The domain is bigconfig.online.
The host is www.bigconfig.online.
The container is ghcr.io/amiorin/big-config-website:latest
The compute provider is OCI with 6 GB, 1 core, and 50 GB of disk.
The dns provider is Cloudflare.
The smtp provider is Resend.
The backend provider is S3.
You need to create the `.envrc` to store environment variable for the credentials, I will provide the values later.