Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to access Laradock from other VM (Parallels) #1931

Closed
tobysommer opened this issue Jan 2, 2019 · 3 comments
Closed

How to access Laradock from other VM (Parallels) #1931

tobysommer opened this issue Jan 2, 2019 · 3 comments
Labels

Comments

@tobysommer
Copy link

tobysommer commented Jan 2, 2019

Info:

  • Docker version 18.09.0
  • Laradock commit d8c36ab
  • System info Mac
  • System info disto/version: macOS Mojave 10.14.2

Issue:

Hi everyone and happy new year,

and thanks a lot for this great repository! It completely removes the need of Homestead! I use Laradock to serve multiple projects (as described in Installation: B) Setup for Multiple Projects) and it works like a charm!

I wonder, how I can access my sites through another computer on my local network; e.g. I use a Windows VM in Parallels and I need to test the web application in IE/Edge and I don't know how to access them. I tried to use the following entry in C:\Windows\System32\drivers\etc\hosts

10.211.55.2     laravel.test

But this didn't work.

Can you give me any tips how to connect to a Laradock app from my VM?!

Thanks in advance and have a nice day!

@bestlong
Copy link
Member

if laradock host ip is 192.168.1.201
all other computer need set hosts file 192.168.1.201 laravel.test
and laradock host must open firewall port 80

nginx container need a site .conf file server_name laravel.test;

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants