Beginner's query - adding seafile to existing database engine?

Seafile Server
1

I’m trying to add seafile as a docker container to a system already running mariadb. Do I need to create a network specifically for seafile (“seafile-net” in the docker-compose file provided with the documentation), or can I use pre-existing networks? My docker-compose file starts with

version: "3"

networks:

proxy: external: true internal: external: false

Should I add “seafile-net” here? Or just use “internal”?

The trouble is that I last fiddled with my docker installation over a year ago, since when personal and professional matters have taken precedence in my tiny brain. So in looking at my docker-compose file I’m confused about what’s going on! Are there other examples of docker-compose files including seafile? Maybe I can find one to use as an example… (I should point out that I am not an IT expert or networking guru, just an ornery academic trying to run a VPS.)

Thanks for allowing me to ramble.

2

You can use existing networks, but I would advise against it.
Ideally, the seafile container and the database container are in the same network (seafile-net), and then you only expose the relevant ports of the seafile container via a reverse proxy.

There already is a docker-compose.yml provided by seafile. I suggest starting from that and adapting it to your needs.