Release 1.8.0

New in 1.8.0

• Update key generation with separate features to set secrets and restart the apps
• Fixed the stop behavior to correctly set the scaling to 0
• Differentiate correctly absent machines from existing suspended ones
• Correctly compare version numbers.

https://owlcms-cloud.fly.dev

Release 1.7.0

New in 1.7.0

• Operations now shown in a popup dialog.
• Tracker now show shown before legacy publicresults

https://owlcms-cloud.fly.dev

owlcms-cloud 1.6.0

Added Tracker as deployable

https://owlcms-cloud.fly.dev

1.5.1

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.4.4

• Now uses the GitHub API to fetch the latest release.

1,4,4

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.4.3

Uses a pin map updated twice daily. Pins are the average of locations in a given city (one pin per city)

1.4.3

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.4.2

• Now links to a clustered usage map that is updated twice daily

Release 1.4.2

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.4.1

• Caption for the usage map modified.

Release 1.4.1

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.3.0

• Radical solution to the database connection issue. The provided fly postgres attach command fails with timeouts, so we now create the database connection ourselves.

Release 1.3

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.0.11

• Application creation works again (creation scripts were not being found)

Release 1.0.11

The application is deployed in the cloud at https://owlcms-cloud.fly.dev/

Changes since 1.0.10

• Further actions to fix a problem that cause the postgres database not to be attached to the application
• ACTIONS REQUIRED: Export your existing database; delete the owlcms application; recreate the application; reload the database