- Ubuntu 18.04
- NVIDIA driver 430.40
- NVIDIA Video Codec SDK 9.0.20
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Download binaries: https://github.com/TalalMash/ubond/releases/tag/v0.1.1 | |
Disable encryption for 400Mbit+ , force DNS over HTTPS if needed. | |
Temporarily running as root. (tun bugfix TODO) | |
---------------------- | |
VPS/crontab -e: | |
@reboot screen -d -m sh -c "/root/startubond.sh" | |
---------------------- | |
/root/startubond.sh | |
---------------------- | |
#!/bin/sh |
If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.
To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.
-
Clone some repo (you've probably already done this step).
git clone git@github...some-repo.git