Added volume mounting to docs

.gitignore

@@ -1 +1,3 @@
-.DS_Store
+.DS_Store
+.vs
+.vscode

BASIC/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/basic_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it basic_dev bash
+dgisolfi/docker run -it basic_dev bash
 ```
 
 *Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/BASIC/files" with the path to your files and "PRJ_Name" with the folder name*
 
 ```bash
-docker run -it basic_dev -v/Path/to/BASIC/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/BASIC/files:/DEV/BasicFiles dgisolfi/basic_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "BasicFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +40,6 @@ To run your own programs alter the command to use the following format:
 
 `fbc file_name.bas`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

COBOL/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/cobol_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it cobol_dev bash
+dgisolfi/docker run -it cobol_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/COBOL/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/COBOL/files" with the path to your files*
 
 ```bash
-docker run -it cobol_dev -v/Path/to/COBOL/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/COBOL/files:/DEV/COBOLFiles dgisolfi/basic_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "COBOLFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +40,6 @@ To run your own programs alter the command to use the following format:
 
 `cobc -o program_name file_name.cob`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

Erlang/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/erlang_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it erlang_dev bash
+dgisolfi/docker run -it erlang_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Erlang/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Erlang/files" with the path to your files.*
 
 ```bash
-docker run -it erlang_dev -v/Path/to/Erlang/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/Erlang/files:/DEV/ErlangFiles dgisolfi/erlang_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "ErlangFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +40,6 @@ To run your own programs alter the command to use the following format:
 
 `erlc file_name.erl`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

Fortran/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/fortran_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it fortran_dev bash
+docker run -it dgisolfi/fortran_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Fortran/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Fortran/files" with the path to your files*
 
 ```bash
-docker run -it fortran_dev -v/Path/to/Fortran/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/Fortran/files:/DEV/FortranFiles dgisolfi/fortran_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "FortranFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +40,6 @@ To run your own programs alter the command to use the following format:
 
 `gfortran -o program_name file_name.f90`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

Haskell/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/haskell_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it haskell_dev bash
+docker run -it dgisolfi/haskell_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Haskell/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to develop your own code, run the following command instead and replace "/Path/to/Haskell/files" with the path to your files*
 
 ```bash
-docker run -it haskell_dev -v/Path/to/Haskell/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/Haskell/files:/DEV/HaskellFiles dgisolfi/haskell_dev bash 
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "HaskellFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +40,6 @@ To run your own programs alter the command to use the following format:
 
 `ghc -o program_name file_name.hs`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

LISP/README.md

@@ -15,16 +15,17 @@ docker pull dgisolfi/lisp_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it --security-opt seccomp=unconfined lisp_dev bash
+docker run -it --security-opt seccomp=unconfined dgisolfi/lisp_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/LISP/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/LISP/files" with the path to your files*
 
 ```bash
-docker run -it --security-opt seccomp=unconfined lisp_dev -v/Path/to/LISP/files:/DEV/PRJ_Name bash
+# The security setting is to avoid a warning when runnin in Docker
+docker run -it -v/Path/to/LISP/files:/DEV/LISPFiles --security-opt seccomp=unconfined dgisolfi/lisp_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "LISPFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +41,6 @@ To run your own programs alter the command to use the following format:
 
 `sbcl --script file_name.lisp`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

ML/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/ml_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it ml_dev bash
+docker run -it dgisolfi/ml_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/ML/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/ML/files" with the path to your files*
 
 ```bash
-docker run -it ml_dev -v/Path/to/ML/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/ML/files:/DEV/MLFiles dgisolfi/ml_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "MLFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,4 +40,6 @@ To run your own programs alter the command to use the following format:
 
 `sml file_name.sml`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited**
+
 With your programs written and mounted you may now use the compiler to test and run them.

Pascal/README.md

@@ -15,16 +15,16 @@ docker pull dgisolfi/pascal_dev
 Next to run an instance of the image as a container run the following:
 
 ```bash
-docker run -it pascal_dev bash
+docker run -it dgisolfi/pascal_dev bash
 ```
 
-*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Pascal/files" with the path to your files and "PRJ_Name" with the folder name*
+*Note: If you would like to mount a directory in order to test run the following command instead and replace "/Path/to/Pascal/files" with the path to your files*
 
 ```bash
-docker run -it pascal_dev -v/Path/to/Pascal/files:/DEV/PRJ_Name bash
+docker run -it -v/Path/to/Pascal/files:/DEV/PascalFiles dgisolfi/pascal_dev bash
 ```
 
-The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the appropriate directory of your mounted files. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
+The result should be command line access as the root user to the now running Docker container. You should be located in the DEV directory within the container. If you chose to Volume mount any files first run `ls` which will list all directories and files, then `cd` into the directory "PascalFiles", anything changed within the mounted directory will be reflected accross both host and container. Due to how volumes work in Docker you have the advantage of the files being shared between the container and your host machine, meaning you may now open the directory up in an IDE and begin to program, any changes in the directory on your host will be reflected in the container.
 
 ## Compiling
 
@@ -40,6 +40,8 @@ To run your own programs alter the command to use the following format:
 
 `fpc file_name.bas`
 
+**Note: data inside a Docker container is nonpersistent. Only files that exist inside a volume mounted directory will remain after the container is exited** 
+
 With your programs written and mounted you may now use the compiler to test and run them.
 
 ## IDE