Add tolgee to compose stack #158
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- for the dev stack, serve tolgee on a different port - for staging, serve it on a different domain
ricardogsilva
force-pushed
the
154-add-a-frontend-translation-tool-to-the-stack-
branch
from
73a9bcc
to
aa24c58
Compare
ricardogsilva
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR integrates tolgee into the compose stack.
It adds the tolgee self-hosted version as another service. This tolgee service is included in both the dev and staging stacks.
Dev stack
When standing up the stack on dev, tolgee is accessible with the following characteristics:
localhost:8899/environmentparams in the docker compose fileStaging stack
When standing up the stack on staging, tolgee is accessible with the following characteristics:
tolgee.arpav.geobeyond.dev/