This example will use
laravel to install Laravel from within the Devilbox PHP container.
After completing the below listed steps, you will have a working Laravel setup ready to be served via http and https.
Table of Contents
The following configuration will be used:
|Project name||VirtualHost directory||Database||TLD_SUFFIX||Project URL|
- Inside the Devilbox PHP container, projects are always in
- On your host operating system, projects are by default in
./data/www/inside the Devilbox git directory. This path can be changed via HOST_PATH_HTTPD_DATADIR.
It will be ready in six simple steps:
- Enter the PHP container
- Create a new VirtualHost directory
- Install Laravel
- Symlink webroot directory
- Setup DNS record
- Visit http://my-laravel.loc in your browser
All work will be done inside the PHP container as it provides you with all required command line tools.
Navigate to the Devilbox git directory and execute
shell.bat on Windows) to
enter the running PHP container.
The vhost directory defines the name under which your project will be available.
<vhost dir>.TLD_SUFFIX will be the final URL ).
email@example.com in /shared/httpd $ mkdir my-laravel
Navigate into your newly created vhost directory and install Laravel with
firstname.lastname@example.org in /shared/httpd $ cd my-laravel email@example.com in /shared/httpd/my-laravel $ laravel new laravel-project
How does the directory structure look after installation:
firstname.lastname@example.org in /shared/httpd/my-laravel $ tree -L 1 . └── laravel-project 1 directory, 0 files
If you have Auto DNS configured already, you can skip this section, because DNS entries will be available automatically by the bundled DNS server.
If you don’t have Auto DNS configured, you will need to add the following line to your
host operating systems
/etc/hosts file (or
C:\Windows\System32\drivers\etc on Windows):
This will ensure that your host operating system’s browser will direct any calls on
https://my-laravel.loc to the Devilbox which is listening on
Once everything is installed and setup correctly, you might be interested in a few follow-up topics.
The Devilbox ships most common Web UIs accessible from the intranet.
Go ahead and make the Devilbox more smoothly by setting up its core features.
In case your framework/CMS requires it, attach caching, queues, database or performance tools.