Auto-deploy using non-master branches

[janwerkhoven]

We deploy our code to branch staging and production, not to master. Due this fact we cannot use the auto-deploy feature in either environment. I find myself having to go to /frontends every single time to manually enable the new builds.

Solution: let user choose which branch to listen to for auto-deploy?

What do you think?

PS: Ember Front-end Builds is single best package we ever added to our Ember app. Greatly improved our work and deploy flow. Keep it coming!

[samselikoff]

Thank you for the kind words!

I think this is a great idea, we should add a config option to UI. I think this would be on the Rails gem side of things, right?

[janwerkhoven]

Where ever you think is best. As long as we can configure it somewhere would be great. Make sure it can use the Rails or Ember environment variables. We deploy a staging build to branch staging and deploy it on a staging subdomain. After that we deploy a production build to branch production and deploy it to our main domain.