http://code.secondbit.org/infra/codestorage/hg-repo-sync/ en-us infra/codestorage/hg-repo-sync Changelog http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/32a993adf753 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/32a993adf753 changeset 32a993adf753 branch default bookmark tag tip user Paddy <paddy@impractical.co> description Fix nested repository permissions.

For repositories nested inside folders, fix the permissions on the folders so we
can create other repositories inside them. Before, we only fixed the permissions
on the repositories themselves; now we also fix the root directory that holds
the repository. files pull.sh
]]> Paddy <paddy@impractical.co> Thu, 12 Nov 2015 21:31:15 -0800 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/c8b4b952488a http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/c8b4b952488a changeset c8b4b952488a branch bookmark tag user Paddy <paddy@secondbit.org> description Remove the hgrc file, fix permissions.

When pulling backups, make sure we set the permissions to 0770 as well as change
the group they belong to. This caused us to not be able to write changes (oops).

Also, remove the hgrc file. Which means our annoying "not trusting file
/mounted/repos/blah-blah/.hg/hgrc from untrusted user root, group committers"
message is back, but that's a minor nuisance. The real issue is that we're
overwriting the hgrc for everything _anyways_ to get the push hook, etc. So
there seemed to be little point. files Dockerfile
hgrc
pull.sh
]]> Paddy <paddy@secondbit.org> Wed, 14 Oct 2015 23:04:31 -0700 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/9cc2f3a01ab5 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/9cc2f3a01ab5 changeset 9cc2f3a01ab5 branch bookmark tag user Paddy <paddy@secondbit.org> description Use pip to install Mercurial, pin to 3.5.2

We want to use a relatively recent (but consistent) version of Mercurial, so I
had to switch to using pip to install Mercurial, so I could pin it to version
3.5.2. apt-get didn't have version 3 available. files Dockerfile
]]> Paddy <paddy@secondbit.org> Sun, 11 Oct 2015 16:52:32 -0700 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/cc08c8ed2128 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/cc08c8ed2128 changeset cc08c8ed2128 branch bookmark tag user Paddy <paddy@secondbit.org> description Update to be more modular.

We now have a more modular approach to running our mercurial servers, and the
approach to the individual containers is a bit more modular as well. The
hg-repo-sync container now has a few responsibilities:

1. Install Mercurial
2. Create the group that’s going to be writing all our files
3. Create the folders we’ll store files in, and make the new group the owner
4. Define a script that pulls repos from GCS to local disk
5. Define a script that pushes repos to GCS from local disk
6. Define a script that causes a delay between runs

This mainly involved breaking the previous run script into a few separate
scripts, so they could be invoked individually.

This docker container _can_ be used as a standalone image that will keep the
local disk in sync with GCS, but it’s more useful as a base image for our other
containers to work off of to achieve specialised functionality. files Dockerfile
pull.sh
push.sh
run.sh
sleep.sh
]]> Paddy <paddy@secondbit.org> Sun, 11 Oct 2015 03:48:40 -0700 http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/d8c86bc750ad http://code.secondbit.org/infra/codestorage/hg-repo-sync/rev/d8c86bc750ad changeset d8c86bc750ad branch bookmark tag user Paddy <paddy@secondbit.org> description First commit.

This contains the basic implementation of hg-repo-sync, which is only useful
when you want to do a constant two-way sync every few minutes to Google Cloud
Storage. It also hardcodes more than it should.

But it's running on code.secondbit.org without issue, so it should probably be
preserved. files .hgignore
Dockerfile
hgrc
run.sh
]]> Paddy <paddy@secondbit.org> Mon, 17 Aug 2015 18:56:19 -0400