Skip to content

Conversation

@grantfitzsimmons
Copy link
Member

This was motivated by moving to AWS in Docker, but we might as well properly support deploying the Web Portal this way. This is more tuned for development than it is for production use, and we need to package this and bake everything into the image on Docker Hub. For SSL, we should use a dedicated reverse proxy container and not manage Nginx in the webportal service and SSL on the host.

For now, this is an improvement over installing locally and building the portals as we had in the past.

version: "3.8"

services:
  webportal:
    build:
      context: .
      dockerfile: Dockerfile
    image: webportal-service:improve-build
    container_name: webportal
    ports:
      - "80:80"
      - "443:443"
    volumes:
      # Project files
      - .:/home/specify/webportal-installer

      # SSL and certs
      - /etc/letsencrypt/live/webportal.specifycloud.org:/etc/nginx/ssl
      - /etc/letsencrypt:/etc/letsencrypt
      - /etc/ssl/certs/dhparam.pem:/etc/ssl/certs/dhparam.pem

      # Static content
      - /var/www:/var/www

      # Specify exports and customizations
      # - ./specify_exports:/home/specify/webportal-installer/specify_exports
      # - ./custom_settings:/home/specify/webportal-installer/custom_settings

      # Custom images
      - ./custom-images:/home/specify/

    restart: unless-stopped

@grantfitzsimmons grantfitzsimmons changed the base branch from improve-build to master May 7, 2025 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants