Skip to content

Instantly share code, notes, and snippets.

View juanitoddd's full-sized avatar

Juan David juanitoddd

View GitHub Profile
@juanitoddd
juanitoddd / docker-compose.yml
Created June 1, 2018 12:26
Gitlab docker-compose
gitlab:
image: 'gitlab/gitlab-ce:latest'
restart: always
hostname: 'localhost'
environment:
GITLAB_OMNIBUS_CONFIG: |
external_url 'http://localhost:9090'
gitlab_rails['gitlab_shell_ssh_port'] = 2224
ports:
- '9090:9090'
@juanitoddd
juanitoddd / GitHub-Forking.md
Created November 27, 2017 12:15 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

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.

Creating a Fork

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

@juanitoddd
juanitoddd / gist:e19ec81729de726349d5e5413ecf7c3c
Created August 13, 2016 15:09
Node.js install Ubuntu 14.04 and update to 5.12.0
sudo apt-get update
sudo apt-get install nodejs
sudo apt-get install curl
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install -y nodejs
sudo ln -s /usr/bin/nodejs /usr/bin/node
node -v
v5.12.0