All of our SVN packages come packed with numerous features at no extra cost, allowing you to kickstart your projects immediately and with complete peace of mind.
Each SVN hosting receives its own unique URL from us.
With this URL the SVN repository management can be opened and operated
in the browser.
If necessary, an additional custom domain can be used in addition to our
URL.
You can also use your own SSL certificate or Let's Encrypt.
In addition to the practical web interface for managing Subversion repositories, our hosting already includes many features. All inbound and outbound traffic is included. And if you are missing something with our Subversion service, our support can certainly help you.
SSL encryption is included in each of our SVN hosting packages, so the SVN host can be managed encrypted in the browser.
Access to the repositories is also possible in an encrypted manner.
Optionally, you can ask our support to set up HTTPS Only. This means that the hosting can only be accessed via SSL.
If you use your own domain, you also have the option of using your own SSL certificate.
The SVN Hosting backup of all SVN data is encrypted on external systems.
We would be happy to support you with your questions and concerns.
No matter whether it is about importing existing SVN repositories,
setting up special hook scripts or other concerns.
For secure communication between our clients and the servers, we use encryption using SSL/TLS. Access controls using username and password prevent access to confidential data.
All of our productive systems are designed with multiple redundancies so that another system can take over the services if necessary or the overall output can be increased to cope with load peaks.
Each hosting specifies the maximum number of users and available storage. However, our server structure allows both storage and the number of users to be adapted to the needs of our customers.
All your data is backed up on external servers with encrypted backups and can be downloaded by you.
Our easy-to-use SVN administration enables complete administration via a web browser.
No more complicated commands on the console.
Our SVN hosting is standard, which is why it can be integrated into all environments. The integration can be done via the command line of a client computer or via one of the many development environments.
2750+
satisfied customers
82000+
Subversion Accounts
60000+
active SVN projects
2800
closed projects
* Status January 2023
| Subversion XS | Subversion S | Subversion M | Subversion L | |||||
|---|---|---|---|---|---|---|---|---|
| Storage included | 1250MB | 3000MB | 15000MB | 35000MB | ||||
| Storage expandable | Upgrade | Upgrade | Upgrade | |||||
| Projects / Repositories |
Unlimited! |
|||||||
| User | 10 | 25 | Unlimited | Unlimited | ||||
| Git Repositories | ||||||||
| Own Domain | ||||||||
| SSL | ||||||||
| Backups | ||||||||
| Subversion Hooks | ||||||||
| Availablility | >
99.9% |
>
99.9% |
> 99.9% | > 99.9% | ||||
| Payment method
and price |
yearly
€2.50 / Month |
yearly
€5.99 / Month |
monthly
€19.99 / Month yearly
€16.66 / Month |
monthly
€49.99 / Month yearly
€41.66 / Month |
||||
| Cancellation | Automatic Renewal for a further term unless cancelled at least 30 days before renewal. | |||||||
|
Instant Access to your Hosting
7-Day Free Trial. No Payment, no obligation. |
||||||||
SVN is a version control system (VCS) and manages files of all types and directories and all changes to them. This allows you to restore any version and track changes. Subversion is available centrally in the network for all users with appropriate authorizations.
Subversion, often abbreviated to SVN, is a version control system used to manage and
track changes to files and directories. Here are some main features and use
cases:
Version control: SVN allows you to track every change to files and
directories. This allows you to revert to previous versions at any time.
Collaborative development: Multiple users can work on the same projects at
the same time. Changes can be integrated and conflicts caused by concurrent changes
can be resolved.
Change history: SVN keeps a complete history of all changes, making it easy
to see who changed what and when.
Branching and tagging: Users can create alternate branches to develop new
features or fix bugs without affecting the main line of code. Tags can be used to
mark specific points in the development history.
File synchronization: SVN ensures that all developers have the latest
versions of files and synchronizes changes between the different working copies.
Access control: SVN provides mechanisms for managing user rights and access
controls to ensure that only authorized users can make changes.
Overall, Subversion is a powerful tool that makes software development more
efficient and secure by facilitating collaboration and management of source code and
other files.
An SVN client is software that allows users to interact with a Subversion
repository. An SVN client allows users to retrieve files and directories from the
repository, make changes, and upload those changes back to the repository. Main
functions of an SVN client include:
Checkout: Retrieving a working copy of a project from the repository.
Commit: Uploading changes from the working copy back to the repository.
Update: Synchronizing the working copy with the latest changes from the
repository.
Revert: Reverting changes in the working copy to the state in the repository.
Merge: Merging changes from different development branches.
Examples of SVN clients are TortoiseSVN (for Windows), SmartSVN (cross-platform),
and the command line client that ships with Subversion itself.
An SVN repository is a central storage location for files and their version history
in a project. It allows:
Version history storage: Tracks all changes to files.
Access control: Controls who can make changes.
Branching and tagging: Supports development branches and tags versions.
Transactions: Secures changes atomically to ensure data integrity.
The repository can be accessible locally or over the network.
Subversion (SVN) and Git are version control systems with these main
differences:
Architecture:
SVN: Centralized, with a central repository.
Git: Decentralized, everyone has a complete copy of the repository.
How it works:
SVN: Changes are synchronized directly to the central repository.
Git: Changes are edited locally and synchronized later.
Branching and merging:
SVN: Slower and more complicated.
Git: Fast and easy.
Performance:
SVN: Can be slower, often requires network access.
Git: Faster, many operations are local.
Storage requirements:
SVN: Centralized storage requirements.
Git: Each clone contains the entire history, but stored efficiently.
Areas of application:
SVN: Centralized development structures, companies.
Git: Distributed development, open source projects.
The easiest way to do this is with a Subversio client like TortoiseSVN. This SVN
tool is available on both Linux and Windows.
Many development environments such as Eclipse, PHPStorm or Visual Studio already
have a Subversion client integrated and can carry out commits, checkouts and updates
directly.
A copy of the central repository is created on the local hard drive via a so-called
checkout.
This also works like this on the Linux command line:
svn checkout http://YourUserName@svnXYZ.saas-secure.com/svn/myProject
The copy can now be changed, expanded or parts can be deleted.
Only after a commit are the changes transferred to the central Subversion server and
are also visible to all other users.
Yes.
Each of our packages can be tested thoroughly for 7 days free of charge. If you
don't like our hosting, you can stop the test at any time via the customer center
and all data are deleted.
If you like our hosting, the package will automatically be converted into regular
hosting after the end of the trial period and you can continue working seamlessly.
All of our servers are housed in German data centers. The data centers are certified according to ISO/IEC 27001 and therefore meet all standards regarding safety and environmental protection.
All of our systems are redundantly secured against failure. In recent years we have
achieved an average availability of 99.99%.
Furthermore, all of our customer data is saved once a day with an encrypted backup
on external systems. We keep the backups for 7 days and can restore the backed up
data if necessary.
First of all, you need an SVN client on the local computer to be able to communicate
with the SVN server.
For Windows computers we recommend the TortoiseSVN client.
The Subversion package is available under Linux. You can install this, for example,
with apt install subversion.
Now you can copy the link to the Subversion repository from the SVN administration
(checkout URL).
The process is called checkout and transfers the entire repository from the central
repository to the local computer.
With TortoiseSVN, a right-click in the directory tree is enough to open the checkout
dialog.
On Linux, go to the desired directory and enter: svn co saasurl/repositoryname
my/local/path.
You will then be asked for the user's username and password. The user should have at
least read permissions to read the data.
After successful transfer to your server, you will have the latest status of the
repository on your computer
If you would now like to update your local copy, i.e. add the latest changes from
the server to your local copy, there is the update function.
In Tortoise SVN all you need to do is right-click on the folder to be updated and
execute the update. On Linux it works like this: svn update
my/local/path.
Yes.
As long as you have access to the settings of your DNS server, which contains the
zone of your desired domain, using your own domain is not a problem.
To do this, simply enter your desired domain in the customer center and then add a
CName record to your DNS server that points to the standard domain of the hosting.
For example, if you want to use your domain svn.xyz-my-domain.de instead of
saas01234.saas-secure.com:
CName Record: svn.xyz-my-domain.de => saas01234.saas-secure.com
Setting up on our site usually only takes a few hours. If your DNS record is also
active, you can already access Subversion hosting with your domain.
In the customer center you can then activate a Let's Encrypt certificate or your own
certificate for the domain.
The backup can be done under Linux on an SSH console using svnrdump.
All you need is the URL of the repository and a file name under which the dump
should be saved.
svnrdump dump http://domain.tld/repo > svnexport.dump
The created file svnexport.dump now contains all repository revisions.
Remote export is possible with all Subversion servers from version 1.4!
First of all, an empty Subversion repository must be created on the central server.
Then the import can be started on the local SSH console:
svnrdump load http://domain.tld/repo < svnexport.dump
If a user name and password are required for the import, the command is like
this:
svnrdump load http://domain.tld/repo < svnexport.dump --username admin
--password admin --non-interactive
All revisions will now be transferred to the central server.
However, in some cases you will get an error:
svnrdump: E175002: DAV request failed; it's possible that the repository's
pre-revprop-change hook either failed or is non-existent
svnrdump: E175008: At least one property change failed; repository is
unchanged
svnrdump: E175002: Error setting property 'rdump-lock':
Repository has not been enabled to accept revision propchanges;
ask the administrator to create a pre-revprop-change hook
In this case, a hook must be set up in the target SVN repository to enable the
import.
Of course, this is only possible if you have access to the file system of the
central Subversion server.
In this case, the executable file pre-revprop-change with exit 0 must be created in
the hook directory.
printf '#!/bin/sh\nexit 0' > pre-revprop-change && chmod +x
pre-revprop-change
The remote import should then run.
Yes, it's very easy.
It's best to create your own Redmine user in the SVN administration.
And add the user to the repositories you want to integrate with Redmine.
This user only needs read permissions in the SVN repositories.
In Redmine, now open the desired project in which you want to integrate the
repository.
Now switch to the project configuration and then select the “Repositories” tab.
Now add a new repository. As the URL, enter the URL for the repository from the
Subversion administration.
For username and password, enter the previously created Redmine user.
By clicking on create, the repository is integrated into the Redmine project.
In the project tab “Repository” you will now see the integrated SVN.
Yes.
There are already some hook scripts preinstalled that can be easily added to a
repository.
For example, a hook script to send an email to all project participants when there
is a successful commit.
Or a hook script to enable remote import of a dump file or to change a commit
message afterwards.
If you need a hook with a specific functionality that you cannot find with us,
contact us and we will see how we can make it possible for you.
We have been a provider of SaaS and cloud-based security and development solutions since
2007.
We are experts in project management tool and Subversion hosting and our services are used
by countless developers around the world.
S.Ruttloff, Computer Hard- & Software
Owner: Sven Ruttloff
Morgensternstr. 15
Germany - 04179 Leipzig
VAT ID: DE255789971
Phone: +49 341 248 549 16 | Email: info@svn-hoster.com
SVN-Hoster.com is part of SaaS-Secure.com and is made with ♥ in Leipzig, Germany.
