![](https://lemmy.world/pictrs/image/70c5fe07-4a33-494a-b67b-164287421a94.jpeg)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Personally, literally some postit notes for my own selfhosted projects
Personally, literally some postit notes for my own selfhosted projects
And watch, literally nothing happens. Are you paranoid you’re being personally watched and followed?
Have you considered an implantable NFC chip in his hand?
Ive not shared mine to the point anyone can arbitrarily get media. They have to ask. And I can always say “Oh its not available on my sources” or whatever
Unfortunately not in this example. It has the compose to spin up masto, and the variables to set to tell it where redis etc is
You will need to review all the required variables and configure as you require. But basically, yeah
EDIT - NO
its not just grab and run. From the docs,
This container requires separate postgres and redis instances to run.
If youre looking for a sample docker-compose,
Some things, or points, to consider.
good luck have fun!
Correct terminology makes your eyes hurt?
NPM as in nginx and not Node Package Manager?
When you said Jellyfin streaming isn’t working - are you able to actually get to Jellyfin UI and its the stream failing, or you can’t access Jellyfin at all via nginx?
When you tried caddy and received an error, that looks like you are getting the wrong image name.
Then you mentioned deleting caddyfile as the configuration didn’t work. But, if I am following correctly the caddyfile wouldn’t yet be relevant if the caddy container hadn’t actually ran.
Pulling from Caddys docs, you should just need to run
$ docker run -d -p 80:80 \
-v $PWD/Caddyfile:/etc/caddy/Caddyfile \
-v caddy_data:/data \
caddy
Where $PWD is the current directory the terminal is currently in.
Further docs for then configuring for HTTPs you can find here under
Automatic TLS with the Caddy image
I personally found IRC to be the best solution for ebooks. Not sure how much detail/links are allowed here but theres plenty of guides. Look for “IRCHighway ebooks” on your preferred search engine
Like other commenter said, regardless of podman or docker you will need to handle port forwarding, and any firewall changes.
Port forwarding through docker or podman is pretty similar, if not identical.
I have heard good things about podman but I personally had some strange issues when moving from docker to podman, specifically transferring docker networks to the podman equivalent.
What sort of advice are you looking for? Buy the OLED for the reasons you gave. Get a partial refund and get games.
Flip a coin?
When I am home Ill get an example from my setup 👍
On my phone so I haven’t got the access to give you a good example.
You see in your compose file in your original post you have ‘8080:8080’ under ports?
You should be able to add another line, the left hand side of the colon exposing a different port like so
…
ports:
- ‘8080:8080’
- ‘9090:9090’
…
then one service you can access on port 8080 and the other you access on 9090
then under each service you want to expose you add the other port mappings
qtorrent:
ports:
- 8080:8080
sabnzb:
ports:
- 9090:8080
edit - so you should end up with the vpn container exposing 8080 which points to the service exposing 8080 which maps to application listening on 8080
and the same for 9090 -> 9090 -> 8080
In the VPN service you just expose the port you want and map it to the listener port on the service
vpn: ports: - 5000:8080 - 6000:8080
where you have
servicea listening on 8080 and serviceB on 8080 but exposed on 5000 and 6000 in the VPN service
for example
You can also map different ports to the container. For sake of argument lets say qtorrent had a fixed port you cannot change, that’s just what the application listens to. You can then map a different container port to that application port.
tldr, OP, you can’t have two containers in docker on the same container port
Infisical?
https://github.com/Infisical/infisical