You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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.
The text was updated successfully, but these errors were encountered:
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:
Configure port forwarding so that requests for port 80/443 to the IP of the host machine are forwarded to the guest
Configure an additional NIC on the vagrant box so that it gets it's own local IP
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.
The text was updated successfully, but these errors were encountered: