|
1 | | -# fhooe-webdev - A Vagrantfile and Vagrant Box for Web Development Classes |
| 1 | +# fhooe-webdev – A Vagrantfile and Vagrant Box for Web Development Classes |
2 | 2 |
|
3 | 3 | This repository provides a Vagrantfile for a consistent Linux-based web development environment designed for the use in web development classes at the [Upper Austria University of Applied Sciences (FH Oberösterreich), Hagenberg Campus](https://www.fh-ooe.at/en/hagenberg-campus/). |
4 | 4 |
|
5 | | -The Vagrantfile works with our own [fhooe/fhooe-webdev box](https://app.vagrantup.com/fhooe/boxes/fhooe-webdev), which is based on Ubuntu 21.04 and includes Apache2, PHP 8.0, MariaDB 10.6, as well as additional tools and scripts. |
| 5 | +The Vagrantfile works with our own [fhooe/fhooe-webdev box](https://app.vagrantup.com/fhooe/boxes/fhooe-webdev), which is based on Ubuntu 21.10 and includes Apache2, PHP 8.1, MariaDB 10.7, as well as additional tools and scripts. |
6 | 6 |
|
7 | 7 | Not familiar with Vagrant or not sure, why to use it? Have a look at the [Introduction](https://www.vagrantup.com/intro/) first. |
8 | 8 |
|
@@ -35,16 +35,21 @@ Then install the required software in the following order: |
35 | 35 |
|
36 | 36 | Once the image has successfully booted you will notice that a folder called `code` inside of your `<path-to>/fhooe-webdev` directory has been created. This directory is mapped to `/var/www/html/code` in the image via Vagrant's shared folder functionality. Since it points to Apache's document root, files are immediately served through the web server. |
37 | 37 |
|
38 | | -Additionally, the Vagrantfile configures the IP address `192.168.7.7` as a private network, so you can access the machine - and therefore its web server - under this address. |
| 38 | +Additionally, the Vagrantfile configures the IP address `172.16.7.7` as a private network, so you can access the machine - and therefore its web server - under this address. |
39 | 39 |
|
40 | | -To develop and deploy your web applications, copy them to the `code` folder on your host machine. They will be instantly available through the Vagrant image's web server at 192.168.7.7. E.g.: |
| 40 | +To develop and deploy your web applications, copy them to the `code` folder on your host machine. They will be instantly available through the Vagrant image's web server at 172.16.7.7. E.g.: |
41 | 41 |
|
42 | | -- `code/my_example_project/index.php` -> <https://192.168.7.7/code/my_example_project/index.php> |
| 42 | +- `code/my_example_project/index.php` -> <https://172.16.7.7/code/my_example_project/index.php> |
43 | 43 |
|
44 | 44 | There's a file called `phpinfo.php` in the `code` directory that allows you to quickly check the configuration of this image. Also [phpMyAdmin](https://www.phpmyadmin.net/) is already installed and configured. These are available here: |
45 | 45 |
|
46 | | -- <https://192.168.7.7/code/phpinfo.php> |
47 | | -- <https://192.168.7.7/phpmyadmin> |
| 46 | +- <https://172.16.7.7/code/phpinfo.php> |
| 47 | +- <https://172.167.7.7/phpmyadmin> |
| 48 | + |
| 49 | +The default configuration uses HTTPS and mimics a production webserver without displaying any PHP errors. To work without HTTPS (thus avoiding the certificate warning), open your files with HTTP on port 81. E.g.: |
| 50 | + |
| 51 | +- http://172.16.7.7:81/ for the dashboard or |
| 52 | +- http://172.16.7.7:81/code/ for the code directory. |
48 | 53 |
|
49 | 54 | Since all the files of your web projects are on your host computer, you can destroy, remove or reset the Vagrant image at any time. Nothing within the `code` directory is affected. |
50 | 55 |
|
|
0 commit comments