Jenkins or any other CI/CD system is the ideal solution, but it's arguably a bit overkill for small teams, unless you really to show off devops like a boss.
With a little work you can setup a git server with bare repos and a post-receive hook, to make deploy possible with a simple push to a specific remote. There are services, like the mentioned DeployHQ, that basically provide this functionality (with a lot of bells and whistles), for a price. In the absence of such options, I usually require an ssh access and just use git & composer from cli. Using an FTP client manually is a but too old fashioned and I would not consder it as a viable and reliable alternative, these days. Stefano Torresi Web Developer 2014-05-08 6:41 GMT+02:00 Ralf Eggert <[email protected]>: > Hi, > > I wonder how all of you deploy your ZF2 applications to both staging and > production servers. I used a couple of different approaches and have > seen others in projects respectively: > > - Use Git and Composer for deployment > - Use https://github.com/zfcampus/zf-deploy > - Use Jenkins CI for deployment > - Use good old FTP (extra tool or with IDE support) > > Which way do you prefer? Do you use other deployment strategies? Is > there a standardized way to follow? > > I am looking forward for your thoughts and ideas. > > Thanks and best regards, > > Ralf > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > >
