Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes setup #269

Merged
merged 10 commits into from
May 18, 2024
Merged

Kubernetes setup #269

merged 10 commits into from
May 18, 2024

Conversation

rhit-zhangam
Copy link
Member

Copied most files from our working kubernetes setup, somewhat messy.
This version is built off of an older firebase version, rather than mongodb. However, it does support running multiple experiments in parallel, kind of like a minimal viable product version.

Along with this, tag v1.0.9 contains the main branch version that has mongodb migrated and frontend improvements, but no kubernetes support. This is done as we are still in the process of combining features, so it's kept as reference.

@rhit-zhangam rhit-zhangam force-pushed the kubernetes-setup branch 6 times, most recently from 91aa4d6 to 9229614 Compare May 15, 2024 20:06
@rhit-zhangam
Copy link
Member Author

Redid some CI Github Actions for more basic Dockerfiles, as we shift away from docker-compose. Also, adjusted pylint to check python code in both runner and backend.

Copy link
Collaborator

@rhit-leey2 rhit-leey2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently the main (+ tag version) does not have the mongo db migrated yet, but I'll approve this

@rhit-leey2 rhit-leey2 added this pull request to the merge queue May 18, 2024
Merged via the queue into main with commit ed76adf May 18, 2024
5 checks passed
@rhit-leey2 rhit-leey2 deleted the kubernetes-setup branch May 18, 2024 00:02
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.

3 participants