Storing Wikijs Container Data On NFS share
HTML-код
- Опубликовано: 20 сен 2024
- In this video I show how to create a docker-compose file and where I got my information from. This way people can use this to make their own containers in the future. The container used is wikijs but should work for many different containers that need to have data stored else where.
wikijs: ( js.wiki/ )
NFS docker: ( phoenixnap.com... )
docker volumes: ( docs.docker.co... )
I've watched your entire series so far. Nice, easy-going presentation (sneezing edits aside, lol). Great bite-size nuggest to get things up and going. It's given me the nudge I needed to refresh my home lab. HP 800 G3's arrived yesterday. Docker, Portainer, and Pi-hole were first on my list. Plex is next. Thank you again.
That is great to hear! Thank you for watching it means a lot!
Yeah I sneezed during a great take where i knew it would a bit difficult to rerecord it made me so mad, I was sooo close to being done with the take. I am trying to keep the videos below 30 mins, so the videos are detailed, but not overwhelming. Part of the reason I started making videos is to motivate me to work in my home lab more.
Personally I don't watch many movies or TV shows so I haven't ever really touched plex or jellyfin until I started this channel, now I am using jellyfin to learn it in order to do a series on it potently. That would be a bit down the road tho since I only want to make videos on things I am comfortable with.
I don't really watch live TV or anything these days too, but I converted my DVD collection into a library that I can access easier these days (still have the DVDs in a box). Plex made this SO much easier to manage, watch, search, index and have running in the background.
Thanks for your wikijs video too. I work in a documentation mindset as well, and this was a nice step forward. I like using Portainer since you've started me on that. I wouldn't mind seeing some other videos that detail more about the networking in portainer (bridge/host/ipvlan/etc..), perhaps even some other projects that could be useful in the homelab.
One that I recently in a small VM (vs container) was an in-house Phone-Gallery sync to my NAS. Don't like iCloud or Google Photos, but want to auto-save pictures that I've taken.
Whatever you choose, good luck and thank you.
@@Joshuancsu Yeah I have thought about going over things like container networking, but haven't found a graceful way of making the video. I have tried to write the script, but the it ends up being a bit in complete since I am not an expert on containers networking just a gut passionate for homelab.
Also look into ARM ( github.com/automatic-ripping-machine/automatic-ripping-machine ) if you still have DVDs to rip I haven't personally used it, but a friend of mine at my local LInux User Group said it saved him tons of time.
I have experience with Nextcloud for saving photos that my wife and I take, but nothing really outside of that. Ask Noah Show podcast mentioned a photo gallery a few months back that sounds like it would be perfect, but I can not for the life of me find the episode where it was mentioned. I will comment back if I do find it. I found it already it is immich. Here is the episode of Ask Noah Show if you would like to see what their option is on it ( podcast.asknoahshow.com/335 )
Is it possible to use and connect to an already existing database? So that the database is centralized instead of installing new database engine on each docker app that requires the sama database (postgresql in this case).
Thank you so much for the videos, I really enjoy them and learned a lot from you.
I am no a DBA so I can't give you a perfect answer, but from my understanding yes you should be able to. I have not personally done it as I find it easier in a homelab to just have them separated. Also I have seem over my limit time playing with docker that people tend to prefer running databases that are larger outside of a container say on a VM or even on hardware. I am not 100% sure why this is, but I have assumed it has to do with reliability I have no idea really.
The way I tend to look at it is that Docker is for Micro services and I don't want to maintain some large database. I would rather have many small databases. It also helps make sure an issue with one container doesn't effect all of your services. Say the off chance that a service is hacked due to a day zero or some exploit I wouldn't want that to expose all of my databases potentially.
Also in homelab if you were to mess up badly enough with one DB you could ruin more that just one service.
A bit of reading for you as well about microservices and potential issues:
microservices.io/patterns/data/database-per-service.html
microservices.io/patterns/data/database-per-service.html]