Need advice about which tool to choose?Ask the StackShare community!
Gogs vs SVN (Subversion): What are the differences?
What is Gogs? A self-hosted Git service written in Go. The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.
What is SVN (Subversion)? Enterprise-class centralized version control for the masses. Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
Gogs can be classified as a tool in the "Code Collaboration & Version Control" category, while SVN (Subversion) is grouped under "Version Control System".
"Self-hosted github like service" is the top reason why over 32 developers like Gogs, while over 17 developers mention "Easy to use" as the leading cause for choosing SVN (Subversion).
Gogs and SVN (Subversion) are both open source tools. Gogs with 30.6K GitHub stars and 3.54K forks on GitHub appears to be more popular than SVN (Subversion) with 326 GitHub stars and 118 GitHub forks.
Coderus, Performance Assessment Network (PAN), and Die Coder GmbH are some of the popular companies that use SVN (Subversion), whereas Gogs is used by Write.as, OSInet, and GameDuell. SVN (Subversion) has a broader approval, being mentioned in 77 company stacks & 58 developers stacks; compared to Gogs, which is listed in 9 company stacks and 10 developer stacks.
SVN is much simpler than git for the simple stuff (checking in files and updating them when everyone's online), and much more complex than git for the complicated stuff (branching and merging). Or put another way, git's learning curve is steep up front, and then increases moderately as you do weird things; SVN's learning curve is very shallow up front and then increases rapidly.
If you're storing large files, if you're not branching, if you're not storing source code, and if your team is happy with SVN and the workflow you have, I'd say you should stay on SVN.
If you're writing source code with a relatively modern development practice (developers doing local builds and tests, pre-commit code reviews, preferably automated testing, preferably some amount of open-source code), you should move to git for two reasons: first, this style of working inherently requires frequent branching and merging, and second, your ability to interact with outside projects is easier if you're all comfortable with git instead of snapshotting the outside project into SVN.
Pros of Gogs
- Self-hosted github like service36
- Very low memory footprint31
- Easy to install / update29
- Lightweight (low minimal req.) runs on Raspberry pi17
- Single binary deploy no dependencies16
- Open source14
- Cross platform (MacOS, Windows, Linux ...)12
- Wiki11
- Issue tracker10
- Great UI3
- LDAP Support3
Pros of SVN (Subversion)
- Easy to use20
- Simple code versioning13
- User/Access Management5
- Complicated code versionioning by Subversion3
- Free2
Sign up to add or upvote prosMake informed product decisions
Cons of Gogs
Cons of SVN (Subversion)
- Branching and tagging use tons of disk space7
Sign up to add or upvote consMake informed product decisions
What is Gogs?
What is SVN (Subversion)?
Need advice about which tool to choose?Ask the StackShare community!
What companies use SVN (Subversion)?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Gogs?
What tools integrate with SVN (Subversion)?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7