I've this great webhost that I like and I must stay there. I've this great git curiosity to utilize, so GitHub is the site to visit.
Regrettably, the host don't support git, or other subversion system.
My real question is: How do i marry both under some development workflow? The files is going to be around the webhost and also the "git repository" on gitHub is this done?
Update: The host does not provide spend access and so i believe. (Not confirmed). When they do support, what must i request?
When the host provides you with spend access :
git clone <your repo>
For those who have spend access and never git, you are able to compile git inside your user directory.
Else, you can set-up a git-hook that pushes for your ftp/....
Here's the help guide to git hooks : http://book.git-scm.com/5_git_hooks.html You place it on your personal directory to ensure that it issues the command to push for your ftp
As your host does not support Git you will need to obtain a little creative together with your deploy strategy. For development, you ought to be good as your development machine can push/pull from gihub.
You are able to deploy for your web server from Github using the downloads feature. When you are prepared to deploy a release, tag your repo and push the tag as much as github (
git push --tags ). On github, this can produce a download tarball. Out of your webhost, just wget this download to your directory and not-tar it towards the directory that serves the web pages. You may want to copy inside your configuration files that are not within the repo.
You may also do all of this using the git bundle command.
One potential option to hooks is https://github.com/ezyang/git-ftp, a script you'd run out of your local machine which makes coping with FTP a little less painful by uploading only transformed files. I'd continue using GitHub (or any other git hosting solution) for backup/collaboration reasons, but after that you can also "deploy" for your shared hosting company using git-ftp.
On the separate note: As I understand your need to stay with your shared hosting company, I recommend that you simply consider improving to some VPS or similar sooner or later. Getting git on my small VPS (and which makes it part of my workflow and deploy strategy) saves hrs of labor. Even spend access alone can significantly quicken things, when you start learning how to capitalize from it.
Possibly your shared hosting company also provides a VPS plan?
For those who have spend access, you are able to write a custom publish-receive hook on github.com. You used code ought to be symbolically linked from another directory outdoors your webroot and after every deployment you are able to alter the symbolic connect to the final up-to-date code. Make certain you don't upload the .git folder or make certain that apache does not serve individuals files.