12factor's Introduction

The Twelve-Factor App

Showing how to create a Tweleve-Factor app using ASP.NET Core and Azure DevOps.

Each factor will live in a branch for that factor. The master branch will contain the completed project.

Branch 1: Codebase

One codebase tracked in revision control, many deploys

Branch 2: Dependencies

Explicitly declare and isolate dependencies

Branch 3: Config

Store config in the environment

Branch 4: Backing services

Treat backing services as attached resources

Branch 5: Build, release, run

Strictly separate build and run stages

Branch 6: Processes

Execute the app as one or more stateless processes

Branch 7: Port binding

Export services via port binding

Branch 8: Concurrency

Scale out via the process model

Branch 9: Disposability

Maximize robustness with fast startup and graceful shutdown

Branch 10: Dev/prod parity

Keep development, staging, and production as similar as possible

Branch 11: Logs

Treat logs as event streams

Branch 12: Admin processes

Run admin/management tasks as one-off processes

12factor's People

Contributors

Stargazers

Watchers

12factor's Issues

What Are The Ideas for Admin Processes?

I know I'm here early, but what are your initial ideas for implementing the 12th factor, Admin Processes?
Since C# doesn't have a REPL this poses some challenges.

Some ideas that I've had:

A separate command line project that can call the admin process specific code.
Implement something like EF Core does for keeping track of migrations. You could queue up the one-off admin process and the process would be logged in the _AdminProcessHistory table when it has started.

Recommend Projects