Custom config directory with custom site location creates unexpected search path when pushing site

Project structure:

project/
|--deploy_config/
|--stage/
|--s3_website.yml
|--prod/
|--s3_website.yml
|--public/
|--index.html
|--assets/
|-- <... etc>

deploy_config/stage/s3_website.yml contents:
```
...
site: public
...
```

Push command:

s3_website push --config-dir=deploy_config/stage

Result:

[fail] Could not load the site:
       Could not find a website. (The site setting in s3_website.yml points to a non-existing file deploy_config/stage/public)
       Either use the --site=DIR command-line argument or define the location of the site in s3_website.yml.

       Here's an example of how you can define the site directory in s3_website.yml:
          site: dist/website

Expected results:

I would expect the push to work.
I'd expect the working directory in this case to be the project root, and not relative to my config dir, as the error message suggests.
OR I'd expect the error message to at least tell me I need to specify the site dir as ../../public in the config if that's the intended behavior.

Current workaround:

The solution is indeed to configure the site dir as site: ../../public in s3_website.yml, but this seems counterintuitive based on the docs.

laurilehmijoki / s3_website

Custom config directory with custom site location creates unexpected search path when pushing site #296