wormbase / down Goto Github PK

Ensure dependencies are up-to-date.
Ensure coding style is consistent with that employed in pseudoace.

This cannot be done until hosting of the application is decided upon, since the cloudwatch config requires association of an IAM instance profile.

If deployed under Elastic Beanstalk, then this could easily be added, since beanstalk creates instances on demand at deployment/environment creation time.

Otherwise, we'd need to ensure that such an IAM role is provided at instance creation time for hosting this.

Currently, the EC2 instance being (re-)used for testing this project (The db-migration instance) does not have an instance profile, thus cloudwatch cannot be configured and tested at present.

This project contains a rest API (http routes); this is now provided by the datomic-to-catalyst project
(which was originally extracted from the project from which this project derives).

If it's desired to have a rest api on top of say "geenace", the we should make it possible to deploy datomic-to-catalyst against a given datomic uri (if it's not already).

In the new year (or even over my holiday), I plan to spin up an instance to replace the legacy curation.wormbase.org ec2 instance (currently stopped) with an EC2 instance spun up using elasticbeanstalk.

The infrastructure we have for this is identical to the way the datomic-to-catlyst REST API is deployed (Makefile, Docker, ECR, S3 and EC2, via Elasticbeanstalk).

For those who don't know, this repo contains a version of Thomas's TrACe Viewer and Colonnade tools, modified to have updated clojure dependencies, some code cleanup and notably:

• no ability to edit
• no requirement to login

It'd be nice to have the tools running for the purpose of exploring the migrated datomic WormBase database.

In particular, Colonnade provides a "table maker" style query builder UI that produces the datalog requried to construct queries - I think this would be a useful tool for the developers of the REST API going forward.

More generally, having a tool to explore the data that's a bit more friendly (and aware of the ACeDB schema) that the native datomic console application would also be of benefit to all.

Questions

1. How do we want to access these web "curation" tools?
   a) Do we still want to use curation.wormbase.org?
   b) Would a random elasticbeanstalk URL suffice?
   datomic-to-catalyst uses the generated elasticbeanstalk URL (which can change depending on what's changed in the elasticbeanstalk "environment") - an example of what the generated looks like is: datomic-to-catalyst.a26ahpitsj.us-east-1.elasticbeanstalk.com

In order for the domain curaiton.wormbase.org to map to the ec2 instance that will be spun up via elasticbeanstalk, it would need custom DNS routing using AWS's Route53 service to map to the elasticbeanstalk subdomain.