Get boot2docker working with nfs instead of vboxsf.
Tested on:
- Boot2Docker-cli version: v1.6.0
Git commit: 9894ae9
- Boot2Docker-cli version: v1.6.2
Git commit: cb2c3bc
Get boot2docker working with nfs instead of vboxsf.
Tested on:
- Boot2Docker-cli version: v1.6.0
Git commit: 9894ae9
- Boot2Docker-cli version: v1.6.2
Git commit: cb2c3bc
| # in case of conflict with local nginx: | |
| # make sure in all *.confs ( | |
| # also in default and example to avoid error like | |
| # 'nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)' | |
| # ) | |
| # set for instance "listen 127.0.0.1:80" instead of "listen *:80" | |
| # docker & network settings | |
| DOCKER_IMAGE_NAME="maxexcloo/nginx-php" # build of nginx-php - for example | |
| DOCKER_CONTAINERS_NAME="nginx_bridged" # our container's name |
sudo su
apt-get update && apt-get install -y libvirt-dev ruby-all-dev apparmor-utils
curl -O -L https://dl.bintray.com/mitchellh/vagrant/vagrant_1.6.5_x86_64.deb
dpkg -i vagrant_1.6.5_x86_64.deb
aa-complain /usr/lib/libvirt/virt-aa-helper # workaround
exit
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "your_email@youremail.com"
| #!/bin/bash | |
| set -eu | |
| shopt -s nullglob | |
| readonly base_dir=/var/lib/docker/registry | |
| readonly output_dir=$(mktemp -d -t trace-images-XXXX) | |
| readonly jq=/usr/bin/jq | |
| readonly repository_dir=$base_dir/repositories |
| #!/bin/bash | |
| set -eu | |
| shopt -s nullglob | |
| readonly base_dir=/var/local/docker-registry | |
| readonly output_dir=$(mktemp -d -t trace-images-XXXX) | |
| readonly jq=/tmp/jq | |
| readonly repository_dir=$base_dir/repositories |
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
| #!/bin/bash | |
| # | |
| # Efstathios Xagoraris <sxagoraris@gmail.com> | |
| # Validate YAML files using ruby | |
| # | |
| if [ $# -eq 0 ] | |
| then |
mix3d asked for some help using this guide with windows so here we go. This was tested with Windows 10. Run all commands in Git Bash once it's installed.
Github will be the main account and bitbucket the secondary.
Now located at https://github.com/JeffPaine/beautiful_idiomatic_python.
Github gists don't support Pull Requests or any notifications, which made it impossible for me to maintain this (surprisingly popular) gist with fixes, respond to comments and so on. In the interest of maintaining the quality of this resource for others, I've moved it to a proper repo. Cheers!