Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/attitude/git-workflow-scipts

#!/usr/bin/php scripts I use to sync and deploy to Websupport.sk servers using GIT hooks, RSYNC and SSHFS (all scripts are experimental)
https://github.com/attitude/git-workflow-scipts

Last synced: about 6 hours ago
JSON representation

#!/usr/bin/php scripts I use to sync and deploy to Websupport.sk servers using GIT hooks, RSYNC and SSHFS (all scripts are experimental)

Host: GitHub
URL: https://github.com/attitude/git-workflow-scipts
Owner: attitude
Created: 2012-12-03T20:13:29.000Z (almost 12 years ago)
Default Branch: master
Last Pushed: 2012-12-04T07:32:53.000Z (almost 12 years ago)
Last Synced: 2023-03-11T07:18:31.089Z (over 1 year ago)
Size: 117 KB
Stars: 1
Watchers: 1
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md

Awesome Lists containing this project

README

Git Workflow Scipts
===================

\#!/usr/bin/php scripts I use to sync and deploy to Websupport.sk servers using GIT hooks, RSYNC and
SSHFS (all scripts are experimental)

While trying to use **mounted hosting using SSHFS** what frustrated me most was the fact that every
command run near zero speed. Any *git* command was **painfully slow** and in the end it just failed
(might have been my mistake).

Anyway, to be able to use any *GIT flow deployment tactics* you need to have some direct acces to a git
enabled host directly. Well even with the best hosting providers you can hardly get SSHFS, RSYNC.
Forget about getting access to GIT command any soon. Although, some rumors say, there might be some
hope in the future.

And since GIT looks at the whole repository when looking for changes, every command requiring lookup
through remote files was a waste of time and trafic of files up-down for (not tested all but all
mostly used like *clone*, *pull*) every GIT command.

So I did my homework, researched a bit and realised that it can be done the other way. This way:

1. I realised that GIT is a distributed system and therefore, I can use the same tools to create my own
"remote origin" on my machine. Soon I found out that you can only push to a --bare repository
(otherwise you would need to make a hard reset of the HEAD).
1. If you upload a `id_rsa.pub` (public key) to the [Websupport.sk](http://www.websupport.sk/) servers
you don't need to write any password during the connection process. (You need to rename it to
`/.ssh/authorized_keys` where `/` is the root of your path to which the user.your-hosting.sk has
access - not necessarily the root of the server.
1. You can pull to any other repository from the bare repo to get the copy of your working files.
1. Rsync is a very fast way to sync any local dir with remote dir.

Boom, you might now see the pattern or navigate to the scripts and read the inline comments for
more inside perspective.

Why the hack did you chose PHP?
-------------------------------

1. I used PHP as language of choice as it allows me to do what I need to do (GTD).
1. It is the language I use the most, so I can write scripts quite fast (learning curve reason).
1. I am not as close to be skilled in BASH and other fancy shell stuff as I am skilled in PHP (quality).

Requirements
------------

- any UNIX/LINUX/OSX will do
- git, rsync, sshfs installed
- /.ssh/authorized_keys on server

*Note:* I use Homebrew, [The missing package manager for OS X](http://mxcl.github.com/homebrew/).
Others might want to use *apt-get* (Ubuntu and other Defian-based) or *yum* (CentOS).
Feel free to suggest others packaging managers.

So if you are the match, feel free to fork and make something awesome with it, spreading word is also
appreciated. I might also add issues for this repository so if that is true feel free to open one if
you get the feeling that there's something you might want to say. Any ideas are wellcome.