To be clear - I say "forget the ports", which sounds like it entirely contradicts the rest of my "read the docs and understand what these things do" advice.
What I mean to say is forget thinking in terms of running a development server, using a custom port etc - with the vagrant setup, you're working as though you're deploying to a production server, using the same workflow. On Tue, Mar 4, 2014 at 5:40 PM, Stephen McDonald <[email protected]> wrote: > You shouldn't need to do any of that. Here's my vagrantfile: > > Vagrant.configure("2") do |config| > config.vm.box = "precise64" > config.vm.network :private_network, ip: "10.10.10.10" > end > > Forget the ports. Your vagrant vm is synonymous with a production server - > you're deploying to it, and the various layers of nginx and gunicorn should > deal with it. SSH onto this server. Look at the config files deployed > there. Read each of the corresponding project's own documentation on these > config files, and what they mean. > > > > > On Tue, Mar 4, 2014 at 5:30 PM, Jesse Carrigan <[email protected] > > wrote: > >> I tried forwarding a port from my host machine and got the same result. >> With localhost:8080 forwarded to 80 on the guest machine, I get the message >> from ngnix. Forwarding localhost:8080 to 8000, I get no response. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Stephen McDonald > http://jupo.org > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
