- Member | 1
I would like to know what tools you use for project deployment?
I deploy rather frequently and randomly to several projects and current state of my tools is not satisfying enough
I am not interested in copy-paste helpers like ftp deployment tool or just using git. Rather I would like to know how if you use CI or some lighter alternative to handle setup, database migration and other stuff that comes with it eg.: package management.
I do it like this:
I use composer, pear or pecl (ordered by preference).
Usually manually with some complex scripts written and tested on side, or via
adminers create+alter export option for simple cases from test database to
I was for some time considering using rake db:migrate tool from ruby but I have seen it on just one project and badly implemented (and config has to be duplicated for this tool and it is ruby).
I don't do testing (but that will change in near future).
Do you even test projects after deploy?
For automated generation I use mine web-resource-management (as of yet it generates on request, pre-generation will be implemented rather soon).
I hope it is everything, if you find important part of project deployment I omitted please include it in your response.
- Member | 301
Hi, we use deployer as the last job in our CI/CD pipeline. It comes with some predefined common deploy scenarios which you can extend with custom commands, or you can set up scenario from scratch. It supports zero-downtime deployment as well (uses symlink switch).
When using SSH strategy, you can run any command you want on the remote server, so you can basically run database migrations, cache warmup or whatever else right in the deployment process.
Assets build and tests are run in preceding jobs of the pipeline.
Last edited by dakur (2021-05-25 12:43)