Import and export workflows

Please use the latest release.

Import and Export: This release includes new features for importing and exporting workflows. Importing is now a more controlled process with its own page. Before importing, you load a .aq file to see what components will be added to your instance of Aquarium. In addition, you can choose how to deal with potential conflicts. Export also has its own page, and allows you to mix and match operation types and workflows from different categories. You can also export to a Github repo, which will create an entire website for your exported workflow that you can use to document and advertise it. Workflows can be shared via the Aquarium webpage.

Documentation moved: The Aquarium documentation is now on the Aquarium webpage, except for the API autogenerated documentation, which is still managed with yard.

Improved Docker Container: A new docker container is included with this release that has a version of S3 running in it, so you no longer need to set up an AWS S3 bucket to get Aquarium up and running (although we still recommend that you use AWS S3 when scaling up your instance to a production environment). Please read the updated Docker installation instructions here under "Getting Started" > "Installation".

Minor changes:

• Bugfix: Chrome detection improved.
• Increased field value string size to 65535 (see "Migrating" notes below).
• Bugfix: New collections rows and columns are recorded upon creation.
• Improved template and system template logic

Migrating: If you are upgrading from v2.4.*, you will need to update your gems and migrate your database as follows:

bundle update
rake anemone:setup
rake db:migrate

The anemone line adds a background worker table to the database, and the migration increases the field value string size limit.