I still point to this document as the base of DevOps. Most people I work with in IT never read it. If you want to do proper DevOps these are a requirement not optional.
Last time I pointed someone to this site was last week.
The Twelve-Factor App (2025)
171–180 of 184 posts
Re: The Twelve-Factor App (2025)
#172Ah memories. Adam Wiggins, Heroku. Great marketing. IMHO to some extend not only best practices, but also limitations of the platform they had built.
Interesting to see that also this now copyright by Salesforce.
Re: The Twelve-Factor App (2025)
#173Still incredibly relevant. Even if you don’t apply it, there is so much to learn by reading this in 15 minutes. The only grievance I have with this is Chapter 3: Config [1] “Store config in the environment”, “Credentials to external services such as Amazon S3 or Twitter” Besides being bad advice, this had the second-order effect of leading devs to believe they could put all their local env secrets in ~/.bashrc files.…
It’s a terrible pattern, but one that is simply entrenched. Pretty much everything treats .env as if it’s /etc/shadow now.
I would prefer to see secrets from .env not actually splattered in the environment but processed/read on demand, and there are indeed libraries to do that.
Re: The Twelve-Factor App (2025)
#174How is this only from 2025? I thought this was a thing back in 2015
It's even older the page says "Last updated 2017" and the repo goes back to 2011, and in fact see HN discussion from November 2011: https://news.ycombinator.com/item?id=3267187
Re: The Twelve-Factor App (2025)
#175[dead]
Re: The Twelve-Factor App (2025)
#176Very good discussion on III. Config or the use of environment variables for config. For the sake of discussion I'd share an argument against X. Dev/Prod parity https://www.sc.com/engineering/blogs/Technology/development-... I do not fully agree with the author and I think the author is reaching a bit hard because in my reading Twelve-Factor App X does not argue for complete parity. My reading is that whatever the app…
that link 404's :(
Re: The Twelve-Factor App (2025)
#177Still incredibly relevant. Even if you don’t apply it, there is so much to learn by reading this in 15 minutes. The only grievance I have with this is Chapter 3: Config [1] “Store config in the environment”, “Credentials to external services such as Amazon S3 or Twitter” Besides being bad advice, this had the second-order effect of leading devs to believe they could put all their local env secrets in ~/.bashrc files.…
I'm the creator of Node dotenv and I gave this a lot of thought a couple years back. I put together a whitepaper on this. Ultimately your secrets do still have to hit your environment. But at-rest they should be split from the environment. Today I think that is encrypting your .env file and keeping the decryption key separate. Bring the decryption key only at runtime inside your environment.
Re: The Twelve-Factor App (2025)
#178This is way older than 2025, no?
Re: The Twelve-Factor App (2025)
#179Very good discussion on III. Config or the use of environment variables for config. For the sake of discussion I'd share an argument against X. Dev/Prod parity https://www.sc.com/engineering/blogs/Technology/development-... I do not fully agree with the author and I think the author is reaching a bit hard because in my reading Twelve-Factor App X does not argue for complete parity. My reading is that whatever the app…
that link 404's :(
What a shame.
Please check the archive for now: https://web.archive.org/web/20240628184010/https://www.sc.co...
Re: The Twelve-Factor App (2025)
#180Still incredibly relevant. Even if you don’t apply it, there is so much to learn by reading this in 15 minutes. The only grievance I have with this is Chapter 3: Config [1] “Store config in the environment”, “Credentials to external services such as Amazon S3 or Twitter” Besides being bad advice, this had the second-order effect of leading devs to believe they could put all their local env secrets in ~/.bashrc files.…
> Besides being bad advice, this had the second-order effect of leading devs to believe they could put all their local env secrets in ~/.bashrc files.
I don't agree, and I think this is personal belief is unfounded. 12 factor apps clearly apply to deployments, not your local dev environment. The whole industry pivoted towards .env files in local dev environments. Local dev tools still store their secrets where they can: local storage.