Amazon EC2 上实际上是否有任何 Mercurial 托管？
我需要能够在重置时从 Mercurial 中的标签更新我的 ec2 实例，以便我的应用程序始终设置为正确的版本。
如果能够将我的更改推送到 Mercurial 主机，并在重置时让我的实例在 ec2 网络上自动更新，那就太棒了！
我真的不想在同一个实例（甚至是专用实例）上托管 Mercurial
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)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您想要的是 Mercurial 原生支持使用 S3 作为数据存储的后端，但不存在这样的代码。您也许可以找到一个在FUSE（或S3- >DAV 桥，您可以将其安装为文件系统），然后告诉 Hg 从该虚拟文件系统推送和提取数据，但否则您将需要一个专用的 ec2 实例来实际提供数据（您可以按需启动它，但延迟非常糟糕，您可能很清楚）。
S3 有一个基于 FUSE 的文件系统，称为 s3fs，但看起来它主要是一个商业产品的驱动程序。
（另外，根据您的 ec2 架构，并假设您在多个实例上有重叠的正常运行时间，理论上您可以利用 Hg 的分布式特性来使用现有实例在它们之间传递更改，而无需“根”存储库如果你只有一个实例，当然这是不可能的。）
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.)