Empower your Laravel project as cloud native application
Former Software Engineer,
switched to the dark side of
DevOps Engineer @ Kiratech
NOt many slides, just demos...
...hoping everything goes fine!
(meme courtesy of @liuggio)
One codebase tracked in revision control, many deploys.
Explicitly declare and isolate dependencies
(A twelve-factor app never relies on implicit existence of system-wide packages)
The twelve-factor app stores config in environment variables.
Env vars are easy to change between deploys without changing any code.
Treat backing services as attached resources.
A codebase is transformed into a (non-development) deploy through these three stages.
Execute the app as one or more stateless processes.
Export services via port binding.
Scale out via the process model.
Maximize robustness with fast startup and graceful shutdown.
Keep development, staging, and production as similar as possible.
Treat logs as event streams.
Run admin/management tasks as one-off processes.
By Dario Tranchitella