nils måsén

I personally don't think such a solution belongs inside watchtower, especially since it's interacting with a closed down proprietary system. It should be possible to accomplish with #1231 though...

This looks really nice! I would probably prefer the frontend stuff to be moved to it's own repo though. Not sure about what to do with the distribution though... @simskij,...

Why are you not using a package.json and including the dependencies as static libs? If the content are to be included in the container image they should probably be processed...

> I chose not to use npm in an effort to reduce the overall complexity of the PR. Ideally, for larger projects, I agree that one should use a package...

> I made an attempt to make the API URL also work in non-local environments. Please forgive my Go skills, I haven't used it before... :) Check the [Codacy Analysis](https://app.codacy.com/gh/containrrr/watchtower/pullRequest?prid=10547431)...

> Currently when the API is checking for updates it also pulls any new images. This could take some time, and I was wondering if it would be better UX...

Sorry for not keeping up with this, I have been busy with work. I will help get this merged as soon as I get some free time :)

This PR currently make some changes to the API that affects other functions of watchtower. I started working on splitting the new functionality out to new APIs, but it grew...

Please fill in the form. What configuration are you using? How are you starting watchtower? Did this work on a previous version?

@obzocker I'm not sure what you mean... The docs explain why it's pulling the image. There could be code added that would skip the pulling for monitor-only, but it's not...