I was wondering if it was possible to install subversion onto an nfo shared system. I wanted to host some of my coding projects privately on a server. If nfo doesn't support subversion on their shared hosting systems, I already have a virtual server with apache and subversion installed, and I'd like to know if it was possible to point a subdomain to the separate server for subversion hosting.
mywebsite.com -> x.x.x.x
dev.mywebsite.com -> y.y.y.y
Two separate ips for obviously using the second server for my svn server.
Installing and managing subversion on a managed webhosting
-
- A regular
- Posts: 52
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Wed May 28, 2014 9:20 pm
Re: Installing and managing subversion on a managed webhosti
Also, when I visit dev.mydomain.come it says this

That IP is the IP of my VDS, which currently has apache2 and subversion installed and working properly, all I am wanting to do is point my subdomain to that server.
Here's a screenshot of my domain page if it will help at all.No website is currently set up at this address.
If you just set this site up, there may be a slight delay of up to a minute while the new Apache configuration is loaded; try visiting the page again in a minute or two and clicking refresh in your browser.
Redirecting to our main rentals page in 5 seconds..

That IP is the IP of my VDS, which currently has apache2 and subversion installed and working properly, all I am wanting to do is point my subdomain to that server.
Re: Installing and managing subversion on a managed webhosti
The subversion binaries are installed on the shared webhosting space but I have not experimented with them beyond this. It can definitely be used in the client capacity.Jake wrote:I was wondering if it was possible to install subversion onto an nfo shared system.
From this error and the page, it looks like your DNS change hasn't propagated to your ISP's DNS server yet. It will likely start working after a few hours.Also, when I visit dev.mydomain.come it says this
Re: Installing and managing subversion on a managed webhosti
So I could use SSH to create repositories and such with subversion on my shared web hosting, correct?
Also, its been over 72 hours since I submitted that A record change for dev.mydomain.com and it still appears to be not functional.
For some reason when I attempt to visit it, it adds www to the beginning of it, I thought this might have been caused for me redirecting my @ to a .htaccess to adds www to it, but I didn't think @ was triggered while visiting a subdomain.
Also, its been over 72 hours since I submitted that A record change for dev.mydomain.com and it still appears to be not functional.
For some reason when I attempt to visit it, it adds www to the beginning of it, I thought this might have been caused for me redirecting my @ to a .htaccess to adds www to it, but I didn't think @ was triggered while visiting a subdomain.
Re: Installing and managing subversion on a managed webhosti
I went on SSH, setup all the repository stuff in my directory, but ran into a problem while trying to commit.
Wait.. I think that's svn authentication, not failure to access.>svn commit -m "Initial Import"
svn: E170001: Commit failed (details follow):
svn: E170001: Authorization failed
Re: Installing and managing subversion on a managed webhosti
I almost need a KB article. There's so many articles online, and I'm not sure which ones I can use or which ones even work. From what I've read setting it all up is confusing, there's so many different routes to take, and most of them are saying /etc/apache2/mods-available/dav_svn.conf Which I'm assuming has already been pre-configured. Perhaps someone else knows more? I feel like I'm the only one here who's trying to get subversion.
Re: Installing and managing subversion on a managed webhosti
I am not very experienced with setting up SVN repos myself. I have heard that others have done it on the shared webhosting but have not experimented with it personally.
In terms of the DNS record, it sounds like your web browser may have a cached version of the redirect page. Try clearing your temporary internet files -- I think that will take care of it.
In terms of the DNS record, it sounds like your web browser may have a cached version of the redirect page. Try clearing your temporary internet files -- I think that will take care of it.