![]() ![]() TODO: Deployment Tasks # i.e.: Run Puppet Apply, Restart Daemons, etc $ mkdir push-to-deploy $ cd push-to-deploy $ mkdir '" # 4. Let's keep things straightforward by placing our development git repository, remote git repository, and deploy directory under the same local directory. (I'm assuming a working knowledge of: terminal, git, and a scripting language.) Preparing our Repositories In this post, I'll walk through the setting up Push-to-Deploy from the ground up. The Push-to-_ pattern is powerful and easy to use, once you know how the pieces fit together. I've started thinking about my next iteration of this system for Didsum, and using pushing for more than just deployment purposes. It offers the simplicity of the "push-to-deploy" model Heroku pioneered, with full control and flexibility over the operating system environment. ![]() ![]() It worked so well I transitioned my company's development process onto it for all of our new projects starting last year. I first set up a push-to-deploy system with git and puppet for a side project a few years back. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |