# Automated deployment to Rancher **URL:** \ **Category:** Rancher 1.x\ **Created:** [July 7, 2015, 7:53pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35 "2015-07-07T19:53:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![spacezio](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@spacezio](https://forums.suse.com/u/spacezio)\ **Post date:** [July 7, 2015, 7:53pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/1 "2015-07-07T19:53:28Z")
I have a repository on Docker Hub that is an automated build. The development process currently ends with the container build. I would like to extend this process into Rancher and automate the deployment into a specific environment/project. Is there a way to do that natively in Rancher? An external process would suffice as well. I am using Ansible to build the containers and could extend that to manage the deployment. Any direction or suggestions would be great. Thanks! ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [July 7, 2015, 8:01pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/2 "2015-07-07T20:01:04Z")
Rancher-compose would be able to deploy services (multiple containers) into a specific environment/project within Rancher. It works just like docker-compose, where you have a docker-compose.yml and a rancher-compose.yml files. You would be able to do a rancher-compose up, which would deploy the services into a specific environment/project. [http://rancher.docs.rancher.com/docs/rancher-compose/](http://rancher.docs.rancher.com/docs/rancher-compose/) I believe that would help you start with what you’re looking to do. ---
**Author:** ![spacezio](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@spacezio](https://forums.suse.com/u/spacezio)\ **Post date:** [July 7, 2015, 8:04pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/3 "2015-07-07T20:04:36Z")
Thanks! Would that imply a manual process and not something automated? ---
**Author:** ![fnord](https://avatars.discourse-cdn.com/v4/letter/f/97f17d/32.png) [@fnord](https://forums.suse.com/u/fnord)\ **Post date:** [July 8, 2015, 9:53am UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/4 "2015-07-08T09:53:41Z")
Ansible seems like the way to go. I haven’t done this myself but it’s something I’ve been thinking about. You could have it template a docker compose with enviornment specific settings and then run a command to start that up. I’m personally hoping that docker label support gets into Ansible soon so that can be used to provision Rancher containers directly. ---
**Author:** ![wizardofmath](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/wizardofmath/32/23_2.png) [@wizardofmath](https://forums.suse.com/u/wizardofmath)\ **Post date:** [July 9, 2015, 5:49pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/5 "2015-07-09T17:49:06Z")
@spacezio It sounds like you are wanting a way for rancher to have incoming webhooks. That way you can trigger it in a chain. Or am I misreading what you trying to accomplish? ---
**Author:** ![spacezio](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@spacezio](https://forums.suse.com/u/spacezio)\ **Post date:** [July 9, 2015, 6:35pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/6 "2015-07-09T18:35:11Z")
@wizardofmath that would be the ideal method, yes. Failing that I was looking for an alternative method, for now we’ll likely extend our Ansible configuration. ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [July 15, 2015, 9:04pm UTC](https://forums.suse.com/t/automated-deployment-to-rancher/35/7 "2015-07-15T21:04:21Z")
@spacezio Re-reading this and thinking that maybe you are looking for this feature request: [https://github.com/rancher/rancher/issues/619](https://github.com/rancher/rancher/issues/619)