Twelve-Factor Apps
summary
Advocates applying the 12‑factor rules to Laravel with concrete practices: commit vendor directory to avoid external downtimes, bake dependencies into images via Docker or Packer and use multi‑stage builds, store encrypted config in S3 or use AWS SSM/Secrets Manager and export env vars at deploy, use IAM roles and managed RDS, treat backing services as attachable resources, prefer SQS over MySQL for high‑volume queues, give each release a unique ID and never change a running release, log to stdout and push logs to a collector.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:4312 FACTOR APPS
- 5:02DEPENDENCIES
- 16:10Acceptable exceptions: In production everything is highly available Environment variable config differences
- 28:28PORT BINDING
- 30:39CONCURRENCY
- 32:42DISPOSABILITY
related talks
48m12 Factors Laravel
24mTwelve Factor App
46mThe 12 Factor App for Data
44mMillions of Apps: What we've learned
34m7 Missing Factors for Your Production-Quality 12-Factor Apps
27mCF & The 12-factor App 101: The Secret Decoder Ring for Operations
23m12 Factor Frontend Apps through Dockerization
01h 11mTwelve Factor Apps in .NET : Building apps for the cloud