Amalgamated pipeline code
pipeline
A repository for amalgamating pipeline issue tickets and general VFB pipeline doc
Pipeline documentation:
Summary:
VFB live server info:
Rancher Cluster Documentation and backup configs
Neo4J databases:
- VFBneoKB : KnowledgeBase of annotations kept by VFB.
- VFBneoProd : Web facing Neo4J database
Endpoints:
| Endpoint | DB | Neo4j version | Bolt | r/w status | Behind VPN | Status in pipeline (test/dev/staging/prod) | backup link |
|---|---|---|---|---|---|---|---|
| kbw.virtualflybrain.org:7474 | VFBneoKB | Neo4j 3,n | y | r/w | Y | prod | backup/deploy |
| kb.virtualflybrain.org | VFBNeoKB | Neo4j 3.n | Y | read only | N | ? | update |
| pdb.virtualflybrain.org | VFBNeoProd | Neo4j 2.n | NS | read only | N | prod? |
...
TODO:
- Document relaionship kb to kbw
- If we have test instances for production, which front end server are they currently used by. Would be very handy to keep this up-to-date.
OWL servers:
AberOWL:
| Endpoint | Status in pipeline (test/dev/staging/production) |
|---|---|
| http://owl.virtualflybrain.org/api/runQuery.groovy? | production |
SOLR servers:
front end:
virtualflybrain.org - live VFB 1.5
VFB 1.5 Site Deployment Documentation
v2.virtualflybrain.org - live VFB 2.0
GitHub branches for server code
TODO: Doc branch -> front end relationship (this should probably be on geppetto-vfb repo)