diff --git a/.nojekyll b/.nojekyll index b2e1ef2e0..6a84fa5f5 100644 --- a/.nojekyll +++ b/.nojekyll @@ -1 +1 @@ -03b9f0e5 \ No newline at end of file +01eec242 \ No newline at end of file diff --git a/admins/howto/managing-multiple-user-image-repos.html b/admins/howto/managing-multiple-user-image-repos.html index f82c70267..8b69b8481 100644 --- a/admins/howto/managing-multiple-user-image-repos.html +++ b/admins/howto/managing-multiple-user-image-repos.html @@ -431,7 +431,7 @@

Managing multiple user image repos

Managing user image repos

Since we have many multiples of user images in their own repos, managing these can become burdensome… Particularly if you need to make changes to many or all of the images.

-

For this, we have aa tool named manage-repos.

+

For this, we have a tool named manage-repos.

manage-repos uses a config file with a list of all of the git remotes for the image repos (repos.txt) and will allow you to perform basic git operations (sync/rebase, clone, branch management and pushing).

The script “assumes” that you have all of your user images in their own sub-folder (in my case, $HOME/src/images/...).

@@ -586,7 +586,7 @@

Usage examples

Clone all of the image repos to a common directory:

manage-repos --destination ~/src/images/ --config /path/to/repos.txt clone

Clone all repos, and set upstream and origin for your fork:

-
manage-repos --destination ~/src/images/ --config /path/to/repos.txt clone --set-origin --github-user <username>
+
manage-repos --destination ~/src/images/ --config /path/to/repos.txt clone --set-remote --github-user <username>

Sync all repos from upstream and push to your origin:

manage-repos --destination ~/src/images/ --config /path/to/repos.txt sync --push

Create a feature branch in all of the repos:

diff --git a/incidents/index.html b/incidents/index.html index 8e9367c68..8caa52524 100644 --- a/incidents/index.html +++ b/incidents/index.html @@ -508,7 +508,7 @@

Incident Reports

- + Feb 9, 2017 @@ -516,7 +516,7 @@

Incident Reports

JupyterHub db manual overwrite - + Feb 24, 2017 @@ -524,7 +524,7 @@

Incident Reports

Custom Autoscaler gonee haywire - + Feb 24, 2017 @@ -532,7 +532,7 @@

Incident Reports

Proxy eviction strands user - + Mar 6, 2017 @@ -540,7 +540,7 @@

Incident Reports

Non-matching hub image tags cause downtime - + Mar 20, 2017 @@ -548,7 +548,7 @@

Incident Reports

Too many volumes per disk leave students stuck - + Mar 23, 2017 @@ -556,7 +556,7 @@

Incident Reports

Weird upstream ipython bug kills kernels - + Apr 3, 2017 @@ -564,7 +564,7 @@

Incident Reports

Custom autoscaler does not scale up when it should - + May 9, 2017 @@ -572,7 +572,7 @@

Incident Reports

Oops we forgot to pay the bill - + Oct 10, 2017 @@ -580,7 +580,7 @@

Incident Reports

Docker dies on a few Azure nodes - + Oct 19, 2017 @@ -588,7 +588,7 @@

Incident Reports

Billing confusion with Azure portal causes summer hub to be lost - + Jan 25, 2018 @@ -596,7 +596,7 @@

Incident Reports

Accidental merge to prod brings things down - + Jan 26, 2018 @@ -604,7 +604,7 @@

Incident Reports

Hub starts up very slow, causing outage for users - + Feb 6, 2018 @@ -612,7 +612,7 @@

Incident Reports

Azure PD refuses to detach, causing downtime for data100 - + Feb 28, 2018 @@ -620,7 +620,7 @@

Incident Reports

A node hangs, causing a subset of users to report issues - + Jun 11, 2018 @@ -628,7 +628,7 @@

Incident Reports

Azure billing issue causes downtime - + Feb 25, 2019 @@ -636,7 +636,7 @@

Incident Reports

Azure Kubernetes API Server outage causes downtime - + May 1, 2019 @@ -644,7 +644,7 @@

Incident Reports

Service Account key leak incident - + Jan 20, 2022 @@ -652,7 +652,7 @@

Incident Reports

Hubs throwing 505 errors - + Feb 1, 2024 diff --git a/search.json b/search.json index 12fc16252..b98646464 100644 --- a/search.json +++ b/search.json @@ -490,7 +490,7 @@ "href": "admins/howto/managing-multiple-user-image-repos.html", "title": "Managing multiple user image repos", "section": "", - "text": "Since we have many multiples of user images in their own repos, managing these can become burdensome… Particularly if you need to make changes to many or all of the images.\nFor this, we have aa tool named manage-repos.\nmanage-repos uses a config file with a list of all of the git remotes for the image repos (repos.txt) and will allow you to perform basic git operations (sync/rebase, clone, branch management and pushing).\nThe script “assumes” that you have all of your user images in their own sub-folder (in my case, $HOME/src/images/...).", + "text": "Since we have many multiples of user images in their own repos, managing these can become burdensome… Particularly if you need to make changes to many or all of the images.\nFor this, we have a tool named manage-repos.\nmanage-repos uses a config file with a list of all of the git remotes for the image repos (repos.txt) and will allow you to perform basic git operations (sync/rebase, clone, branch management and pushing).\nThe script “assumes” that you have all of your user images in their own sub-folder (in my case, $HOME/src/images/...).", "crumbs": [ "Using DataHub", "Contributing to DataHub", @@ -503,7 +503,7 @@ "href": "admins/howto/managing-multiple-user-image-repos.html#managing-user-image-repos", "title": "Managing multiple user image repos", "section": "", - "text": "Since we have many multiples of user images in their own repos, managing these can become burdensome… Particularly if you need to make changes to many or all of the images.\nFor this, we have aa tool named manage-repos.\nmanage-repos uses a config file with a list of all of the git remotes for the image repos (repos.txt) and will allow you to perform basic git operations (sync/rebase, clone, branch management and pushing).\nThe script “assumes” that you have all of your user images in their own sub-folder (in my case, $HOME/src/images/...).", + "text": "Since we have many multiples of user images in their own repos, managing these can become burdensome… Particularly if you need to make changes to many or all of the images.\nFor this, we have a tool named manage-repos.\nmanage-repos uses a config file with a list of all of the git remotes for the image repos (repos.txt) and will allow you to perform basic git operations (sync/rebase, clone, branch management and pushing).\nThe script “assumes” that you have all of your user images in their own sub-folder (in my case, $HOME/src/images/...).", "crumbs": [ "Using DataHub", "Contributing to DataHub", @@ -529,7 +529,7 @@ "href": "admins/howto/managing-multiple-user-image-repos.html#usage", "title": "Managing multiple user image repos", "section": "Usage", - "text": "Usage\n\nOverview of git operations included in manage-repos:\nmanage-repos allows you to perform basic git operations on a large number of similar repositories:\n\nbranch: Create a feature branch\nclone: Clone all repositories in the config file to a location on the filesystem specified by the --destination argument.\npatch: Apply a git patch to all repositories in the config file.\npush: Push a branch from all repos to a remote. The remote defaults to origin.\nstage: Performs a git add and git commit to stage changes before pushing.\nsync: Sync all of the repositories, and optionally push to your fork.\n\n\n\nUsage overview\nThe following sections will describe in more detail the options and commands available with the script.\n\nPrimary arguments for the script\n$ manage-repos.py --help\n\npositional arguments:\n {branch,clone,patch,push,stage,sync}\n Command to execute. Additional help is available for each command.\n\noptions:\n -h, --help show this help message and exit\n -c CONFIG, --config CONFIG\n Path to file containing list of repositories to operate on.\n -d DESTINATION, --destination DESTINATION\n Location on the filesystem of the managed repositories. If the directory does not exist, it will be created. Defaults to the current working directory.\n--config is required, and setting --destination is recommended.\n\n\n\nSub-commands\n\nbranch\n$ manage-repos branch --help\nusage: manage-repos branch [-h] [-b BRANCH]\n\noptions:\n -h, --help show this help message and exit\n -b BRANCH, --branch BRANCH\n Name of the new feature branch to create.\nThe feature branch to create is required, and the tool will switch to main before creating and switching to the new branch.\n\n\nclone\n$ manage-repos.py clone --help\nusage: manage-repos clone [-h] [-s] [-g GITHUB_USER]\n\nClone repositories in the config file and optionally set a remote for a fork.\n\noptions:\n -h, --help show this help message and exit\n -s, --set-remote Set the user's GitHub fork as a remote.\n -r REMOTE, --remote REMOTE\n If --set-remote is used, override the name of the remote to set for the fork. This is optional and defaults to 'origin'.\n -g GITHUB_USER, --github-user GITHUB_USER\n The GitHub username of the fork to set in the remote.\nThis command will clone all repositories found in the config, and if you’ve created a fork, use the --set-remote and --github-user arguments to update the remotes in the cloned repositories. This will set the primary repository’s remote to upstream and your fork to origin (unless you override this by using the --remote argument).\nAfter cloning, git remote -v will be executed for each repository to allow you to confirm that the remotes are properly set.\n\n\npatch\n$ manage-repos patch --help\nusage: manage-repos patch [-h] [-p PATCH]\n\nApply a git patch to managed repositories.\n\noptions:\n -h, --help show this help message and exit\n -p PATCH, --patch PATCH\n Path to the patch file to apply.\nThis command applies a git patch file to all of the repositories. The patch is created by making changes to one file, and redirecting the output of git diff to a new file, eg:\ngit diff <filename> > patchfile.txt\nYou then provide the location of the patch file with the --patch argument, and the script will attempt to apply the patch to all of the repositories.\nIf it is unable to apply the patch, the script will continue to run and notify you when complete which repositories failed to accept the patch.\n\n\npush\n$ manage-repos push --help\nusage: manage-repos push [-h] [-b BRANCH] [-r REMOTE]\n\nPush managed repositories to a remote.\n\noptions:\n -h, --help show this help message and exit\n -b BRANCH, --branch BRANCH\n Name of the branch to push.\n -r REMOTE, --remote REMOTE\n Name of the remote to push to. This is optional and defaults to 'origin'.\nThis command will attempt to push all staged commits to a remote. The --branch argument is required, and will be the name of the feature branch. The remote that is pushed to defaults to origin, but you can override this with the --remote argument.\n\n\nstage\n$ manage-repos stage --help\nusage: manage-repos stage [-h] [-f FILES [FILES ...]] [-m MESSAGE]\n\nStage changes in managed repositories. This performs a git add and commit.\n\noptions:\n -h, --help show this help message and exit\n -f FILES [FILES ...], --files FILES [FILES ...]\n List of files to stage in the repositories. Optional, and defaults to all modified files in the repository\n -m MESSAGE, --message MESSAGE\n Commit message to use for the changes.\nstage combines both git add ... and git commit -m, adding and committing one or more files to the staging area before you push to a remote.\nThe commit message must be a text string enclosed in quotes.\nBy default, --files is set to ., which will add all modified files to the staging area. You can also specify any number of files, separated by a space.\n\n\nsync\n$ manage-image-repos.py sync --help\nusage: manage-repos sync [-h] [-b BRANCH_DEFAULT] [-u UPSTREAM] [-p] [-r REMOTE]\n\nSync managed repositories to the latest version using 'git rebase'. Optionally push to a remote fork.\n\noptions:\n -h, --help show this help message and exit\n -b BRANCH_DEFAULT, --branch-default BRANCH_DEFAULT\n Default remote branch to sync to. This is optional and defaults to 'main'.\n -u UPSTREAM, --upstream UPSTREAM\n Name of the parent remote to sync from. This is optional and defaults to 'upstream'.\n -p, --push Push the locally synced repo to a remote fork.\n -r REMOTE, --remote REMOTE\n The name of the remote fork to push to. This is optional and defaults to 'origin'.\nThis command will switch your local repositories to the main branch, and sync all repositories from the config to your device from a remote. With the --push argument, it will push the local repository to another remote.\nBy default, the script will switch to the main branch before syncing, and can be overridden with the --branch-default argument.\nThe primary remote that is used to sync is upstream, but that can also be overridden with the --upstream argument. The remote for a fork defaults to origin, and can be overridden via the --remote argument.\n\n\n\nUsage examples\nClone all of the image repos to a common directory:\nmanage-repos --destination ~/src/images/ --config /path/to/repos.txt clone\nClone all repos, and set upstream and origin for your fork:\nmanage-repos --destination ~/src/images/ --config /path/to/repos.txt clone --set-origin --github-user <username>\nSync all repos from upstream and push to your origin:\nmanage-repos --destination ~/src/images/ --config /path/to/repos.txt sync --push\nCreate a feature branch in all of the repos:\nmanage-repos -c /path/to/repos.txt -d ~/src/images branch -b test-branch\nCreate a git patch and apply it to all image repos:\ngit diff envorinment.yml > /tmp/git-patch.txt\nmanage-repos -c /path/to/repos.txt -d ~/src/images patch -p /tmp/git-patch.txt\nOnce you’ve tested everything and are ready to push and create a PR, add and commit all modified files in the repositories:\nmanage-repos -c /path/to/repos.txt -d ~/src/images stage -m \"this is a commit\"\nAfter staging, push everything to a remote:\nmanage-repos -c repos.txt -d ~/src/images push -b test-branch", + "text": "Usage\n\nOverview of git operations included in manage-repos:\nmanage-repos allows you to perform basic git operations on a large number of similar repositories:\n\nbranch: Create a feature branch\nclone: Clone all repositories in the config file to a location on the filesystem specified by the --destination argument.\npatch: Apply a git patch to all repositories in the config file.\npush: Push a branch from all repos to a remote. The remote defaults to origin.\nstage: Performs a git add and git commit to stage changes before pushing.\nsync: Sync all of the repositories, and optionally push to your fork.\n\n\n\nUsage overview\nThe following sections will describe in more detail the options and commands available with the script.\n\nPrimary arguments for the script\n$ manage-repos.py --help\n\npositional arguments:\n {branch,clone,patch,push,stage,sync}\n Command to execute. Additional help is available for each command.\n\noptions:\n -h, --help show this help message and exit\n -c CONFIG, --config CONFIG\n Path to file containing list of repositories to operate on.\n -d DESTINATION, --destination DESTINATION\n Location on the filesystem of the managed repositories. If the directory does not exist, it will be created. Defaults to the current working directory.\n--config is required, and setting --destination is recommended.\n\n\n\nSub-commands\n\nbranch\n$ manage-repos branch --help\nusage: manage-repos branch [-h] [-b BRANCH]\n\noptions:\n -h, --help show this help message and exit\n -b BRANCH, --branch BRANCH\n Name of the new feature branch to create.\nThe feature branch to create is required, and the tool will switch to main before creating and switching to the new branch.\n\n\nclone\n$ manage-repos.py clone --help\nusage: manage-repos clone [-h] [-s] [-g GITHUB_USER]\n\nClone repositories in the config file and optionally set a remote for a fork.\n\noptions:\n -h, --help show this help message and exit\n -s, --set-remote Set the user's GitHub fork as a remote.\n -r REMOTE, --remote REMOTE\n If --set-remote is used, override the name of the remote to set for the fork. This is optional and defaults to 'origin'.\n -g GITHUB_USER, --github-user GITHUB_USER\n The GitHub username of the fork to set in the remote.\nThis command will clone all repositories found in the config, and if you’ve created a fork, use the --set-remote and --github-user arguments to update the remotes in the cloned repositories. This will set the primary repository’s remote to upstream and your fork to origin (unless you override this by using the --remote argument).\nAfter cloning, git remote -v will be executed for each repository to allow you to confirm that the remotes are properly set.\n\n\npatch\n$ manage-repos patch --help\nusage: manage-repos patch [-h] [-p PATCH]\n\nApply a git patch to managed repositories.\n\noptions:\n -h, --help show this help message and exit\n -p PATCH, --patch PATCH\n Path to the patch file to apply.\nThis command applies a git patch file to all of the repositories. The patch is created by making changes to one file, and redirecting the output of git diff to a new file, eg:\ngit diff <filename> > patchfile.txt\nYou then provide the location of the patch file with the --patch argument, and the script will attempt to apply the patch to all of the repositories.\nIf it is unable to apply the patch, the script will continue to run and notify you when complete which repositories failed to accept the patch.\n\n\npush\n$ manage-repos push --help\nusage: manage-repos push [-h] [-b BRANCH] [-r REMOTE]\n\nPush managed repositories to a remote.\n\noptions:\n -h, --help show this help message and exit\n -b BRANCH, --branch BRANCH\n Name of the branch to push.\n -r REMOTE, --remote REMOTE\n Name of the remote to push to. This is optional and defaults to 'origin'.\nThis command will attempt to push all staged commits to a remote. The --branch argument is required, and will be the name of the feature branch. The remote that is pushed to defaults to origin, but you can override this with the --remote argument.\n\n\nstage\n$ manage-repos stage --help\nusage: manage-repos stage [-h] [-f FILES [FILES ...]] [-m MESSAGE]\n\nStage changes in managed repositories. This performs a git add and commit.\n\noptions:\n -h, --help show this help message and exit\n -f FILES [FILES ...], --files FILES [FILES ...]\n List of files to stage in the repositories. Optional, and defaults to all modified files in the repository\n -m MESSAGE, --message MESSAGE\n Commit message to use for the changes.\nstage combines both git add ... and git commit -m, adding and committing one or more files to the staging area before you push to a remote.\nThe commit message must be a text string enclosed in quotes.\nBy default, --files is set to ., which will add all modified files to the staging area. You can also specify any number of files, separated by a space.\n\n\nsync\n$ manage-image-repos.py sync --help\nusage: manage-repos sync [-h] [-b BRANCH_DEFAULT] [-u UPSTREAM] [-p] [-r REMOTE]\n\nSync managed repositories to the latest version using 'git rebase'. Optionally push to a remote fork.\n\noptions:\n -h, --help show this help message and exit\n -b BRANCH_DEFAULT, --branch-default BRANCH_DEFAULT\n Default remote branch to sync to. This is optional and defaults to 'main'.\n -u UPSTREAM, --upstream UPSTREAM\n Name of the parent remote to sync from. This is optional and defaults to 'upstream'.\n -p, --push Push the locally synced repo to a remote fork.\n -r REMOTE, --remote REMOTE\n The name of the remote fork to push to. This is optional and defaults to 'origin'.\nThis command will switch your local repositories to the main branch, and sync all repositories from the config to your device from a remote. With the --push argument, it will push the local repository to another remote.\nBy default, the script will switch to the main branch before syncing, and can be overridden with the --branch-default argument.\nThe primary remote that is used to sync is upstream, but that can also be overridden with the --upstream argument. The remote for a fork defaults to origin, and can be overridden via the --remote argument.\n\n\n\nUsage examples\nClone all of the image repos to a common directory:\nmanage-repos --destination ~/src/images/ --config /path/to/repos.txt clone\nClone all repos, and set upstream and origin for your fork:\nmanage-repos --destination ~/src/images/ --config /path/to/repos.txt clone --set-remote --github-user <username>\nSync all repos from upstream and push to your origin:\nmanage-repos --destination ~/src/images/ --config /path/to/repos.txt sync --push\nCreate a feature branch in all of the repos:\nmanage-repos -c /path/to/repos.txt -d ~/src/images branch -b test-branch\nCreate a git patch and apply it to all image repos:\ngit diff envorinment.yml > /tmp/git-patch.txt\nmanage-repos -c /path/to/repos.txt -d ~/src/images patch -p /tmp/git-patch.txt\nOnce you’ve tested everything and are ready to push and create a PR, add and commit all modified files in the repositories:\nmanage-repos -c /path/to/repos.txt -d ~/src/images stage -m \"this is a commit\"\nAfter staging, push everything to a remote:\nmanage-repos -c repos.txt -d ~/src/images push -b test-branch", "crumbs": [ "Using DataHub", "Contributing to DataHub", diff --git a/sitemap.xml b/sitemap.xml index 524b3b39b..dbd44ccd7 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,266 +2,266 @@ https://docs.datahub.berkeley.edu/admins/cluster-config.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/index.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/transition-image.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/github-token.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/cheatsheet.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/clusterswitch.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/rebuild-postgres-image.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/calendar-scaler.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/delete-hub.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/core-pool.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/managing-multiple-user-image-repos.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/new-hub.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/credentials.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/policy/create_policy.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/policy/index.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/policy/principles.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/index.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/users/features.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/shiny.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/prob140.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/r.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/data100.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/authentication.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/incidents/2017-04-03-cluster-full-incident.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2019-05-01-service-account-leak.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2018-01-25-helm-chart-upgrade.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2018-01-26-hub-slow-startup.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-03-23-kernel-deaths-incident.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-02-09-datahub-db-outage.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2024-core-node-incidents.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2018-06-11-course-subscription-canceled.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-10-19-course-subscription-canceled.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-02-09-datahub-db-outage-pvc-recreate-script.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2019-02-25-k8s-api-server-down.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2022-01-20-package-dependency-upgrade-incident.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-05-09-gce-billing.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2018-02-06-hub-db-dir.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2018-02-28-hung-node.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-02-24-autoscaler-incident.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-10-10-hung-nodes.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-03-20-too-many-volumes.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/index.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-03-06-helm-config-image-mismatch.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/incidents/2017-02-24-proxy-death-incident.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/users/private-repo.html - 2024-10-18T22:39:39.012Z + 2024-10-21T21:11:35.987Z https://docs.datahub.berkeley.edu/users/hubs/data102.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/stat20.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/edx.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/stat159.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/users/hubs/datahub.html - 2024-10-18T22:39:39.008Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/policy/policy_deploy_mainhubs.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/policy/policy_create_hubs.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/policy/storage-retention.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.979Z https://docs.datahub.berkeley.edu/admins/storage.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/pre-reqs.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/course-config.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/new-image.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/rebuild-hub-image.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/new-packages.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/google-sheets.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/dns.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/remove-users-orm.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/documentation.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/howto/prometheus-grafana.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z https://docs.datahub.berkeley.edu/admins/structure.html - 2024-10-18T22:39:39.004Z + 2024-10-21T21:11:35.975Z diff --git a/users/hubs.html b/users/hubs.html index e0c37c1d4..717d7e7a0 100644 --- a/users/hubs.html +++ b/users/hubs.html @@ -476,7 +476,7 @@

JupyterHub Deployments

-
+

 
@@ -512,7 +512,7 @@

-
+

 
@@ -548,7 +548,7 @@

-
+

 
@@ -578,7 +578,7 @@

-
+

 
@@ -611,7 +611,7 @@

-
+

 
@@ -644,7 +644,7 @@

-
+

 
@@ -680,7 +680,7 @@

-
+

 
@@ -713,7 +713,7 @@

-
+

 
@@ -752,7 +752,7 @@

-
+