Explore >> Select a destination
|
You are here 
|
michael.stapelberg.ch | ||
| | | | |
benscofield.com
|
|
| | | | | When GitHub goes down, you can almost hear the wailing in the streets. GitHub has cemented itself as a central part of many development workflows, and while much of that is unaffected by the occasional DDOS, one element in particular has the potential to cause a lot of trouble: deploys. Standard practice for many deployment tools (e.g., Capistrano) critically relies on the GitHub repository being available - checking out the latest code either on the remote server itself or locally before pushing it to t... | |
| | | | |
github.com
|
|
| | | | | RethinkDB plugin for Dokku. Contribute to stuartpb/dokku-rethinkdb-plugin development by creating an account on GitHub. | |
| | | | |
www.jtolio.com
|
|
| | | | | ||
| | | | |
danielpecos.com
|
|
| | | In a previous post, we have seen what Git is and its main characteristics. Now, we'll go more into detail about its functionality and we'll see what a usual day working with Git looks like. But before, some initial concepts: Repository: A working tree of files and directories which can be versioned, keeping track of every single modification made over the working tree, been able to move forward and backward in its history. | ||
