用敏感信息独自开发应用程序

Question

I'm making myself an app with Android Studio. It will have sensitive information (like social security number etc.) and I don't have any private repos on sites like Github. What is the best option for version control? I will be the only developer.

Can Git and SVN be setup to use the local computer or do they need a remote server? Would it make sense even considering Git as it seems like the main advantage is the ability to push once back online?

Answer 1

Since you are using Git for version control, below are the options for you to manage your git repo privately.

Option 1: Hosted remote repo to 3rd-party companies where private git repos are free

For Github, you need additional pays to use priavte git repos. While, you can hosted your remote git repo to other place where the private git repos are free. Such as you can use bitbucket instead. You can select to create private/public repo freely.

Option 2: Setup remote repo by yourself

You can setup your own remote repo by git into --bare , and then push the changes to your own remote repo. And if you have server(s), you can setup the git repo there, so that only the people who can access to your server have permission to access your git repo.

Answer 2

You can use Subversion locally without any server. Subversion client can access the repository via file:// access schema.

This approach should work in case there is only one or a couple of users who plan to use the repository. It will be simple to move the repository to a cloud or on-premise SVN server.

Answer 3

Well, svn has to have a server process to connect to. I guess it's up to you whether that is hosted on a remote computer, or on your desktop.

By contrast, git doesn't require a server of any sort. Its functionality is completely local. It does define protocols for sharing objects (ie your history, more or less) with other repos if you want, and those repos can be on a remote computer if you want, but all actual source control functions are local.

So while git's design is motivated by the need for ludicrously distributed development on a project like the Linux kernel, it's also a perfectly sensible option when you just want to work locally (with the caveat that if there's only one local copy of the repo database, then you're data is only as protected as the backups you keep of your local system).

Not sure what leads you to think that the ability to work in isolation and then sync up with a remote later is the "main" advantage of git.