Installation

Installation

Server Requirements

You will need to make sure your server meets the following requirements:

  • PHP >= 7.1.3
  • OpenSSL PHP Extension
  • PDO PHP Extension
  • Mbstring PHP Extension
  • Tokenizer PHP Extension
  • XML PHP Extension
  • Ctype PHP Extension
  • JSON PHP Extension

Installing Daalder

Daalder utilizes Composer to manage its dependencies. So, before using Daalder, make sure you have Composer installed on your machine.

Via Daalder Installer

First, download the Daalder installer using Composer:

composer global require daalder/installer

Make sure to place composer's system-wide vendor bin directory in your $PATH so the Daalder executable can be located by your system. This directory exists in different locations based on your operating system; however, some common locations include:

  • macOS: $HOME/.composer/vendor/bin
  • GNU / Linux Distributions: $HOME/.config/composer/vendor/bin

Once installed, the daalder new command will create a fresh Daalder installation in the directory you specify. For instance, daalder new store will create a directory named store containing a fresh Daalder installation with all of Daalder's dependencies already installed:

daalder new store

Configuration

Public Directory

After installing Daalder, you should configure your web server's document / web root to be the public directory. The index.php in this directory serves as the front controller for all HTTP requests entering your application.

Configuration Files

All of the configuration files for Daalder are stored in the config directory. Each option is documented, so feel free to look through the files and get familiar with the options available to you.

Directory Permissions

After installing Daalder, you may need to configure some permissions. Directories within the storage and the bootstrap/cache directories should be writable by your web server or Daalder will not run. If you are using the Homestead virtual machine, these permissions should already be set.

Application Key

The next thing you should do after installing Daalder is set your application key to a random string. If you installed Daalder via Composer or the Daalder installer, this key has already been set for you by the php artisan key:generate command.

Typically, this string should be 32 characters long. The key can be set in the .env environment file. If you have not renamed the .env.example file to .env, you should do that now. If the application key is not set, your user sessions and other encrypted data will not be secure!

Additional Configuration

Daalder needs almost no other configuration out of the box. You are free to get started developing! However, you may wish to review the config/app.php file and its documentation. It contains several options such as timezone and locale that you may wish to change according to your application.

You may also want to configure a few additional components of Daalder, such as:

Web Server Configuration

Pretty URLs

Apache

Daalder includes a public/.htaccess file that is used to provide URLs without the index.php front controller in the path. Before serving Daalder with Apache, be sure to enable the mod_rewrite module so the .htaccess file will be honored by the server.

If the .htaccess file that ships with Daalder does not work with your Apache installation, try this alternative:

Options +FollowSymLinks -Indexes
RewriteEngine On

RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]

Nginx

If you are using Nginx, the following directive in your site configuration will direct all requests to the index.php front controller:

location / {
    try_files $uri $uri/ /index.php?$query_string;
}

Of course, when using Homestead or Valet, pretty URLs will be automatically configured.