-
Notifications
You must be signed in to change notification settings - Fork 57
[Documentation:Developer] Updated Installation Instructions #622
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
base: main
Are you sure you want to change the base?
Changes from 4 commits
3bceb8d
c5be546
351ae90
996dcae
5740ccd
52e74d1
412ccff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -155,6 +155,13 @@ with no explanation, then there are a couple of things that may be going wrong: | |
``` | ||
VM_PORT_SITE=1512 vagrant up | ||
``` | ||
* Steps to edit the env file | ||
|
||
1. Go to Submitty install directory and locate the file named "Vagrantfile." | ||
2. Open the "Vagrantfile" in a text editor. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Developers should not manually edit the Vagrantfile. Doing so will make it difficult for git commit tracking. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is indeed true, unless dev puts it in git ignore, it can mess with tracking. On my second thought, I think we should revert this change entirely. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, it's true that it will make tracking a little bit difficult, but they should be aware of how they can create the env file. We can do one thing: add one more line about that to put it in gitignore or not to commit it as a note. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Gitignore is also a tracked file, so you will run into even more issues by editing it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, let me remove it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fyi the major issue isn't them accidentally committing it, that can be easily caught. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, I get it. |
||
 | ||
3. Identify the port causing the error and change it to a port of your choice. | ||
 | ||
|
||
You can alternatively create a `.env` file in the root of your project | ||
with the text `VM_PORT_SITE=1512` (and any other variables separated by | ||
|
Uh oh!
There was an error while loading. Please reload this page.