Enable initial dockerized deployment #7
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
* find least viable build environment * add docker-based builder
… adding adapters for db and session store * introduce db adapters * refactor existing cosmosdb stuff into one * add a verrrrry simple memory-based one * introduce session-store adapters * refactor existing cosmosdb stuff into one * shift around secrets and reduce coupling * TCQ_CDB_SECRET is not needed anymore, because if missing defaults to in-memory-stuff
|
So it is basically done. Dockerized, ready for deployment on any infrastructure, with either persistency in CosmosDB, MongoDB or in-memory. What proved to be really challenging - but in a fun way - was the very old environment:
This is specially challenging for Apple silicon users, because there are no native pre-built NodeJS versions available < 16. So the main idea, was to use docker to have a build environment. This clearly shows, how far the eco system has progressed and what kind of vendor lock-in you get, by relying on a webpack-based tool chain. I'll explain some of my rationales in the PR myself. |
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 dockerizes the old application, while keeping changes to a minimum. It also includes AWS Copilot-enabled deployment, that currently is manually automatically deployed to https://tcq.staging.tcq-reloaded.tcq.ninja/ .
Design Goals
Non-Design Goals
In making TCQ run anywhere (just like Java :D), I had to expose internally hard-coded values as environment variables. I tried to make this basically still compatible to the old one, i.e. it still defaults to certain hard-coded stuff like
tcq.app, if certain env variables are not set.Getting rid of Azure-specific stuff, I introduced the concept of adapters, for the DB and the Session Storage, for both in the past CosmosDB has been used. Right now, both can be replaced with non-production-ready memory-based adapters. I'll add mongodb-based ones soonish and I am so far not so happy with the clunky
else-ifstructure.TODO