# Auto-generate the `./docker/docker-compose.yml` config file. bwdata/config.yml: # Full URL for accessing the installation from a browser. bwdata/docker/docker-compose.yml: image: bitwarden/nginx:1.38.4Īnd in. Before I was trying to figure out how to show the Bitwarden container the paths to the certs on the host machine, but the other solution is actually doable. The problem is that I don’t know if I need to do anything else within Bitwarden’s docker container. This means that I should be able to configure Nginx on the host to the SSL certs’ paths when I proxy it back to the docker container. I do not want to use any of Bitwarden’s default SSL support options, since I already have a (better) system implemented. I think I have thought up a solution while typing this draft actually.
So how can I fix these ports’ problems? Another problem I have is with SSL. Yet Bitwarden doesn’t use this to be set up. But the only way I know how to do this is through the docker run -p 8080:80 command for example. I know that Docker supports binding the ports inside the container to a completely different port on the host. This means that it is already bound to ports 443 and 80. I have an Nginx server running on the host Linux machine. I say that this is relatively simple only because my needs mean that I cannot accept Bitwarden’s defaults. I am very new to docker, and lack much of the knowledge necessary to set up a simple installation even on my Linode. However, this is proving more and more difficult. Ideally I’d put Bitwarden on the same machine as my Nextcloud server. Well anyway, I’d also like to set up Bitwarden.
Even though I have full control of the server, it is still someone else’s hardware and I have no real way to tell if there isn’t a backdoor or something. I am reworking my Linode setup so that I can have my Nextcloud data stored on my hardware instead of on my Linode.
0 kommentar(er)
