-
Notifications
You must be signed in to change notification settings - Fork 32
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
csiro.pangeo.io ? #285
Comments
Hi @jmunroe! While this is certainly possible, and there are some benefits to having things consolidated, there are some downsides as well:
So, it might make more sense to create a fork and deploy separately? In theory, the only manual step is creating a circleci project with your own GIT_CRYPT_KEY (https://github.com/pangeo-data/pangeo-cloud-federation/blob/staging/.circleci/config.yml#L145). Other groups are going this route. here are some related issues: #32, #39, #181, #263 |
Actually this can be configured separately for each hub. |
I am going down the route of forking and deploying separately. I've been able to copy and modify a previous deployment, got git_crypt working, set things up with CircleCI, built the image. Currently trying to get helm (hubploy deploy) to successfully complete. I'll post here if I hit a blocking issue. Thanks. |
Both the staging and prod deployments for pangeo-csiro are are now working. I think the NFS storage is working and I still need to test out the dask worker scaling. Thanks so much @scottyhq ! I've been mostly successfully by trying to replicate a good chunk of what you have recently been doing. |
I've been working on deploying an AWS-based (using EKS and eksctl, on ap-southeast-2) Pangeo JupyterHub for CSIRO. Rather than duplicating efforts in a separate repo, perhaps a better way forward is to integrate my efforts within this repository? Would it be appropriate to hang a csiro subdomain off of pangeo.io ?
The text was updated successfully, but these errors were encountered: