1.3.1

• Fixed a bug with the --plugin-secret option when deployed using more recent versions of the flyctl command. Thanks, Franz Novak and Cade Ekblad-Frank. #29

1.3

• New --setting name value option and --crossdb option as a neater way of applying Datasette settings. #25
• Exit code from datasette publish fly is now non-zero if the publish command fails - useful for running in CI. #20
• --generate-dir option now correctly handles relative paths, and includes plugins and templates in the generated directory structure. #18

1.2

• New -o/--org option for specifying the Fly organization to deploy to - defaults to "personal". #22
• Fixed bug where port no needs to be specified as an integer. #21

1.1.1

• Fixed bug where a *.db database file was created when an application with a volume was first deployed. #17

1.1

• New --create-volume and --create-db options for adding a Fly volume to the instance and creating a read-write database that will persist data between deployments. See Using Fly volumes for writable databases for details. #10
• --generate-dir option creates a directory with the fly.toml and Dockerfile needed for the deployment without deploying them. #13
• --plugin-secret option now stores secrets using the Fly secrets mechanism #14
• Fixed to work with the latest version of the flyctl tool

1.0.2

• Now uses --json option to read existing application names from flyctl apps list. #5

1.0.1

• Fixed various errors that occurred when using latest version of flyctl. #7

1.0

• Fixed compatibility with Datasette 0.44. #6
• Fix for Python 3.6. #4

0.2

• First non-alpha release
• Fixed bug when flyctl returns an upgrade message. #3

0.1a

• First working version