{"id":15937473,"url":"https://github.com/andersy005/yellowstone-deploy","last_synced_at":"2025-09-10T13:35:26.161Z","repository":{"id":96025563,"uuid":"156759282","full_name":"andersy005/yellowstone-deploy","owner":"andersy005","description":null,"archived":false,"fork":false,"pushed_at":"2018-11-08T19:48:02.000Z","size":27,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-28T23:38:00.139Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Jupyter Notebook","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/andersy005.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-11-08T19:38:27.000Z","updated_at":"2018-11-08T19:48:04.000Z","dependencies_parsed_at":null,"dependency_job_id":"8a8d1982-5af8-4fa2-99d1-a9a797a9676c","html_url":"https://github.com/andersy005/yellowstone-deploy","commit_stats":{"total_commits":2,"total_committers":1,"mean_commits":2.0,"dds":0.0,"last_synced_commit":"52a3a330fc60157aa796e0b5f6730c7364c1c17a"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/andersy005%2Fyellowstone-deploy","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/andersy005%2Fyellowstone-deploy/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/andersy005%2Fyellowstone-deploy/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/andersy005%2Fyellowstone-deploy/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/andersy005","download_url":"https://codeload.github.com/andersy005/yellowstone-deploy/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247070782,"owners_count":20878581,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-07T05:03:09.682Z","updated_at":"2025-04-03T19:44:33.940Z","avatar_url":"https://github.com/andersy005.png","language":"Jupyter Notebook","funding_links":[],"categories":[],"sub_categories":[],"readme":"# About\n\nThis repository contains the reproducible configuration for deploying a Pangeo\ninstance on Google Kubernetes Engine.\n\nIt contains scripts to automatically redeploy when the image definition or\nchart parameters are changed.\n\n# Setup\n\nThe first step to using this automation is to create a Kubernetes cluster and\ninstall the server-side component Tiller on it (used for deploying applications\nwith the Helm tool). Scripts to do so can be found here:\nhttps://github.com/pangeo-data/pangeo/tree/master/gce/setup-guide\n\n* Modify the script `gce-pangeo-environment.sh` with the parameters for your deployment\n* Run the following scripts:\n```\n. gce-pangeo-environment.sh\n./1_create_cluster.sh\n./2_configure_kubernetes.sh\n```\n\n## Install git-crypt\n\nYou will need to install\n[`git-crypt`](https://www.agwa.name/projects/git-crypt/). `git-crypt` is used\nto encrypt the secrets that are used for deploying your cluster. Please read this [HOW GIT-CRYPT WORKS](https://www.agwa.name/projects/git-crypt/) if new to it. \n\n# Configure this repository\n\nOnce you have a cluster created, you can begin customizing the configuration.\n\n* Create a fork of this repository in GitHub. (Note: the default branch is staging)\n* Copy the deployments/example.pangeo.io directory to your desired name\n  * `cp -r example.pangeo.io newname.pangeo.io`\n* Regenerate the git-crypt key. This will be used to encrypt the secrets\nthat are used for your deployment.\n  * `git crypt init`\n* Create a CircleCI job for the repo. \n  * Log in or Sign up [here](https://circleci.com). Go to [dashboard](https://circleci.com/dashboard). \n  * Click add project under your github account name. \n  * Click Set Up Project for the example.pangeo.io-deploy repo. Click Linux. Click Start building at bottom. \n  * You will need to add the below environmental variables to your CircleCI configuration:\n\n| Name | Description |\n| ---- | ----------- |\n| GCR_READWRITE_KEY | The JSON output of `gcloud iam service-accounts keys create` (ask Pangeo administrator to configure this) |\n| GIT_CRYPT_KEY | The base64 encoded output of `git crypt export-key key.txt` Then run `base64 key.txt` to get pipe the key to standard output. Copy past into the env var. Delete `key.txt` afterwards!|\n| GKE_CLUSTER | The name that your cluster was created with |\n| GOOGLE_PROJECT | The identifier of the project where your cluster was created |\n| GOOGLE_REGION | The Google compute region where your cluster is located (e.g. us-central1) |\n| GOOGLE_ZONE | The Google compute zone where your cluster is located (e.g. us-central1-b) |\n| IMAGE_NAME | The container registry image to build and use for your notebook and worker containers (e.g. us.gcr.io/pangeo-181919/example-pangeo-io-notebook). See [documentation](https://cloud.google.com/container-registry/) for setting up with your own project. Note: you need write permisson for this project. You will also have to give permisson (Storage Admin, Kubernetes Engine Admin, and Viewer) to the circleCI service account on the container registry ([see doc](https://cloud.google.com/container-registry/docs/access-control)). Then enable the registry API [here](https://console.cloud.google.com/flows/enableapi?apiid=containerregistry.googleapis.com\u0026redirect=https://cloud.google.com/container-registry/docs/quickstart\u0026_ga=2.12214260.-1113544925.1533776076)|\n| DEPLOYMENT | The name of the directory in `deployments` you wish to deploy (e.g., example.pangeo.io) |\n\n* Make a commit to test if the job succeeded on circleCI. If it failed troubleshoot it. \n\n# Common Issues\n\n* `Error: could not find a ready tiller pod` Some times it takes a while to download the new tiller image, wait and try again.\n* `Error: UPGRADE FAILED: \"example.pangeo.io-staging\" has no deployed releases` If your first deploy of an application fails. Run `helm delete polar.pangeo.io-staging --purge` anywhere you have run `gcloud container clusters get-credentials`\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fandersy005%2Fyellowstone-deploy","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fandersy005%2Fyellowstone-deploy","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fandersy005%2Fyellowstone-deploy/lists"}