mealie VS Nginx Proxy Manager

Mealie can be found at https://github.com/mealie-recipes/mealie and Mealie Client at https://github.com/kirmanak/Mealient

If one of them cooks, spin up a mealie instance for them. I made my mom her own after she saw some recipes on mine. And she uses it all the time. Mealie Github

When you get stuck like this, always look at the docker-compose.yml file if provided. You can find this one here: https://github.com/mealie-recipes/mealie/blob/mealie-next/docker/docker-compose.yml

I tried the official docker compose from the Github page (https://github.com/hay-kot/mealie/blob/mealie-next/docker/docker-compose.yml), I git cloned the whole mealie folder (https://github.com/hay-kot/mealie.git) and got a whole host of issues or what seems like lots of issues. The only changes I made were to change the username and password under the postgres config. When I docker compose up the file I get the error message below (all the way at the end of this post). With the git clone I should have all of the dependencies and I am just not sure what these errors are telling me.

So far I am hosting my own photo backup and sharing (think Google Photos replacement, except the data just goes straight from my phone to a server that I have in my closet), a media server for streaming my own videos, and an awesome cloud recipe book to share with family (https://nightly.mealie.io/).

Personally I run mealie as a digital recipe book - https://github.com/hay-kot/mealie

For some time I've been making use of an open source recipe management tool called Mealie. You can find the code at https://github.com/hay-kot/mealie

The in my opinion best way is to contribute to software you already use. In my case that's self-hosted stuff like Mealie or Owncast.

Not possible for the moment but an issue is open https://github.com/hay-kot/mealie/issues/2161

I discovered these 3 amazing projects recently:

Cryptpad, essentially google docs/sheets/forms e2e encrypted. It does include collaboration. https://github.com/cryptpad/cryptpad

Immich, google photos self hostable, with share options https://github.com/immich-app/immich

Nginxproxymanager manages certificates and proxies to self hosted stuff through nginx https://github.com/NginxProxyManager/nginx-proxy-manager

Great self hosting stuff!

Nginx Proxy Manager

Take a look at NginxProxyManager. This would give you the opportunity to put everything in the form of service1.domain.com , service2.domain.com ,etc.

Prime example: Nginx Proxy Manager is often recommended in the sub. The latest minor release came with breaking changes (so already ignoring semver). I bet you many people were running on latest and then had broken stuff: https://github.com/NginxProxyManager/nginx-proxy-manager/releases/tag/v2.10.0

I started looking into how to make add dynamic IPs to NPM access lists. I came across a couple of GitHub issues (1, 2) on the topic. It looks like people have solved the problem, but not in a complete way without modifying the NPM docker image. I did not want to do that, so decided looking into writing a separate script.

Here is the (NPM) GitHub issue where the "fork of a fork" image came into existence (lepresidente/nginx-proxy-manager). It has some interesting discussions about the challenges of having NPM and CrowdSec coexist and cooperate.

Agree with this, myQ is such a dumpster fire. It needs to have an the ability to be managed over the local network instead of requiring the garage door and app connect to their server.

My very first experience with myQ was figuring out that their IP blocklist provider, brightcloud, blocks anything with the word "proxy" - including the default "it works" page for Nginx Proxy Manager [1]. And they have no way of overriding this to actually provide service if someone turns out to be a legitimate customer.

[1]: https://github.com/NginxProxyManager/nginx-proxy-manager/dis...

Edit: If you're using Nginx Proxy Manager there seems to be open PR for support for proxy protocol https://github.com/NginxProxyManager/nginx-proxy-manager/pull/1882 however in the comments there's a name of repository with this PR merged.