dmfutcher / git-s3-push Goto Github PK

I was trying to use, but need to specify a specific profile with a token (mfa). Any plans for support on this?

Current release breaks on High Sierra. I did a manual rebuild and it works. So a new download for High Sierra would be great.

Not sure why this is happening, but it keeps sending the files whether or not they are updated.

The magicmime dependency needs the header files from libmagic to build. I fixed this on my environment by installing libmagic with my package manager.

Seems like this is probably just something we need developers to do as a manual step (can't imagine the go tooling is going to install this for us) so I propose splitting out the existing build instructions in Installation into a new section which also includes this requirement.

Happy to submit a PR for this if you agree with the approach!

Trying out git-s3-push for a personal Jekyll site on S3. Tool works fine (thanks!) but the sidecar file that stores the settings gets uploaded to s3 along with the content. Suggest that this file is ignored by default.

Add an option to specify a path prefix for the bucket key ie. allow pushing git repos into sub-folders of S3 buckets. This would allow, for example, storage of multiple git repos in a single S3 bucket.

Should update the git-s3-push command to check for deleted files and delete those files in s3. Currently the git-s3-push command does not have a delete functionality when a commit includes deletion of files.

CSS gets set to mimetype text/plain instead of text/css which screws up the browser. Is there any way to change this behavior or is this a code issue? I'm guessing this is something coming from libmagic so maybe there is configuration I can do?

There are currently 0 (zero) tests for git-s3-push.

Would be great to add:

• Unit testing for whichever chunks of code make sense to unit test
• End-to-end test to run git-s3-push against some example git repos and check the correct files end up in a test S3 bucket.

Hi, @bobbo!

Just wanted to ask you, did you consider to use custom git protocol (e.g. git-remote-<name>) instead of making a separate tool for the task? It looks for me that it might provide much better user experience.

What I'm thinking now is something like:

% git add remote production s3://<region>/<my-bucket-name>
... write some code, as usual
% git commit -a -m 'release'
% git push production

What this particular push call should do is to invoke

% git-remote-s3 production s3://<region>/<my-bucket-name>

so git-remote-s3 (former git-s3-push) could parse region and bucket from the passed "url" and deploy the code.

Does this kind of tool look like the one that makes sense? What do you think?

See this post https://rovaughn.github.io/2015-2-9.html with some additional explanation about custom protocols in git.

MacOS binary release is missing for 0.2.0. Will create next opportunity I have.

CC @Willjfield (#2 (comment))

I find that git-s3-push works well except that my html, css and js files are given the filetype binary/octet-stream. This means that I have to instruct AWS to change the filetype so that my website can be served properly :-(

Hi there,

looks like it still requires a dependency - libmagic

$ ./git-s3-push
dyld: Library not loaded: /usr/local/opt/libmagic/lib/libmagic.1.dylib

$ brew install libmagic
==> Downloading https://homebrew.bintray.com/bottles/libmagic-5.30.sierra.bottle.tar.gz
######################################################################## 100.0%
==> Pouring libmagic-5.30.sierra.bottle.tar.gz
==> Using the sandbox

$ ./git-s3-push --help
stat /Users/XXXX/.git: no such file or directory