Replies: 1 comment
-
Not sure how Vagrant port mapping works. But the nginx container that CapRover runs uses The reason why this has to be done this way is that otherwise the source IP in nginx logs will be masked behind a private IP: https://serverfault.com/questions/778798/nginx-reverse-proxy-in-docker-container-wrong-ip-logged |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Since dokku doesn't support ARM and caprover does, I needed and got caprover running on my Mac Mini M1 using Vagrant.
This use case is possible and works, and I even installed Wordpress from the dashboard. A pity it is not better documented as I'd imagine it is a common scenario for local development - the existing local install documentation gets me 70% of the way there but I had to figure out quite a few things on my own. Compare this to the dokku project which has a Vagrant project and documentation as first class citizens. Anyway, I can supply my Vagrantfile and installation steps if anyone is interested.
What I don't understand is why I need to have
in my
Vagrantfile
in order for the http://captain.caproverinstance.local name to work. Note I have /etc/hosts192.168.0.219 captain.caproverinstance.local
and set the root domain in caprover tocaproverinstance.local
via the dashboard.If I comment out the vagrant port 80 to 80 mapping, the url fails. The port mapping in the vagrantfile also means my localhost:80 is now taken up by caprover. Trying to get my head around this. Why would port 80, 300 and 443 on localhost be needed to get caprover properly running on my vagrant VM on 192.168.0.219 ?
Beta Was this translation helpful? Give feedback.
All reactions