Code for Berkeley's DataHub JupyterHub installation anaylsis.
Mostly focused around server/user usage, files opened and nbgitpuller links that are clicked.
If you've created ssh keys previously, please skip to the next step.
If you're running Ubuntu, regular installation/VM or WSL2, and have NOT previously generated SSH keys please execute the following commands:
ssh-keygen -t rsa -b 8192
For added security, you can choose to enter a passphrase during key creation. This is optional.
If you're using macos, and have NOT previously generated SSH keys please execute the following commands:
ssh-keygen -t rsa -b 8192
For added security, you can choose to enter a passphrase during key creation. This is optional.
If you're running Windows, please install either WSL2 native linux or gitbash.
Open a terminal, and run the following command. WSL2 is preferred, but there are a few additional steps required.
ssh-keygen -t rsa -b 8192
For added security, you can choose to enter a passphrase during key creation. This is optional.
Please follow the instructions here
to upload your SSH public key to GitHub. This allows you to authenticate while
using git in a repo.
When you log in to your terminal, you will be in your home directory. We
recomend creating a sub-directory named something like src or repos. This
will help you manage any other repos you might download.
$ pwd
/home/sknapp
$ mkdir src
$ cd src
Next, go to the Datahub Usage Analysis github repo
and create a fork. To do this, click on the fork button and then
Create fork.
Now clone the primary Datahub Usage Analysis repo on your local device. You
can get the URL to do this by licking on the green Code button in the primary
Datahub Usage Analysis
repo (not your fork) and clicking on ssh and copying the value in the box.
Before you clone, make sure that you're in the subdirectory that will contain this repo:
$ pwd
/home/sknapp/src
Now you can run the git clone command:
git clone git@github.com:berkeley-dsep-infra/datahub-usage-analysis.git
Now cd in to datahub-usage-analysis directory and set up your local repo
to point both at the primary repo (upstream) and your fork (origin). After
the initial clone, origin will be pointing to the main repo and we'll need
to change that.
Here is an example, including output, of how to set up your remotes:
$ cd datahub-usage-analysis
$ git remote -v
origin git@github.com:berkeley-dsep-infra/datahub-usage-analysis.git (fetch)
origin git@github.com:berkeley-dsep-infra/datahub-usage-analysis.git (push)
$ git remote rename origin upstream
$ git remote add origin git@github.com:<your github username>/datahub-usage-analysis.git
$ git remote -v
origin git@github.com:<your github username>/datahub-usage-analysis.git (fetch)
origin git@github.com:<your github username>/datahub-usage-analysis.git (push)
upstream git@github.com:berkeley-dsep-infra/datahub-usage-analysis.git (fetch)
upstream git@github.com:berkeley-dsep-infra/datahub-usage-analysis.git (push)
The raw commands to copy and paste are below:
cd datahub-usage-analysis
git remote -v
git remote rename origin upstream
git remote add origin git@github.com:<your github username>/datahub-usage-analysis.git
git remote -v
Now you can sync your local repo from upstream, and push those changes to
your fork (origin):
git checkout main && \
git fetch --prune --all && \
git rebase upstream/main && \
git push origin main
When making changes to anything in this repo, always work in a fork and on a feature branch. You should also make sure that your local repo is up-to-date with this one (upstream) prior to making and committing changes. This is because other contributors may have pushed changes after you last synced with this repo.
git checkout main && \
git fetch --prune --all && \
git rebase upstream/main && \
git push origin main
To create a new feature branch and switch to it, run the following command:
git checkout -b <branch name>
After you make your changes, you can use the following commands to see
what's been modified and check out the diffs: git status and git diff.
When you're ready to push these changes, first you'll need to stage them for a commit:
git add <file1> <file2> <etc>
Commit these changes locally:
git commit -m "some pithy commit description"
Now push to your fork:
git push origin <branch name>
Once you've pushed to your fork, you can go to the
Datahub Usage Analysis repo
and there should be a big green button on the top that says Compare and pull request.
Click on that, check out the commits and file diffs, edit the title and
description if needed and then click Create pull request.
If you are new to git, or just want to learn a bit more about it, I highly
recommend taking a look at the official git online book.
Specifically, please read/review the following chapters: