Rock64 as multiple server

[Sputnik]

Hello -

I want to set up a Rock64 mini server with NextcloudPi and an extra web server for myself.
In front of both could be a a NGinX as a proxy server so that the subdomains can be reached without port information. My idea is to use Docker and set up NGinX, NextcloudPi and the web server in different containers. Does the setup make sense?Or how can it be better configured?
I don't know Linux very well yet. Are there any instructions or hints for this?
I want to learn and constantly improve the system but not run into a dead end...

Any help would be appreciated!

[Trash_Can_Man]

Hello -

I want to set up a Rock64 mini server with NextcloudPi and an extra web server for myself.
In front of both could be a a NGinX as a proxy server so that the subdomains can be reached without port information. My idea is to use Docker and set up NGinX, NextcloudPi and the web server in different containers. Does the setup make sense?Or how can it be better configured?
I don't know Linux very well yet. Are there any instructions or hints for this?
I want to learn and constantly improve the system but not run into a dead end...

Any help would be appreciated!

Im using a rock64 4gb with OMV and a dozen dockers over it, in your case you can use this instead of nextcloudpi since im guessing that if its made for the pi its made for armhf, any docker you use on the rock64 you want to use em with either arm64 or aarch64 for best performance, you can add any web server docker after that, im personally using a wordpress docker for extra simplicity, omv includes between their own plugins a docker plugin and they plan to maintain it for the time being since its a widelly used feature, i cant think of an easier OS to start using containers on the rock64 for a newbie...a few tips to keep in mind, docker is very VERY annoying to allow any given docker to communicate with the host OS BUT the communicatiuon between dockers is very easy so if you take this path try to install EVERYTHING you plan to use on containers, not on the host OS, there are TONS of aarch64 containers everywhere to try and use...

A workaround for the mentioned limitation is to let the containers use the host network cards directly, its a bit risky because you ""break"" the containerization in regards to networking, possibly opening unneded ports or causing network problems on the host...

And about the subdomains you can look up for macvlan networking on docker, basically it gives any given docker an ip on your network and then you can set up on your router a static adress with a name wich in fact makes that name resolve by dns, after that you only need to change the port on your service if it uses anything other than port 80 (or use docker to redirect said internal port to 80 external)

I gave you a lot of ideas, go my little grasshopper and practice that google-fu

[Sputnik]

Thank you very much for these valuable hints. These are a good starting point for me and give me some confidence with my first steps on this terrain.