Month: February 2017

This is too long and rambling, but to steal a joke from Mark Twain Blaise Pascal I haven’t had time to make it shorter yet.  There is some discussion of this post on the git mailing list, but…

Source: git: fetch and merge, don’t pull | Mark’s Blog

Git Pull Rebase is taking while.

Source: Resolving merge conflicts after a Git rebase – User Documentation

What’s the difference between git merge and git rebase?

Source: What’s the difference between ‘git merge’ and ‘git rebase’? – Stack Overflow

 

Create a directory on the drive

Create empty repository on that directory

 

git init –bare

 

Now Repository is created.

 

Go to Visual Studio, and clone that directory, and create empty solution, and add projects file.

 

After project is working fine, please add untracked file, and push and sync.

 

Once Initial Sync is done, you can clone that repo, with other name to test.

Note: VS Git client doesn’t pull all the files correclty

Using Open Data API

Source: Google Maps Mashup | Socrata

Cloud Development Trial

Source: Login

With the release of Docker 1 inwpurj.8, Windows users who have been learning Docker using Boot2Docker VM Tool, need to learn a few new concepts to get their environment in place for their Docker learning…

Source: Docker Toolbox Setup — Windows

Currently Windows Toolbox doesn’t support this feature, but recert is good way

Contract/freelance Python, XSL/XQuery development and Scrum consultancy.

Source: Creating a Docker Machine with a fixed IP – Oldham-Made: Python/XSL/Xquery Development and Scrum consultancy

By default, seems docker-machine picks one randomly, so forced to use the one for vboxnet0(192.168.59.3/24, the one used by boot2docker) seems to solve the issue:

$ docker-machine create --driver virtualbox --virtualbox-hostonly-cidr "192.168.59.3/24" dev
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM...
To see how to connect Docker to this machine, run: docker-machine env dev

$ docker-machine ip dev
192.168.59.103

By default, seems docker-machine picks one randomly, so forced to use the one for vboxnet0 (192.168.59.3/24, the one used by boot2docker) seems to solve the issue: $ docker-machine create –driver virtualbox –virtualbox-hostonly-cidr “192.168.59.3/24” dev Creating VirtualBox VM… Creating SSH key… Starting VirtualBox VM… Starting VM… To see how to connect Docker to this machine, run: docker-machine env dev $ docker-machine ip dev 192.168.59.103

Source: [Feature Request] Specify a static IP for VirtualBox VMs · Issue #1709 · docker/machine