Tag Info

New answers tagged

1

Most CI servers are somewhat language agnostic -- at the end of the day you are really just executing shell scripts with some fancy reporting -- so your general premise is correct. The physical deployment of PHP apps is typically pretty simple -- they are just files on disk so rsync is your friend here. The difficult parts come in with things like user data ...


2

If you're using GitHub as your central Git repository, you could take a look at Travis CI. It's a cloud-based CI system, so you don't have to manage the server yourself. I'm thinking of trying this out for some of my open-source projects. If you want to stick with Apple's tools all the way, try out Bots. It ships as part of Xcode Server. I've been ...


6

Continuous deployment or continuous delivery is very common in web services and SaaS apps. Amazon, Facebook, Github, Google...they're all deploying all the time. Some operators deploy a handful or even dozens of updates a day for each very narrowly-defined service. I'm not even sure you could easily count the number of deployment events massive shops like ...


2

I think this varies from project to project. Generally the advise by Bart is a valid one. If these assets are directly connected to the source-code and managed by the developer (best example are images statically linked/embedded in a template) it's a good practice to have them inside the repo. If this isn't the case, we have to ask some other questions. ...



Top 50 recent answers are included