Datasette-publish-fly

- Fixed a bug with the `--plugin-secret` option when deployed using more recent versions of the `flyctl` command. Thanks, [Franz Novak](https://github.com/fndiri) and [Cade Ekblad-Frank](https://github.com/cadeef). [#29](https://github.com/simonw/datasette-publish-fly/issues/29)

- New `--setting name value` option and `--crossdb` option as a neater way of applying [Datasette settings](https://docs.datasette.io/en/stable/settings.html). [#25](https://github.com/simonw/datasette-publish-fly/issues/25)
- Exit code from `datasette publish fly` is now non-zero if the publish command fails - useful for running in CI. [20](https://github.com/simonw/datasette-publish-fly/issues/20)
- `--generate-dir` option now correctly handles relative paths, and includes plugins and templates in the generated directory structure. [18](https://github.com/simonw/datasette-publish-fly/issues/18)

- New `-o/--org` option for specifying the Fly organization to deploy to - defaults to "personal". [22](https://github.com/simonw/datasette-publish-fly/issues/22)
- Fixed bug where port no needs to be specified as an integer. [21](https://github.com/simonw/datasette-publish-fly/issues/21)

- Fixed bug where a `*.db` database file was created when an application with a volume was first deployed. [17](https://github.com/simonw/datasette-publish-fly/issues/17)

- New `--create-volume` and `--create-db` options for adding a [Fly volume](https://fly.io/docs/reference/volumes/) to the instance and creating a read-write database that will persist data between deployments. See [Using Fly volumes for writable databases](https://github.com/simonw/datasette-publish-fly/blob/1.1/README.md#using-fly-volumes-for-writable-databases) for details. [10](https://github.com/simonw/datasette-publish-fly/issues/10)
- `--generate-dir` option creates a directory with the `fly.toml` and `Dockerfile` needed for the deployment without deploying them. [13](https://github.com/simonw/datasette-publish-fly/issues/13)
- `--plugin-secret` option now stores secrets using the [Fly secrets](https://fly.io/docs/reference/secrets/) mechanism [#14](https://github.com/simonw/datasette-publish-fly/issues/14)
- Fixed to work with the latest version of the `flyctl` tool

- Now uses `--json` option to read existing application names from `flyctl apps list`. [5](https://github.com/simonw/datasette-publish-fly/issues/5)