simple version control and collaboration
darcs makes version control simple. darcs hub provides easy repo hosting and collaboration for darcs users, and is 100% FOSS software and a community service you can contribute to ( issues, code, docs ). The philosophy here is Less But Better. Enjoy the simplicity of darcs hub!
Darcs is a version control system, broadly similar to Git, Mercurial and others, but with a simpler conceptual model that many people find less costly to learn and use. If you don't have a lot of time to spend learning your version control tool, darcs (and darcs hub) may be a good choice.
Darcs hub is the free darcs repository hosting site operated since 2012 by Simon Michael. It succeeds the older patch-tag.com and darcsden.com sites. It aims to:
provide a reliable, usable and evolving hosting and collaboration hub for darcs users
accelerate the development of darcs and its ecosystem, eg through an easier contribution process and increased visibility and dogfooding.
Darcs hub is currently an all-volunteer effort by Simon Michael with help from the darcs team. However it's robust enough to host your project and to depend on for daily work. We currently host about 800 users and 1600 repos.
Currently, the stability is that of a usable beta; you can expect a serviceable UI, some functionality and performance limitations, decent reliability, and no data loss. Uptime and response time are checked every minute (see link in the footer).
As with all cloud-based services, it's wise to (a) keep your own backups of important data and (b) assume no guarantee of security or privacy. The site is hosted in the US. We do our best and all improvements are welcome.
The roadmap gives some more overview.
The VPS running hub.darcs.net and other sites is backed up nightly, between 0100 and 0300 GMT-8, by Linode's backup system. This keeps three backup images: the one from last night, the one from last Sunday, and the one from the previous Sunday. In other words, there is generally a backup that's one day old, and a backup that's 1-2 weeks old.
You should also keep your own backup(s) of your repositories. Basically, keep one or more copies of the repo elsewhere and up to date, using darcs get and darcs pull. (If you decide to automate this, don't forget to plan for the scenario where someone cracks your darcs hub account, logs in as you and quietly obliterates or modifies your repos.)
Use hub.darcs.net and provide bug reports and feedback
Investigate and clarify open issues
Test the setup process by setting up your own instance:
Contribute code and documentation patches. This is a fun project! It's a web app, so there's quick visual feedback. It's darcs-related, but easier to understand than darcs itself. Developers are online in #darcs, and useful changes will be quickly deployed to this site.
Also each of the repositories hosted here has its own changes page and feed. Here are a few interesting ones: darcs-reviewed, darcs-screened, darcs-wiki, darcsden, divine-mainline, dnplayer, globalscript, happstack, netwire
Via HTTP - works for any public repo and requires no authentication. Examples:
darcs get http://hub.darcs.net/OWNER/REPO darcs get http://hub.darcs.net/simon/darcsden
darcs get [YOU@]hub.darcs.net:[OWNER/]REPO darcs get hub.darcs.net:simon/darcsden darcs get hub.darcs.net:myrepo
YOU is your darcs hub username; you can omit it if it's the same as your local username. OWNER/ can be omitted if the repo is yours.
Then test your ssh access like so:
$ ssh YOU@hub.darcs.net
But, the ssh lib we use will probably require special configuration of your ssh client. Eg on unix, add these lines to
Host hub.darcs.net ControlMaster no ForwardAgent no ForwardX11 no Ciphers +aes256-cbc MACs +hmac-sha1
Also, we only support RSA ssh keys at the moment. If your usual ssh key is eg ED25519, you will need to generate a RSA key for connecting to darcs hub:
$ ssh-keygen -t rsa -f ~/.ssh/darcshub
and add this to the ssh config above to make sure the RSA key is used:
If in the past you added
KexAlgorithms +diffie-hellman-group1-sha1 based on this obsolete advice, you should remove it.
On first connection you will probably be asked to authenticate our host key:
The authenticity of host 'hub.darcs.net (22.214.171.124)' can't be established. RSA key fingerprint is SHA256:3eBJH9dB8ez4tJuxmnEP7dNHRRTk2BAKPuUmcGaoAAM. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'hub.darcs.net,126.96.36.199' (RSA) to the list of known hosts.
The IP address and fingerprint should be as shown above.
Returning users might see loud warnings about the remote host idenfication having changed, due to a server migration in 2018/06. To fix this, try:
$ ssh-keygen -R hub.darcs.net # remove hub.darcs.net entry from known_hosts $ ssh-keygen -R 188.8.131.52 # remove entry for the old IP address $ ssh-keygen -R 184.108.40.206 # remove any out-of-date entry for the new IP address
On a successful ssh connection, you should see ("failed" is normal as we don't provide shell access):
PTY allocation request failed on channel 0 shell request failed on channel 0
Otherwise, add the
-v flag to help troubleshoot the issue:
$ ssh YOU@hub.darcs.net -v
Once you've got a local copy of a repo, you can merge any new changes from the upstream repo on darcs hub by running:
in your repo. It uses the original get address by default.
Pushing requires SSH access. If you got the repo via SSH, just
If you got it via HTTP, you must configure ssh access and then push to the SSH address:
darcs push [YOU@]hub.darcs.net:[OWNER/]REPO [--set-default]
--set-default flag will make it remember this as the upstream address, so you can just type
darcs push in future.
You can push to someone else's repo if they've added you as a repo member in the repo settings. Otherwise, make a fork of their repo and push to that, so they can review and merge your changes themselves (on their repo branches page).
ssh [YOU@]hub.darcs.net init REPO DESCRIPTION(or: log in -> my repos -> new repo)
darcs push -a [YOU@]hub.darcs.net:REPO
In your repo's settings, you can add other darcs hub users as members. They will be able to push to your repo (but not delete changes from it, nor change its settings), and view it even if it's private.
ssh [YOU@]hub.darcs.net obliterate REPO
darcs obliterate in your repo on hub, prompting interactively for each change, most recently pushed first. You must be the repo owner, not just a member. Options like
--dry-run are not supported, so you'll sometimes have to figure out which later depending patches also need to be selected for obliteration. Another option is to obliterate locally, then delete the hub repo and re-publish it.
Obliterate rewrites your repo's history, so be mindful - if others have forked your repo and you obliterate, they'll need to do the same or the change will show up again in your branches page.
Click the file name in the page heading. Currently this forces the text/plain content type.
/atom to the changes url. Eg http://hub.darcs.net/simon/darcsden/changes/atom.
After pushing some patches to your fork of someone's repo, those patches will automatically appear in the branches page of the parent repo. However, the parent repo's owner may not notice. Currently there are two ways to notify them:
track down their email or IRC name and ping them. Eg look for a nick in #darcs matching their hub username, or check the READMEs in their public repos.
if the parent repo has its darcs hub issue tracker enabled, you can open a new issue and attach your new patches as a bundle - this will send them a notification email
When a patch is pushed to an issue-tracker-enabled repo, and the patch name contains a reference to an open issue, that issue will be closed automatically, and the commit will be mentioned in an issue comment. Here is the syntax. Some valid examples:
some patch (closes #1) resolves #52, blah blah this fixes #100 I think
I think the following are not yet supported: