-
Notifications
You must be signed in to change notification settings - Fork 31
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
should have FAQ page #207
Comments
hoavt [2:30 PM] hoatle [2:36 PM] hoavt [2:36 PM]
hoavt [2:50 PM] [2:51] hoatle [3:06 PM] [3:06] [3:07] hoavt [3:09 PM] hoatle [3:11 PM] hoavt [3:12 PM]
hoatle [3:14 PM] [3:16] [3:17] hoavt [3:17 PM] hoatle [3:18 PM] [3:18]
|
Q: What should I do after updating |
when
Then stop it, |
|
when vagrant ssh got stuck at "settings networks", then try this: #262 |
many people has the problem that /etc/hosts are not properly updated when they got errors, after $ vagrant destroy and $ vagrant up. They end up having multiple same entry that the wrong one is one the top of the file. This leads to wrong dns to point to the right VM IP. What can we do?
|
|
should answer the question: "Why teracy-dev? Why not just Docker?"
|
How do I know which version of teracy-dev that I'm using? |
verified, close |
to answer FAQ
The text was updated successfully, but these errors were encountered: