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

Evaluate opening vagrant box to local traffic #2076

Closed
crossan007 opened this issue Mar 11, 2017 · 1 comment
Closed

Evaluate opening vagrant box to local traffic #2076

crossan007 opened this issue Mar 11, 2017 · 1 comment

Comments

@crossan007
Copy link
Contributor

This issue is to explore the possibility of altering the core networking functionality of the Vagrant box.

It's necessary to test components of ChurchCRM on actual mobile devices.

It may be beneficial to configure the project's vagrant box to allow for local network communication.

There are two different approaches:

  1. Configure port forwarding so that requests for port 80/443 to the IP of the host machine are forwarded to the guest

    • This will break if other software is already listening on those ports on the development machine
  2. Configure an additional NIC on the vagrant box so that it gets it's own local IP

    • This is probably more reliable, but not everyone's network will support it.

We could add either of these changes to the vagrant file.
We could also comment them out so devs would re required to "opt-in" if they want to use these features.

@crossan007 crossan007 modified the milestone: Backlog Jul 14, 2017
@DawoudIO DawoudIO removed this from the Backlog milestone Nov 1, 2023
@DawoudIO
Copy link
Contributor

DawoudIO commented Nov 1, 2023

No longer using vagrant, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants