Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to be able to update my ec2 instance from a label in mercurial when it resets so my application is always set at the right revision.
It’d be great to be able to push my changes to a mercurial host and have my instances automatically update across the ec2 network when they are reset!
I really don’t want to host mercurial on the same instance (or even a dedicated instance)
What you want is Mercurial to natively support using S3 as a backend for data storage, and no such code exists. You could maybe find an S3 bridge to run in FUSE (or an S3->DAV bridge that you could possibly mount as a filesystem), and then tell Hg to push and pull data from that virtual filesystem, but otherwise you would need a dedicated ec2 instance to actually serve the data (you could launch it on demand, but the latency on that is pretty bad, as you probably well know).
There is a FUSE-based filesystem for S3 called s3fs, but it looks like it’s mainly a driver for a commercial offering.
(As a separate aside, depending on your ec2 architecture, and assuming you have overlapping uptimes on multiple instances, you could theoretically leverage the distributed nature of Hg to use your existing instances to pass the changes around amongst themselves, without a “root” repository. If you only have one instance, of course, this is a non-starter.)