# Different deployment environments

**URL:** https://forums.suse.com/t/different-deployment-environments/8060
**Category:** General
**Created:** [December 15, 2017, 8:26pm UTC](https://forums.suse.com/t/different-deployment-environments/8060 "2017-12-15T20:26:46Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![chrisreed87](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/chrisreed87/32/2940_2.png) [@chrisreed87](https://forums.suse.com/u/chrisreed87)
#### Post date: [December 15, 2017, 8:26pm UTC](https://forums.suse.com/t/different-deployment-environments/8060/1 "2017-12-15T20:26:46Z")

</div>

Curious how others are managing their rancher deployments to different environments. We have a 3 stage environment, lab, stage, production and the deployments _should_ follow that natural path.

So i have my rancher configs living in a repo `/stackname/docker-compose.yml + rancher-compose.yml` and i can deploy easily using `rancher up`.

I can set different environment variables in the config files like `$variable` but wondering how others are doing it at the .yml level for different envs.

Like `if env=lab` then `image: org/app:latest` else `if env=stage` then `image:org/app:1.01`

Maybe something clever with the host “Require container level”?

Thanks in advance!