Install the OpenSSL on Debian based systems
sudo apt-get install openssl
rem KILL WINDOWS UPDATE REBOOT WITH FIRE!!! | |
SET mwuo=Microsoft\Windows\UpdateOrchestrator | |
schtasks /End /TN "\%mwuo%\Reboot" | |
schtasks /End /TN "\%mwuo%\USO_UxBroker_Display" | |
schtasks /End /TN "\%mwuo%\USO_UxBroker_ReadyToReboot" | |
schtasks /Change /TN "\%mwuo%\Reboot" /DISABLE | |
schtasks /Change /TN "\%mwuo%\USO_UxBroker_Display" /DISABLE | |
schtasks /Change /TN "\%mwuo%\USO_UxBroker_ReadyToReboot" /DISABLE | |
icacls "%WINDIR%\System32\Tasks\%mwuo%\Reboot" /deny "*S-1-1-0:F" | |
icacls "%WINDIR%\System32\Tasks\%mwuo%\USO_UxBroker_Display" /deny "*S-1-1-0:F" |
[Unit] | |
Description=Atlassian Bamboo Service | |
After=syslog.target network.target | |
[Service] | |
Type=forking | |
User=atlbamboo | |
ExecStart=/opt/atlassian/bamboo/bin/start-bamboo.sh | |
ExecStop=/opt/atlassian/bamboo/bin/stop-bamboo.sh |
. |
# Backup | |
docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql | |
# Restore | |
cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE | |
# Extremely basic development setup to serve the current directory at http://localhost:9001 | |
# Start nginx in this directory with `nginx -p . -c nginx.conf` | |
# Stop nginx with `nginx -p . -s stop` | |
events {} | |
http { | |
# Serve files with correct mimetypes on OSX | |
# location may have to be adjusted depending on your OS and nginx install | |
include /usr/local/etc/nginx/mime.types; |
#!/bin/sh | |
# | |
# !!! IMPORTANT !!! | |
# As of 2017-12-14, pacaur is unmaintained (https://bbs.archlinux.org/viewtopic.php?pid=1755144#p1755144) | |
# For alternatives see the arch wiki: https://wiki.archlinux.org/index.php/AUR_helpers#Active | |
# pacaur seems to get occasional updates to fix breaking changes due to pacman updates though. | |
# | |
# If you are new to arch, I encourage you to at least read and understand what | |
# this script does befor blindley running it. | |
# That's why I didn't make a one-liner out of it so you have an easier time |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j