I've never used any kind of source control before although I understand the concept. What I am confused about (and perhaps just not aware) is what benefit do I achieve and/or why would I want to configure Subversion and Apache? Do I need to configure it with Apache to be able to access my repositories from other computers over a network? Please feel free to provide any other details you feel are relevant?
My setup right now is a laptop (Windows XP Pro) and a virtual machine (Windows XP Pro). On my virtual machine I have Apache 2.2, MySQL 5 and PHP 5. This setup is my main concern although I'm happy to hear examples/situations that deviate from my scenario.
Subversion is developed as a project of the Apache Software Foundation, and as such is part of a rich community of developers and users.
VisualSVN Server and its components are not based on Java, and they do not depend on the vulnerable Apache Log4j library. Although VisualSVN Server itself is not affected, it is recommended to check if your Subversion repositories have custom or third-party hooks that use Java and the vulnerable Apache Log4j library.
Subversion is still used by some projects, but git has replaced it for most new projects. Many subversion projects have also migrated to git. But since subversion is open source it won't ever completely disappear.
Client-Server ArchitectureSharing a Subversion repository between users requires the use of a server. Repositories should never be accessed simultaneously by multiple users or client apps without employing a server to manage access to the repository.
Check out the SVNBook Entry: Choosing a Server Configuration. It talks about the pros and cons of the different ways of accessing a Subversion server.
The SVN protocol is the simplest to set up and administer, but probably won't work across corporate firewalls (but Apache will, via HTTP).
It can be beneficial when port 3690 needs to be closed. It also lets users browse the code using a browser, which has pros and cons. You don't need to have a Subversion client to see the code, but a web browser makes a crummy repository browser.
Setting it up isn't too tricky. I found this page to be useful.
But, if you're just using it in a local VM environment, svnserve
would be fine for you.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With