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

Remove "api.vagrant" host requirement from vagrant setup #20

Closed
GUI opened this issue Feb 3, 2014 · 1 comment
Closed

Remove "api.vagrant" host requirement from vagrant setup #20

GUI opened this issue Feb 3, 2014 · 1 comment
Labels

Comments

@GUI
Copy link
Member

GUI commented Feb 3, 2014

When setting up a vagrant box for local development, we currently assume the host machine can resolve the api.vagrant hostname. This requires explicitly adding that hostname to your computer's /etc/hosts file. Right now this is needed for the HTTPS redirects when accessing the admin, but it would be best to remove this hostname requirement, so editing your global hosts file is not necessary for local development.

@GUI
Copy link
Member Author

GUI commented Oct 27, 2014

As part of the new installation packages, it listens to all hostnames by default. You can explicitly override it to only listen for specific hostnames, but out of the box, it will listen for everything, which should simplify initial setup.

@GUI GUI closed this as completed Oct 27, 2014
GUI added a commit that referenced this issue Sep 27, 2015
Fix multiple logs.json requests being made on analytics form chagnes
GUI added a commit that referenced this issue Sep 27, 2015
Move rate_limit_bucket_name into an API setting
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

1 participant