Deployment adjustments for templates

[esteinig]

Dev deployment mode should be able to access the templates from the repository (docker-compose.yml - cerebro_api)

volumes:
  {{#if dev }}
  # Path mount for application in development
  - {{{ dev }}}:/usr/src/cerebro
  - {{{ dev }}}/templates/email:/data/templates/email:ro
  - {{{ dev }}}/templates/report:/data/templates/report:ro
  {{else}}
  # Volume mount for application in production deployment
  - cerebro_api:/data
  - {{{ outdir }}}/templates/email:/data/templates/email:ro
  - {{{ outdir }}}/templates/report:/data/templates/report:ro
  {{/if}}

Dockerfile.server that is deployed currently does not include PDF compiler testing - this is necessary to load dependent LaTeX packages so that the first report generation takes little time. However - currently the Docker container user needs to be root for this to access rott installed system dependencies for tectonic.

ENV PATH="${PATH}:/opt/cerebro/bin"
RUN cargo build --release --features pdf && cp target/release/cerebro /opt/cerebro/bin
WORKDIR /opt/cerebro

RUN cerebro report compile --base-config /usr/src/cerebro/templates/report/report.toml --output test.pdf --pdf && rm test.pdf

Perhaps we can implement sudo install of dependencies with container user and remove sudo access when built?

[esteinig]

This will need some more thought when deploying development versions to the web server

[esteinig]

Some other issues here:

• [x] add api and app subdomains as param in stack config
• [x] change template directory moutns for complete mounts in docker-compose.yml

[esteinig]

Closing this, being addressed in the larger project scope of issue #4