Adding first shot at drift server #112
Open
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
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
we were close to getting to a deployment, but our app (drift-server) had an error with the database string we want to debub this first and then come back to test again. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
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.
@alecbcs is working on a drift analysis for spack (or BUILD SI) and part of that requires deploying this drift server:
https://github.com/buildsi/drift-server
We have a PR underway that is going to do an automated build for the container base:
https://github.com/buildsi/drift-server/pull/7
and our plan is to create an AWS database to connect to (via the
DRIFTSERVER_DATABASE_DSNthat is a secret). We will also define some username and password (also secrets) that have permission to write to it.In terms of the kubernetes yaml recipes, I took my best effort first shot here! The container basically runs the app when you run it on port 8080, so it shouldn't need to look very different than the other spack webby things. I'm thinking before this gets added here so it's automated, we probably want to get the container deployed, create the database, and then test our deploying the files from our local machines. If that works, then would adding the recipes here automate it (but we would still need to deploy our secrets from our local machines?)
@opadron if you have maybe 30 minutes next week (and think it would be fun) I think this could be a fun way for @alecbcs and I to meet up with you and walk through the steps of interacting with kubernetes to test this out. Hey, maybe we might even be useful someday! 馃槅
Signed-off-by: vsoch vsoch@users.noreply.github.com