What is Reddit's opinion of
TortoiseSVN?
From 3.5 billion Reddit comments
21 reviews of this app found across Reddit:
When you're working on any kind of serious project, use proper version control. It not only works as a backup solution, but also allows you to go back to previous versions on a file-by-file basis when needed, or to show you the changes you made since X.
If you're not familiar with version control systems yet and work on Windows, I recommend Tortoise SVN. Here's a tutorial on that: https://www.youtube.com/watch?v=osnP8MGO0PQ
TortoiseSVN is a nice option especially if you use it in a local network but with a few tricks you can use SVN with Google drive witch gives a lot of storage with low prices and you can share it with your friend online. The only problem will be the security drive is not the most secure place.
In our small group (5 persons) we use Subversion for about 7 years. It's simple and works fine, providing butthurt with merging time to time. But in general it's OK. We use Visual SVN Server (https://www.visualsvn.com/server/) and Tortoise SVN (https://tortoisesvn.net/) as client. There is also free command line client which is available at collab.net
Hi Joson. Writing and traveling is a great combo.
I co-authored a book with someone 3000 miles away so we had a similar need. We had a server set up with TortoiseSVN, an apache subversion client. Nice interface and great for keeping track of different versions. (As you know, it's a PITA to edit an outdated version or not have access to a prior version when you realize the old approach was better. Tortoise can be a godsend.)
It gets better: It's free and open source.
We had someone else set it up--and it was a long time ago so I can't be much help on the tech. I can tell you it was great then, and likely even better now.
I run a SVN server on my synology NAS and push/pull it from there. (git would also work)If you don't have the budget for a NAS you could also just use a secondary hard drive and still use SVN. That's still better than copying stuff around.
Try: https://tortoisesvn.net/ free and very easy to use
I would use svn Then you can commit the files/folders, delete them, then check them out the next time you want to play
I use it to sync game files across devices where steam sync isn’t implemented, but this will work too.
You (and everyone) else write bug-free code 100% of the time?
How do you do regression testing?
The reality is that people (your or others) make changes and eventually notice something else broke. Using source control makes it MUCH easier to see WHAT broke and WHEN it broke.
If you aren't using Source Control for Software Development then you are doing it wrong. i.e. You are making things 100x more complicated then they need to be.
Hell, even use TortoiseSVN if you don't want to use a Git GUI.
Every week you should be checking your code in and having a testable "snapshot."
- A] Easy, Bad: copy folders manually and share using discord or wetransfer
- B] Easy, Bad but slightly better: Dropbox + SyncBack systematic backing up and duplication
- C] Harder, Better: local version control with a dropbox to share to someone else
- D] Hardest, Best: web accessible version control for both to directly back up and version files.
​
Easy way is back and forth file sharing, but it's also really rough in the long run. Manually copying files leads to someone eventually (or often) making a mistake and overwriting work, or tossing out the wrong copy.
Using something like dropbox or google has the same issues though slightly better. Using a dropbox style service with a batch file backup program like SyncBack can also help automate this, and it may be the best option for the "easy" method.
Ultimately, best to use what pros use: version control software. One of the current favorites is called Git, but for the type of files that csgo uses, you can't go wrong with svn. Svn is complicated, but less complicated than a lot of other software like this. Also free. A popular way to use SVN is with a client called Tortoise SVN.
It's possible to set this up on your own pc, or have a webhost do it for you. Most decent webhosts can get svn setup with the click of a button, though you'd still have to do some learning to know how to use it.
Once you do all this - csgo mapping is a one at a time type of thing. Break the map into chunks or layers, make your own system, but you can't both be editing at the same time in the same map.
TIL GitHub Repo's can be accessed with SVN.
> I couldn't find anywhere in GitHub settings to get an application password like in other service having 2FA.
It is called Access token. Here's some info.
2FA is only for accessing your Account and the GitHub API, not for commits as far as I'm aware. You would secure your Repository by using an SSH Key stored for your account. I couldn't find anything about this but it might be a security measure to disable Repository Access with just USR:PWD when 2FA is activated.
TortoiseSVN appears to support login via SSH Key, this should at least be a workaround for your problem.
- An easier way to reference commits. SVN's sequential revision number is far more convenient to use than a Git commit hash. First it's shorter, and it also indicates the sequence of the commits. I recall that there is one VCS that allows you to reference local commits using a shorter identifier, but wouldn't necessarily be shared between other clones of the same repo.
- Ability to checkout just a subfolder of a repo, like SVN lets you.
- ACTUALLY TRACKING CHANGES. Git doesn't track changes. It only tracks a sequence of snapshots of the entire repo. I don't know how anyone can take a VCS seriously when it doesn't do the one thing we need a VCS to do: track files. File move and rename tracking is almost useless beyond a few commits. When I compare 2 commits, it should know the history of every file. A similarity score isn't too bad for tracking file move/rename, but it should allow for manually overriding that heuristic when it is wrong. This also allows for the powerful TortoiseSVN Revision Graphs. SVN is still my preferred VCS for long-term commit history for this reason (but Git is pretty handy for local hacking).
>Funny that link didn't work for me. And if it had worked for you, I imagine you would have pasted it directly.
It isn't a web link, it's the address to a subversion repository. You need an svp client to access the files there.
At this point I feel that this line of argument is well and truly dead. The data are freely available, the methods are well described and replicable. If you want to critique the surface temperature record, you need to show that the methods are wrong or are being applied incorrectly.
You really should learn how to use some form of Version Control. It really makes a major difference in complicated development. I much prefer local solutions as I don't always trust Cloud storage. If you're on Windows, Tortoise is very easy to setup. You make an SVNRepoistory folder at your C: drive root (or if you have D: data drive use that) and point Tortoise at it.
You can Tag (stable versions) or Branch off whole builds, or just sections you're working on.
First step is to always make sure your Version Control solution is working, and it is up to date. Depending on what you're using, you'll want to Branch the current stable version you're using. Use the Version Control to effectively set it aside "as is" so you can always go back to it.
Once you've Branched your stable version, you can begin refactoring without fear of irreversible damage.
I'm used to working with TortoiseSVN for personal projects, others prefer Git (and online services like GitHub).
If you still want to use Subversion you might like https://tortoisesvn.net as a graphical client.
But getting familiar with git will be good for you in general, though, as more and more companies are moving to git as the years go on. You don't have to use Github, but you can. They offer free private repos now, which is great. You can also use Gitlab which is also popular (and no you don't have to host it yourself).
Graphical clients for Git that you might be interested in (in no particular order):
- Github Desktop (also works on other git hosts, AFAIK)
- GitKraken
- SmartGit
- SourceTree
- TortoiseGit
- GitExtensions
- Tower
- Sublime Merge (from makers of Sublime Text)
https://tortoisesvn.net/ this one is kinda cool and is local and has a nice gui. i used it once and i liked it. i dont know if connects to vscode. you can try the microsoft team services too. it connect to vscode for sure
You cant get it by just opening it in a web browser you need an svn program like Tortoisesvn https://tortoisesvn.net/
After you download and install tortoise svn or a similar program go into your mods folder for ck2 and create a new folder and name it "EKSVN" then right click on EKSVN and click "SVN checkout" and put the svn url in the box at the top labeled "URL of Repository" then click OK and then it should ask for the username and password. It might also give you a popup about an invalid certificate just click one of the accept options.
It will probably take several minutes or more depending on your internet speed to finish downloading. After it finishes downloading open the EKSVN folder and find the ESM.mod file and copy it back out into your mod folder and then it should show up in the ck2 launcher.
Revision control software is a tool used by developers to track changes and revisions to files. It is used to store source code and, when necessary, revert or review the history of changes to a file.
The same idea applies here. Because there are many files, it is assumed the author wants a history of changes and revisions otherwise the author would save over the same file each revision.
My team uses Apache Subversion. It is open source and free.
https://subversion.apache.org/
There is a free shell integration component called Tortoise SVN that adds context menu items to files for easy commit, revert, and view history operations.
We use Subversion (SVN) at work. It works well. It can get confusing when things go wrong, but it doesn't happen often. Don't use it without some sort of GUI; our company uses TortoiseSVN.
SVN is on the older side; I believe all the cool kids use Git or Github now.
Ah, I can throw up a couple steps for the SVN parts. First, an SVN repository is basically just a place to keep files, where you can also get the older versions of files if you want. Kinda like a Dropbox folder or something along those lines.
- Anyways, you'll need to download an SVN client, which lets you get files from an SVN repository. I use https://tortoisesvn.net/downloads.html All the program basically installs is stuff that lets you right click a folder and do SVN stuff.
- Once you install TortoiseSVN above, you'll create an empty folder somewhere like your desktop, right click it, and click "SVN Checkout...". At that point, just paste https://subversion.assembla.com/svn/ryona-rpg-translation/trunk/RyonaRPG_patch in the URL field and click "OK" and it should download the files from that URL.
EDIT: Forgot the core stuff.
- Download both core0104.7z and core0105.7z from http://dev.rsaga.org/core/.
- Extract core0104.7z to wherever you want (this file has the game inside of it). You can use 7-zip to extract it, unless you already having something else.
- Also extract core0105.7z (this file has the pictures for the game) and cut the "Picture" folder you find inside there into the "RyonaRPG" folder you got from core0104.7z (it might be a folder or two deep). Basically, you want the "Picture" folder to be in the same place as the "RPG_RT.exe". You're combining the two files to create a complete game.
Source/Version control is the way to go. You don't ever want to find your work overwritten by someone else. I've used tortoiseSVN and have been looking for something else that is also easy to use.