Using --project-dir option

When deploying a package this works fine to deploy a package:

```
$ cd quickdraw-lambdas/
$ chalice deploy --no-autogen-policy
```

but this does not:

```
$ cd ..
$ chalice --project-dir "quickdraw-lambdas/" deploy --no-autogen-policy
```

I get the error message:

`FileNotFoundError: [Errno 2] No such file or directory: 'quickdraw-lambdas/.chalice/config.json'`

Even though that file exists:

```
$ ll quickdraw-lambdas/.chalice/config.json
-rw-rw-r-- 1 jim jim 129 Aug 18 21:07 quickdraw-lambdas/.chalice/config.json
```

I can change that directory to an absolute path to make it work but I want it to be relative. I do see issue #414 . Is it supposed to work this way? Is there a way to specify a relative path?

Thanks

Start by reproducing the deploy command from the parent directory with --project-dir, then inspect how the Chalice CLI resolves .chalice/config.json relative to that option. Done means a relative project directory locates its existing config.json and deployment proceeds without requiring an absolute path.

Written by the indexing model from the issue text.