Source: fidum.uk
Deploying the same code to multiple Laravel Vapor projectsCategory: Software, Database, Data, Redis, github, automation
I have been using https://vapor.laravel.com/ since it was launched at our company to deploy our white-label product to multiple different aws accounts and projects. The problem is that when you configure vapor it has a one-to-one relation between your code, and a vapor project.
In order to make this happen, for each client we have one nonprod AWS account and one production AWS account.
The prod environment is similar in that it has a production environment that will be deployed to the clients prod AWS account.
So we created a new S3 bucket in our central AWS account and put a.travis.yml in our vapor config repository.
In order to make this happen, for each client we have one nonprod AWS account and one production AWS account.
The prod environment is similar in that it has a production environment that will be deployed to the clients prod AWS account.
So we created a new S3 bucket in our central AWS account and put a.travis.yml in our vapor config repository.
Related Articles
Community Partners
DevOps Careers