herrfrutti @ herrfrutti @lemmy.world

Posts

3

Comments

42

Joined

2 yr. ago

I'm very happily running openhab!

Kneating is fine, i'm talking about scratching. My had to clarify that... my bad.

Don't be too angry with him! But tell him every time that he does something bad.

I'm just constantly telling my cat 'NO!'

I think I'm accustomed, lol

Closed!

Additionally making a funny sound to make sure someone wakes up

First, I think you can close that port. You don't need incoming traffic on that port.

I myself use Vaultwarden. But looking on the documentation you need to configure the enviroment correctly.

Florisboard

Works well, but struggeled when I tried sending 100+ files or a 80gb files folder. Don't know if my phone was the limitation factor, but the app crashed.

But a very cool software to easily and fast share some files!

Very nice write up. Thank you for sharing. One thing I like to add.

I've personally moved away from nginx proxy manager, because I read an article that it has some vulnerability that don't get fixed in time. Also there are a ton of issues open on git hub. So I move to caddy, witch also is super easy to set up.

I use tandoor, try it. I like it very much.

On their github they state that mayor releases take time. And there is activity on the github. So I think their working on it!

So if I selfhost an instance the proxy setting still would hit my hosted ip?

Fluffy Chat works great for me!

Audiobookshelf is quite nice too. The ebook reader isn't quite there yet, but it develops very fast. Also apps for Android and iOS

I've got myself a second router and created a second wifi and lan with it. All my smart home devices are in there and also the tv.

I found it. It's in the Account settings, under pin settings.

I've just posted a little example. I'd recommend doing it this way. No more thinking about what port is allready exposed etc

Caddy would have the bridge proxy network and the port 443 exposed.

    
version: "3.7"

networks:
  proxy-network:
    external: true
# needs to be created manually bevor running (docker create network proxy-network)
services:
  caddy:
    image: caddy
    container_name: caddy
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./data:/data
      - ./config:/config
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
    networks:
      - proxy-network

  

Other services:

    
version: "3.7"

networks:
  proxy-network:
    external: true

services:
  app:
    image: app
    container_name: app
    restart: unless-stopped
    volumes:
      - ./app-data:/data
    networks:
      - proxy-network

  

Caddy can now talk to the app with the apps container_name.

Caddyfile:

    
homepage.domain.de {
    reverse_proxy app:80
}

  

So the reverse proxy network is an extra network only for containers that need to be exposed.

If the containers are all in the same network. You dont need to expose a port.

Lets assume you create a docker network called reverse_proxy and add all your contaiers that you want to be accessed by the reverse proxy to that network (including caddy).

Then you can address all containers through the hostname in you caddy file and the port would be the default configurated port from the container.

So in the end you just expose the caddy container and nothing more.