# Vagrant based dev stack

**URL:** <https://forums.suse.com/t/vagrant-based-dev-stack/1445>\
**Category:** Rancher 1.x\
**Created:** [January 12, 2016, 3:03pm UTC](https://forums.suse.com/t/vagrant-based-dev-stack/1445 "2016-01-12T15:03:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![richardoflynn](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@richardoflynn](https://forums.suse.com/u/richardoflynn)\
**Post date:** [January 12, 2016, 3:03pm UTC](https://forums.suse.com/t/vagrant-based-dev-stack/1445/1 "2016-01-12T15:03:25Z")

</div>

In my dev environment, I would quite like to vagrant up my entire stack - one that has the the rancher server running on the same host as the docker host. The only issue being each time I vagrant up the stack, the rancher server is assigned a random registration ID / URL. Is there any way that you could query the server for this value and export it out for consumption by a script in the rancher agent, or a way that you could fix this value from the outset with an environment variable?

Im guessing its a bit obscure and has no real requirements in the real world. A pointer to a hack would be nice though!

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [January 14, 2016, 10:53pm UTC](https://forums.suse.com/t/vagrant-based-dev-stack/1445/2 "2016-01-14T22:53:37Z")

</div>

Not sure if this will help completely, but in the comments of this issue it talks about the registrationURL and how to get it through the API. Currently, there definitely is no way to make the URL using an environment variable.

> [@Is there a way to create a digital ocean host programmatically?](http://forums.suse.com/t/is-there-a-way-to-create-a-digital-ocean-host-programmatically/114/4):
>
> There is not really any documentation of the API, we consider it largely an internal implementation detail for the UI until there is user demand for it because we don’t want to take attention away from all the native docker functionality that we integrate with. The UI is 100% static content on a CDN so it is entirely driven by the API. So there is quite a bit of tooling, framework, and design that goes into it… because we do expect user demand for it eventually, but more importantly because as…

---

<div class="post-metadata">

**Author:** ![richardoflynn](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@richardoflynn](https://forums.suse.com/u/richardoflynn)\
**Post date:** [January 15, 2016, 9:57am UTC](https://forums.suse.com/t/vagrant-based-dev-stack/1445/3 "2016-01-15T09:57:39Z")

</div>

Hi Denise, thanks for coming back to me. Actually if you are running a dev cluster on a single machine (as I was), there is already a vagrant script that does this (without requiring the registrationURL on the basis that when you launch locally authentication is not set)

[https://github.com/rancher/rancher/blob/master/Vagrantfile](https://github.com/rancher/rancher/blob/master/Vagrantfile)

Also cloudnautique pointed me to some bash scripts that you could implement if you want the server to expose the reg url for later consumption by other scripts:

a combo of:

> <https://github.com/rancher/10acre-ranch/blob/master/bin/gce-10acre-ranch#L279>

  

> <https://github.com/rancher/10acre-ranch/blob/master/bin/gce-10acre-ranch#L285>

thanks!