Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

fleet remote add <name> #19

Open
livedata opened this Issue May 27, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@ghost

ghost commented May 27, 2012

I'm wondering about this 'name' parameter... What is it for? I didn't see any command which could use it... But i can see that: fleet deploy default or fleet deploy testenv or fleet deploy staging-env - would be very handy.

Raynos commented Aug 2, 2012

--remote=<name>

Say you have three hubs listening on different ports with different drones connected to each one

{
  "remote": {
    "default": {
      "hub": "localhost:7000",
      "secret": "fooSecret1"
    },
    "dev": {
      "hub": "localhost:8000",
      "secret": "devSecret"
    },
    "staging": {
      "hub": "localhost:9000",
      "secret": "stagingSecret"
    }
  }
}

Deploy to dev
fleet-deploy --remote=dev to deploy to development hub

Deploy to staging
fleet-deploy --remote=staging

Deploy to default
fleet-deploy or fleet-deploy --remote=default

The same is true for the the other commands like fleet-ps and fleet-stop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment