# \[20160623185456\] CLI Start, Build, Switch Improvements

**URL:** <https://community.convox.com/t/20160623185456-cli-start-build-switch-improvements/375>\
**Category:** Releases\
**Created:** [June 20, 2016, 9:36pm UTC](https://community.convox.com/t/20160623185456-cli-start-build-switch-improvements/375 "2016-06-20T21:36:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ddollar](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ddollar/32/3_2.png) [@ddollar](https://community.convox.com/u/ddollar)\
**Post date:** [June 20, 2016, 9:36pm UTC](https://community.convox.com/t/20160623185456-cli-start-build-switch-improvements/375/1 "2016-06-20T21:36:49Z")

</div>

## Convox Start: Better manifest validation

Thanks to [@awsmsrc](https://github.com/awsmsrc) on [#763](https://github.com/convox/rack/pull/763) and [#742](https://github.com/convox/rack/pull/742), `convox start` has better validation around the manifest yaml format, and the cron label. Improvements like this help cement `convox start` as both a development tool and a production verification and configuration tool.

As a reminder, configuring a scheduled task in production is as simple as using the `convox.cron` label:

```auto
web:
  build: .
  labels:
    - convox.port.443.protocol=tls
    - convox.port.443.proxy=true
    - convox.cron.jobs=0 * * * ? rake jobs
  links:
    - database
  ports:
    - 80:4000
    - 443:4001
database:
  image: convox/postgres
  ports:
    - 5432

```

See the [Preparing an Application](https://convox.com/docs/preparing-an-application/) and [Scheduled Tasks docs](https://convox.com/docs/scheduled-tasks/) for more info.

## Convox Build: Better .dockerignore support

Thanks to [@awsmsrc](https://github.com/awsmsrc) in [#757](https://github.com/convox/rack/pull/757), the tarball of code that is uploaded during `convox build` handles `.dockerignore` exactly the same as `docker build`. This is accomplished by delegating responsibilities to the `docker/archive` package.

## Convox Switch

Thanks to [@ddollar](https://github.com/ddollar) and [@nzoschke](https://github.com/nzoschke) in [#691](https://github.com/convox/rack/pull/691), `convox switch` finally offers more strategies to manage multiple racks.

Notably you can `export CONVOX_RACK=myorg/staging` to set the Rack for a particular terminal session.

You can also add the `--rack=myorg/production` flag to explicitly pick a Rack for any operation.

See the [CLI Reference Guide](https://convox.com/docs/cli/) for information about `convox switch`, as well as setting up bash completion and a PS1 helper.

With improvements like this, we hope that `convox` makes it easy to manage all your dev, staging and production environments.

---

<div class="post-metadata">

**Author:** ![phuongnd08](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/phuongnd08/32/57_2.png) [@phuongnd08](https://community.convox.com/u/phuongnd08)\
**Post date:** [March 1, 2019, 10:51am UTC](https://community.convox.com/t/20160623185456-cli-start-build-switch-improvements/375/2 "2019-03-01T10:51:45Z")

</div>

I’m having multiple rack.  
My .convox/auth is like this:

{  
“[production2-xxx.elb.amazonaws.com](http://production2-xxx.elb.amazonaws.com)”: “xxx”,  
“[production3-xxx.elb.amazonaws.com](http://production3-xxx.elb.amazonaws.com)”: “xxx”  
}

I tried:

convox rack params --rack=incorrect-name  
convox rack params --rack=production3  
CONVOX\_RACK=production3 convox rack params

All print the settings of production2 which I installed first.

Advice?

---

<div class="post-metadata">

**Author:** ![phuongnd08](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/phuongnd08/32/57_2.png) [@phuongnd08](https://community.convox.com/u/phuongnd08)\
**Post date:** [March 1, 2019, 10:56am UTC](https://community.convox.com/t/20160623185456-cli-start-build-switch-improvements/375/3 "2019-03-01T10:56:01Z")

</div>

Now updated to latest client version and this command is no longer working

convox rack install --private --vpc-cidr “5.0.0.0/16” --subnet-cidrs “5.0.1.0/24,5.0.2.0/24,5.0.3.0/24” --private-cidrs “5.0.4.0/24,5.0.5.0/24,5.0.6.0/24” --stack-name production4

What had it changed to?