I'm in the process of configuring a Raspberry Pi to function as a media server that will host different types of software for eBooks, audiobooks, and other media (mostly music and some videos). My goal is to make this server accessible over the Internet, rather than just within my home network. I understand that using separate Docker containers for each application is essential, but I'm not very well-versed in the details of how to do this effectively. I'm looking for a solid book recommendation that can help guide me through this process since I have a few questions but expect more to arise.
For starters, if I store all my media files on the same 4TB drive, can all my Docker containers access that drive? Also, do I need to set up a separate subdomain for each container, or can everything be accessed via a single landing page that directs users to the specific container based on their media choice? I know these may seem like basic questions, but any advice would be helpful as I'm trying to learn more about this setup.
1 Answer
These are great questions!
1. Your containers won't automatically have access to your media files unless you create volumes linking to a central media directory for each container.
2. Yes, each container will need a unique port, and you can access them through localhost using the specified port number. If you're considering domains, a proxy manager can help set up subdomains later on. Just take it step by step!
Just a heads-up about ports: the ports inside the containers can be the same (like both using port 80), but you can't have them exposed on the host machine using the same port. So, for example, if container A uses port 80, access it through port 8181 on the host. That's where a reverse proxy can help manage this setup effectively.