This is a command-line focused guide. If you'd like to see how to get started using a GUI on Windows, try this instead.
Creating a repository
Choose your favorite projects folder, or temp, or whatever. Let's
say you've chosen
Two things happened: a
Who am I?
We should tell Veracity who you are. Run
The --create flag will try to create the user first, so you will only need to use that flag the first time you run whoami.
Adding some stuff
Let's give Veracity something to do. Create a file:
and you should see
"Found" means Veracity sees a file it doesn't yet know about. "@/" is the root of the repository. To tell Veracity to keep track of this file:
Let's commit that to the repository, so we can play with it a bit.
Things we can now do:
All of which must be followed by a
If you change the file on disk, e.g.
Running the server
So far, this is all local. To share your code and changes with others, you'll need to run a server, or connect to someone else's. For now, you'll be the server.
Still in your
Veracity's internal web server is up and running on Port 8080. Open a browser (not IE, just yet, but Chrome, Safari, Firefox should work nicely) and you can see your history, add work items, and so on.
Playing with Others
What you can also do is push and pull code through this server.
Assuming the machine you've been using is
On the client, to get a working copy of that same code:
And you're in a working copy of a clone of the original repo.
Make your own local changes, commit them, then:
to send them back to the host. If you see an error complaining that this would create multiple heads, that means there are changes on the host side that you haven't pulled yet. Get those, merge them locally, then push. Actually, it's a better idea to always pull, merge, run unit tests, and commit the merge before pushing.
This answer is marked "community wiki".