Skip to content

Instantly share code, notes, and snippets.

version: '2'
services:
rails:
image: dockermd/frails:rm
hostname: "FichasAPIRails"
container_name: "FichasAPIRails2"
ports:
- "3000:3000"
- "8808:8808"
working_dir: /usr/src/app
version: '2'
services:
rails:
image: frails
hostname: "FichasAPIRails"
container_name: "FichasAPIRails2"
ports:
- "3000:3000"
- "8808:8808"
working_dir: /usr/src/app
@musghost
musghost / Procfile
Created July 21, 2017 20:30 — forked from andrius/Procfile
How to dockerize rails app with puma. Edit config/application.rb and config/puma.rb
api: bundle exec puma -C config/puma.rb
@musghost
musghost / gist:26c02abbc9369463e666198c7610889e
Created December 12, 2016 21:47 — forked from tamoyal/gist:10441108
Create super user and database user in Mongo 2.6
# Create your superuser
$ mongo
> use admin
> db.createUser({user:"someadmin",pwd:"secret", roles:[{role:"root",db:"admin"}]})
> exit
# Alias for convenience (optional and at your own risk)
$ echo 'alias mongo="mongo --port 27017 -u someadmin -p secret --authenticationDatabase admin"' >> ~/.bash_profile
$ source ~/.bash_profile
@musghost
musghost / redis.markdown
Created October 31, 2016 16:24 — forked from bdotdub/redis.markdown
Running redis using upstart on Ubuntu

Running redis using upstart on Ubuntu

I've been trying to understand how to setup systems from the ground up on Ubuntu. I just installed redis onto the box and here's how I did it and some things to look out for.

To install:

SWARM_TOKEN=$(docker run swarm create)
echo $SWARM_TOKEN
docker-machine create -d virtualbox --engine-label datacenter=mex --swarm --swarm-master --swarm-discovery token://$SWARM_TOKEN master
docker-machine create -d virtualbox --engine-label datacenter=usa --swarm --swarm-discovery token://$SWARM_TOKEN node1
docker-machine create -d virtualbox --engine-label datacenter=mex --swarm --swarm-discovery token://$SWARM_TOKEN node2
https://docs.google.com/presentation/d/1GDYbY5cLZWgduQ5fsHEwGqXGOf8Kk6LIRUxoULO9bo0/edit#slide=id.p
ERR=0
IP=$(sudo docker inspect -f jenkins_identidock_1)
CODE=$(curl -sL -w "%{http_code}" $IP:9090 -o /dev/null) || true if [ $CODE -ne 200 ]; then
echo "Site returned " $CODE
ERR=1 fi
#Pull down the system
sudo docker-compose $COMPOSE_ARGS stop
sudo docker-compose $COMPOSE_ARGS rm --force -v
return $ERR
docker run --name myjenkins -p 8080:8080 -v $PWD:/app -v /usr/local/bin/docker:/bin/docker -v /var/run/docker.sock:/var/run/docker.sock my-jenkins
Mocha reporter
/tmp/jenkins-buildenv/${JOB_NAME}/workspace
https://github.com/musghost/mocha-test
# Build the image to be used for this job.

Guía de colaboración para proyectos

Objetivo

Dado que existen numerosos desarrolladores contribuyendo a varios proyectos en paralelo, he creado esta guía para esclarecer el proceso que llevamos a cabo para manejar el modelo de branching. Para esto voy a listar una serie de pasos que es proceso adecuado que debemos llevar a cabo una vez que nos llega una tarea.

Comencemos

Después de aceptar la tarea revisando que todo esté en orden, vamos a nuestra terminal y nos pasamos a la rama de develop.