Context
Applis Technologies needed Vue.js and Laravel dashboards that could ship to AWS without a manual, error-prone release night. I worked as a senior backend Laravel developer: I built and maintained the dashboards and owned how they got to production.
The challenge
The product was fine until deploy. Releases were the risk. They needed a repeatable pipeline and hosting that stayed secure and scalable without someone clicking through a console every time.
The approach
I developed the Vue and Laravel dashboards and put AWS CodePipeline in front of GitHub so a merge could become a release. Elastic Beanstalk, RDS, CloudFront, and S3 carried the hosting: app, data, CDN, and assets as a stack instead of a collection of servers.
The point of the pipeline is that the next change is cheaper than the last one.
What shipped
- Vue.js and Laravel dashboards, built and maintained
- Streamlined deploys via AWS CodePipeline and GitHub
- Elastic Beanstalk, RDS, CloudFront, and S3 hosting
How it holds up
Production is boring in the way it should be. Dashboards ship through the pipeline onto infrastructure that was chosen to scale, not to impress a slide.
Results
What this engagement left in production.
- Vue.js + Laravel dashboards, built and maintained
- Streamlined deploys via AWS CodePipeline + GitHub
- Elastic Beanstalk, RDS, CloudFront, and S3 hosting
- Secure, scalable production infrastructure
