Sourceforge.net also offers SVN hosting now I believe.
-Cliff On 2/28/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote: > Doug, > > If you were to take Simeon up on his offer of SSVN+Trac this issue would go > away instantly since the system he uses is built around the mod_dav plugin > and Apache+Subversion integration. The other nice byproduct of this is the > fact that people can at least get to the repository via any DAV connector > including the one that's built in to Dreamweaver 8. No write access, but > since it's a DAV plugin as far as Apache is concerned it implements the DAV > protocol for interaction. It means that you can at least download the > current version of the repo without using an SVN client. > > It'd also enable bug reports with bug numbers, repo version associated with > bug fixes, repo browsing via HTTP, and a homepage/wiki/blog to boot. If it's > available I can only recommend you take advantage of it. > > That would be my suggestion. :) > > Laterz, > J > > > > > > ------------------------------------------------ > > Jared C. Rypka-Hauer > > Continuum Media Group LLC > > http://www.web-relevant.com > > Member, Team Macromedia - ColdFusion > > > > > "That which does not kill me makes me stranger." - Yonah Schmeidler > > > On Feb 28, 2006, at 2:46 PM, Peter J. Farrell wrote: > > Chris Tilley said the following on 2/28/2006 8:40 AM: > Peter, > > You are exactly right, that is my work problem. I'm not sure I > understand your suggestion with Apache mod? Any suggestions, tutorial > that will assist me would be greatly appreciated. > > Is there a way to change the port that is used for TortoiseSVN? > > Thanks all > Chris > Nope. As Doug said, he uses the Subversion daemon which use port 3690. > This is why I advocate using Subversion with the dav module in Apache > because all your requests are over http and port 80 instead of the > svn:// protocol. You could also use svn+ssh if you have ssh > infrastructure in place, but this causes a bit of a problem for Windows > users since Windows does not ship with an ssh client (BTW, Putty is an > excellent choice if you are in need of a ssh client for Windows and it > integrates with TortoiseSVN as well). Anyways, svn+ssh requires a few > extra bits of configuration and isn't a great solution for anon > repository access (like here with Reactor). In the end, if you want a > robust solution (such as integration with LDAP, Windows domain or plain > old basic http authentication/authorization) -- Apache + Subversion is > the way to go. Also, you won't have to open up as many ports on your > firewall if you run Apache on a standard port (something your net admin > would probably will thank you for). > > The only thing I can think of is to use a proxy server which can be > setup in the Tortoise settings (right-click -> TortoiseSVN -> Settings > -> click on Network in the left column). > > Doug, you might consider running the svn daemon on an alternate http > port like 8080, 81, or 8090. However, then you have to make sure that > people access the repo with that port. Invoke that option by using the > the --listen-port= option when running the daemon (the daemon defaults > to 3690 without it). Although the changes are slim that some firewall > may block those options as well. > > Ok, I'm done evangelizing Subversion. > > Best, > .Peter > > -- > Peter J. Farrell :: Maestro Publishing > Member Team Mach-II :: Member Team Fusion > http://blog.maestropublishing.com > > Create boilerplate beans and transfer objects for ColdFusion! > Fire up a cup of Rooibos! > http://rooibos.maestropublishing.com/ > > > > > > -- Reactor for ColdFusion Mailing List -- [email protected] > -- Archives at > http://www.mail-archive.com/reactor%40doughughes.net/ > > > > -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
