Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a typical hosting account with control panel, ssh access, now my question is, how to set up svn or git on that live account? so that whenever i develop something, I won't have to use FTP client, just commit using svn or push using git ?

share|improve this question

closed as not a real question by MikeyB, Scott Pack, voretaq7 Nov 16 '12 at 3:38

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

You need to clarify what you're trying to accomplish -- this question as you've written it makes little to no sense... – voretaq7 Aug 31 '11 at 15:51

Assumption, since you mentioned using git/svn: You're using this server to store your codebase.

Since you have SSH access, the easiest thing to do is set up git-over-ssh to do your push.

I hate saying 'lmgtfy', but any number of google searches for 'git over ssh' will give you a tutorial on how to do so.

share|improve this answer

I think you've mistaken what SVN/Git are intended to be used for.

It sounds to me that you want to deploy your "developed thing" to a production [serving] environment. SVN/Git/et. al. are repositories for managing change within something (a program's source code, a web site's various files, etc.) So one "checks in" or "commits" to these repositories.

What one does with the "stuff" being managed in the repo is totally up to you. You can use "post commit" scripts in various forms to do things. You can construct automated check-out-and-build scripts, etc. But I don't see how you could auto-deploy-to-production-environment when you check something in. At the very least, you'd want to only go-to-production when you tag the repo for a release...

Bigger picture: If you're in a managed hosting environment, I don't think you'd have the level of access you'd need to get in and bend these tools to do what you think you want to do.

share|improve this answer

you could install uberSVN on the server so you have a nice web interface to the manage the subversion server

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.