Show HN: One click image optimization for GitHub

by mwarkentin • 12 years ago

34 52 12 years ago

Raphmedia• 12 years ago

What happens exactly when I click the button? It optimizes 50 images and put them in a separate commit?

mwarkentin25• 12 years ago

Basically! When you click on the button, it will spin up a bunch of workers (1 for every 10 images). These will optimize your images in parallel, and then push the changes back up to a branch and open a pull request for you to review.

There's no limit on the number of images - it can optimize hundreds quite quickly - 50 is the number of parallel workers you can have.

occam652• 12 years ago

Seems like a pretty useful tool, but I don't have any repos with images. Can anyone report on actual usage?

mwarkentin25• 12 years ago

You can check out an example of the pull request you'd get here: https://github.com/shrinkrayio/demo-images/pull/6

occam652• 12 years ago

Nice. Does it report total filesize reduction across the entire pull request?

mrbig45452• 12 years ago

i'm not sure what it is, or why i would want it. or even what kind of optimising it does

i'm not complaining, just suggesting that you should work on your homepage to make that crystal clear, it'll help with people who might want to use it but don't know it yet

mwarkentin25• 12 years ago

Thanks for the feedback - definitely know that there's lots of work to do. Planning on adding a short 30 second video running from sign up through to viewing the pull request.. surprisingly difficult to do smoothly without a bunch of "um" and "ah".

More work on clarifying things will definitely be happening.. I've just put off showing this to people for too long already. :)

mrbig45452• 12 years ago

Even one small paragraph will help, something like, "When you click on the button, it will spin up a bunch of workers (1 for every 10 images). These will optimize the filesize of your images in parallel, and then push the changes back up to a branch and open a pull request for you to review.

There's no limit on the number of images - it can optimize hundreds quite quickly - 50 is the number of parallel workers you can have"

(i stole this off another of your comments and added filesize after optimise)

lordbusiness2• 12 years ago

I'm assuming this is file size optimization for website use? It would be nice to see a video demo of this before I hand over my GitHub credentials. :-) Call me Mr. Paranoia if you wish; I apologize. I'm sure there are best intentions here.

Nice idea to be honest. Wish I'd thought of it. :-)

mwarkentin25• 12 years ago

Exactly - well, anywhere you have images which you want to make sure are as small as possible (without losing any quality). We've had some success running this against repos for iOS apps and reducing the size of the bundle.

Definitely planning on making a short demo video soon!

lordbusiness2• 12 years ago

Sounds good to me! Keep up the happy hacking. :-)

gingerlime• 12 years ago

Interesting idea and quite clever way to integrate it with github. Very nice.

Does it cost money? (if so, how much? if not, would it cost in future?) Does it continuously monitor all images or can be launched as a one-off task? I think some details are still missing.

mwarkentin25• 12 years ago

At the moment it's free for both public and private repos, but the plan is to follow the standard "Github tool" pricing (free for open source, paid for private / organization support). Happy to hear what people think they or their business would be willing to pay for a tool like this. :)

Right now it's a one-off task, but I've done some work on using Github webhooks to trigger image optimizations directly on a branch while you're working on it. Not sure when this will be available though.

colinbartlett2• 12 years ago

I just used it and I really like it. What would I pay for it is a harder question. Recurring charges are more difficult for me to swallow, but I would be willing to pay the equivalent of a few coffees or beers every time I used it.

Rygu• 12 years ago

Fun side-project, kudos. Also for humans: https://imageoptim.com/

mwarkentin25• 12 years ago

Yep, there are definitely a bunch of ways to do this. A few of the reasons I made this rather than just using a CLI tool:

* Speed - spinning up a bunch of workers to do this can optimize large repos a lot faster than my laptop * CPU - optimizing images on my laptop can really max out the CPU, turning on the fan, using up battery * Stats - I've wanted to make reports to send around to the company on the optimizations that were made - was quite hacky to pull this from a CLI report into something that could be shared

perlgeek• 12 years ago

I hate giving out write access to my repos to somebody I don't know. How about creating pull requests automatically instead?

mwarkentin25• 12 years ago

Yeah, understood that this could be an issue for people. I'd like to at least be able to split out granting access to public / private repos - although write to public could still be an issue..

What do you mean by creating PRs automatically instead?

frabcus• 12 years ago

You could always fork repos to your own robot account, and then do the pull request from there.

jrochkind14• 12 years ago

It sounds like creating PR's is what you're doing, from other people's reports? Which is great.

But Github tells me I'm about to grant you permissions to make commits directly to all my repos.

Can you ask for fewer permissions from github?

I haven't tried it myself yet, because it gave me a bad feeling giving you such permissions. (the permissions sound like they give full git commit access, which would of course include rewriting history. To a random third party? That seems like a terrible idea. If someone wanted to release such a service and use it to inject security vulnerabilities in everyone's (or just some specific targets) code....)

colinbartlett2• 12 years ago

I just used this on my repo and that's exactly what it did. It created a PR. I then reviewed the PR, squashed the commits down to a single one and merged it.

It worked beautifully. 10/10 would use again.

jrochkind14• 12 years ago

Sweet, this is much better, and a perfect use of PRs.

I wonder if it needs to ask for github 'write' permissions in order to do this, or if it could be changed to just ask for read permission and make PRs? If Githubs permissions don't work that way, they should be fixed -- if they do, this tool should be fixed.

When I logged in via oath or whatever, Github warns:

This application will be able to read and write all public and private repo data. This includes the following:
Code; Issues; Pull requests; ...

Yeah, I don't really wanna do that. Granting a random third-party else permission to commit to all of your repos, public and private?

sauere3• 12 years ago

This. Your service is fine for some small projects but a large, widely-used Repo cant just grant some "random" site full access to the code.

Anyway, i like the idea.

mwarkentin25• 12 years ago

Yeah, for some people it might make more sense as a self-hosted thing.. not sure how hard that would be to do though. :)

domedefelice• 12 years ago

Gaining the confidence of the user is not easy:

1) I think you should state explicitly that the compression is lossless (if it is);

2) You should provide some kind of demos/examples to look at.

Good job anyway!

mwarkentin25• 12 years ago

Image compression is lossless.. I really should call that out on the home page. Demo / examples are definitely on my list.. here's an example PR for you: https://github.com/shrinkrayio/demo-images/pull/6

sauere3• 12 years ago

Also, do you preserve metadata (EXIF etc.)?

benbristow• 12 years ago

It would be nice to see a BitBucket version as well. Mainly because I keep my private repos on BitBucket since it's free and then do any open-source stuff on GitHub.

mwarkentin25• 12 years ago

It's something I may look at eventually, but not a priority right now - Github has a lot more users, and it would increase the complexity quite a bit to deal with two separate systems for permissions, APIs, etc.

Thanks for the feedback though!

mcmillion• 12 years ago

Awesome idea, but this should really be a build step, not something people run manually, and definitely not touching the source images.

mwarkentin25• 12 years ago

Yep, if you've got something like this set up as a build step, good on you! A lot of places don't, so this was made as an easy way to reduce your image footprint. It's amazing how much can be saved sometimes.

MichaelTieso• 12 years ago

After clicking on "shrink all images" it goes to say "warming up" but nothing happens.

mwarkentin25• 12 years ago

Yeah, looks like I'm out of capacity on my workers right now - this is the first real burst of traffic I've had.

As far as I can tell, all jobs are either queued or running, so it should complete for you at some point.. not sure if I can get an ETA for you though.

mwarkentin25• 12 years ago

Hey Michael, it looks like there were some errors with a few optimization jobs, including one of yours. If you want, you can try re-queuing the job by refreshing and then clicking on the button again.

mwarkentin25• 12 years ago

Sorry to anyone who this seems to be hanging for - it looks like my workers have gone over their capacity, and things are pretty queued up. I'm checking into increasing capacity, but in the meantime things may take longer than expected.

mwarkentin25• 12 years ago

Ok, it looks like the queue has cleared up for now. There were a few errors, so if one of your requests didn't complete, feel free to retry.

jbox2• 12 years ago

Cool tool!

I gave it a shot on one of our private repos this morning and it did what it said on the box.

In the process it also generated ~150 comments on the repo.

For folks watching the repo, this is a fair amount of email.

Is there anyway to aggregate the comments? Perhaps into the Pull Request description?

mwarkentin25• 12 years ago

Thanks for trying it out.. sorry about the spam. When I added the parallelization of the tasks, I kind of lost the ability to manage things centrally on Github. I'll think about if there's some way to make this better.

Increasing the number of images per task would reduce the number of commits / comments, but could also increase the amount of time it takes to complete.

Did the commits themselves cause email issues for you, or was it just the comments? I could look into appending to the PR description instead of adding comments - I'm just worried about a race condition when multiple tasks are trying to update the description at the same time.

jbox2• 12 years ago

No worries! It worked, we just got a lot of emails :)

Could you aggregate the messages and post an update when the entire task is complete?

Seeing the commits come seems to be a good progress indicator.

If you are "watching" a repo, you get an notification for every comment, not every commit.

You could also just create the PR with a link to the job on ShrinkRay and have the progress updates there...

Show HN: One click image optimization for GitHub

Related Stories