Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy. This forum is not for asking programming related questions.
I really don't think this will solve anything. If the problem is that people don't post their code then what's the likelihood that they'll put it in svn? A lot of people don't even know how to use svn, especially the newbies who are often the ones that forget to post code.
We've got the ability to post code samples here on the forum. We've also got the ability to upload file attachments. How would people know about an svn repository taht's hosted on your computer?
I appreciate that you're enthusiastic about version control but I really don't see the need when it comes to posting code on the forums.
jshpro2 wrote:Alright btw its as easy as:
yum install svn
svnadmin create --fs-type=fsfs /path/to/repository
svn checkout file file:///path/to/repository/ /working/dir/ #tripple slash is intentional
Setting it up to work over SSH takes a little bit more limboing but isn't that much more verbose
I remember there being more configuring even before getting to the stage of svnadmin create... I could be mistaken. I already have it installed just not setup.
Wouldn't it be something more like this...
svn checkout http://path/to/repository/ /working/dir/
or
svn checkout https://path/to/repository/ /working/dir/ # for ssl
But dont know much about ssl, not even sure if it is worth using ssl.
An example of when a svn server would have been very useful...(I am sure there are more)
Thread from today, with parts of the code missing viewtopic.php?f=1&t=93428
But the question someone brought up earlier in the thread still remains, would they know how to use svn? Could we write a simple tutorial?
Well this would be aimed more at people who do use the PHP tags but post like multiple files, etc.. that noone wants to copy & paste into an IDE. The checkout command is generally not run on the server unless you're trying to let people upload & execute arbitrary PHP. If you want it integrated with httpd then theres more steps but if you just SVN over SSH you're done ( which is more secure ). Only downside is SVN won't "remember your password" unless you create a certificate.
Make sure whoever your ISP might be are ok with it, I was on Virgin Media and they went nuts about me having ports (22, svn+ssh, 80, svn webdav and others) open.
I just said it's my choice <span style='color:blue' title='I'm naughty, are you naughty?'>smurf</span> you, I'm on o2 now anyway, they're do disorganised they don't even notice anything I do.
panic! wrote:Make sure whoever your ISP might be are ok with it, I was on Virgin Media and they went nuts about me having ports (22, svn+ssh, 80, svn webdav and others) open.
Really?
I am with virgin media and I think they are great (because I have had no problems). I have ports 22,80, 6891-6999 (bittorrent...ssshh dont tell anyone) and 8080 open. I already have 1 svn server running which I use for when I work remotely and other close open source developers I collaborate with (v.old machine though). The new svn server (better machine) that we were talking about would be more public. I have never heard a peep from virgin about it. My traffic on average is about 50-75GB a month and I have passed 100GB before with no problems - I am on their biggest package so not sure if that makes a difference.