Frank Elsinga

Rebased this PR in https://github.com/louislam/uptime-kuma/pull/4813 to remove the uninteded changes

@hoerup Could you explain more why this cannot be used and what would be needed?

> I was wondering if there was anything I could do to help this along @kn100 v2.0 comes with `...-rootless` images. I would like to see if the issue is...

@jeremyrnelson Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing **what needs to be done how by whom**....

@LoudSoftware @bitsky6 @RisedSky @InsaneSplash Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done...

Reviewing walls of texts is always difficult. If I missed something, feel free to ping. In general, I have a preference for more, shorter pull requests, as this way changes...

> how is this Feature req. sitting on the backseat. As with all other open-source projects, we rely on contributions. Our contribution guide [can be found here](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md). If that is...

@jco-c We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #1089 as this request can be added via the...

@chakflying I need a second opinion. I think this can be implemented via #1089 by adding a monitor which is deemed "reliable". => No need to add a second, mechanism...

As stated above, you can add a password in front of the dashboard and the "api"-response in a reverse proxy. Without user management, adding a password protection in front of...