# eve-assistant -- deployment compose file. # # This file is GENERATED: it is copied here from the private source repo by # scripts/release.sh at each release. Don't hand-edit it -- your changes are # discarded by the next `git pull`. Put your own settings in `.env`. services: app: # Rewritten by scripts/release.sh at release time. Pinned, never `latest`: # a release can carry a one-way database migration, so upgrading is # something you do deliberately (`git pull`), not something a restart does # to you. image: forge.narog.fr/eve-assistant/app:0.3.1 restart: unless-stopped ports: # Host port from .env, so a port clash does not force you to edit this # file -- which is generated and would be reverted by the next `git pull`, # silently moving the app back to 8000 and breaking the callback URL you # registered with CCP. The container side stays 8000. - "${EVE_ASSISTANT_PORT:-8000}:8000" volumes: # Holds sde.db (game reference data) and app.db (your tokens, settings, # and the latest snapshot of your assets). Both are latest-snapshot-only # with no history, and app.db is the one you cannot re-download -- back it # up before an upgrade whose release notes mention a migration. # # The container runs as uid 1000, so this directory must be writable by # that uid on the host: `mkdir -p data && chown 1000:1000 data`. - ./data:/app/data environment: # From .env -- see .env.example. The client id and secret come from YOUR # OWN application registered at developers.eveonline.com; they are not # shipped and cannot be shared between instances. - EVE_SSO_CLIENT_ID=${EVE_SSO_CLIENT_ID} - EVE_SSO_CLIENT_SECRET=${EVE_SSO_CLIENT_SECRET} - EVE_SSO_REDIRECT_URI=${EVE_SSO_REDIRECT_URI} # Identifies YOU to ESI and to mokaam.dk as the operator of this instance. # Set it: unset, your API traffic is attributed to the author and he is # the one CCP contacts if this instance misbehaves. - EVE_ASSISTANT_CONTACT_EMAIL=${EVE_ASSISTANT_CONTACT_EMAIL:-}