4 ms·
S3 does not allow random access reads/writes to the files. "Editing" a file in S3 just means deleting the original blob and creating a new one. Meaning, you ca
by jakewins 10y ago
S3 does not allow random access reads/writes to the files. "Editing" a file in S3 just means deleting the original blob and creating a new one.
Meaning, you can't run git on it, you'd need to make a full copy of the repo each time someone makes a commit.
- alblue 10y agoThat isn't true; a git repository isn't just a single file. It is one (or many) pack and object files, and it's possible to have a repository by using each push (which may be multiple commits) to store a new pack file rather than deleting the old one. The only time you would need to delete/replace is during a GC operation which can be scheduled periodically to compact the representation. The JGit driver supports pushing to S3 in this way, and I have implemented a custom backend to hosting git repositories in an S3 like service (which in turn is based on how Google hosts git repositories at scale)