summaryrefslogtreecommitdiff
path: root/issues/genenetwork/containerising-production-issues.gmi
blob: 6648554ce49ab4b44607410b0b8ad21304649b4d (about) (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
# Containerising Production: Issues

## Tags

* type: bug
* status: open
* assigned: fredm
* priority: critical
* keywords: production, container, tux04
* interested: alexk, aruni, bonfacem, fredm, pjotrp, soloshelby, zsloan, jnduli

## Description

We have recently got production into a container and deployed it: It has come up, however, that there are services that are useful to get a full-featured GeneNetwork system running that are not part of the container.

This is, therefore, a meta-issue, tracking all issues that relate to the deployment of the disparate services that make up GeneNetwork.

## Documentation

=> https://issues.genenetwork.org/topics/genenetwork/genenetwork-services

The link above documents the various services that make up the GeneNetwork service.

## Issues

* [x] Move user directories to a large partition
=> ./handle-tmp-dirs-in-container [ ] Link TMPDIR in container to a directory on a large partition
=> ./markdown-editing-service-not-deployed [ ] Define and deploy Markdown Editing service
=> ./umhet3-samples-timing-slow [ ] Figure out and fix UM-HET3 Samples mappings on Tux04
=> ./setup-mailing-on-tux04 [x] Setting up email service on Tux04
=> ./virtuoso-shutdown-clears-data [x] Virtuoso seems to lose data on restart
=> ./python-requests-error-in-container [ ] Fix python's requests library certificates error