Skip to content
Snippets Groups Projects
Commit 63406640 authored by keleher's avatar keleher
Browse files

auto

parent 6755ea59
No related branches found
No related tags found
No related merge requests found
......@@ -17,7 +17,7 @@ collaboration for your class project, or for other classes.
#### Cloning the Class Repository
We will be using the department `gitlab` for downloading project materials,
and Elms for uploading. Clone `Project1` by installing `git`, and then:
and Elms for uploading. Clone `Project0` by installing `git`, and then:
`git clone https://gitlab.cs.umd.edu/keleher/424f19`
......@@ -29,9 +29,9 @@ and Elms for uploading. Clone `Project1` by installing `git`, and then:
- In order to use this option, you have to first install Vagrant and VirtualBox on your machine (called `Host` henceforth). See the instructions on the two websites above to do that.
- Vagrant makes things **super-easy**. We will provide you with appropriate setup files -- all you need to do is `vagrant up` to start the virtual machine.
- More specifically: in the git sub-directory `project1`, run `vagrant up`. This will start the virtual machine in the background. You may be prompted to run `vagrant box update`. Do so.
- More specifically: in the git sub-directory `project0`, run `vagrant up`. This will start the virtual machine in the background. You may be prompted to run `vagrant box update`. Do so.
- By default, vagrant only provides **ssh** access into the virtual machine (called `Guest VM` henceforth), using `vagrant ssh`. This will work as if you are doing `ssh` into a remote machine.
- The Guest VM will have access to the files in the current directory *on the host machine* (i.e., the files in the `project1` directory and its subdirectories). These are mounted in the guest VM at `/vagrant`. It would be best if you only make edits to that directory -- since those edits will survive a `vagrant destroy`. In fact, you can continue using your favorite text editor (in the host machine) to edit files, and only use the VM for running specific programs (like `postgres`, `psql`, or `ipython notebook` below).
- The Guest VM will have access to the files in the current directory *on the host machine* (i.e., the files in the `project0` directory and its subdirectories). These are mounted in the guest VM at `/vagrant`. It would be best if you only make edits to that directory -- since those edits will survive a `vagrant destroy`. In fact, you can continue using your favorite text editor (in the host machine) to edit files, and only use the VM for running specific programs (like `postgres`, `psql`, or `ipython notebook` below).
- If the Guest VM has a program (e.g., a Web Server) running and listening on a specific port (e.g., 80), you can access those ports from the host machine by adding them to the `VagrantFile`. The provided VagrantFile has two such mappings: for port 8888, used by iPython (mapped to port 8888 on the host machine), and for port 80, used by a Web server (mapped to port 8080 on the host machine).
- If you just exit the `ssh` the VM continues running in the background.
- Some other vagrant commands that you would need to be familiar with:
......@@ -117,7 +117,7 @@ IPython is an enhanced command shell for Python, that offers enhanced introspect
```
This will start a server on the VM, listening on port 8888. We will access it from the **host** (as discussed above, the VagrantFile maps the 8888 port on the guest VM to the 8888 port on the host VM). To do that, simply start the browser, and point it to: http://127.0.0.1:8888
* You should see the Notebooks in the `project1/` directory. Click to open the "IPython Getting Started" Notebook, and follow the instruction therein.
* You should see the Notebooks in the `project0/` directory. Click to open the "IPython Getting Started" Notebook, and follow the instruction therein.
* The second Notebook ("Basics of SQL") covers basics of SQL, by connecting to your local PostgreSQL instance. The Notebook also serves as an alternative mechanism to run queries. However, in order to use that, you must set up a password in `psql` using `\password` (set the password to be `ubuntu`).
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment