Installation

Before you proceed with installing TastyIgniter, you should check that your server meets the minimum system requirements.

Minimum Requirements

These are the requirements for your web hosting to run TastyIgniter:

  • PHP (at least 7.2)
  • PDO PHP Extension
  • cURL PHP Extension
  • OpenSSL PHP Extension
  • GD PHP Extension
  • Mcrypt PHP Extension
  • Mbstrings PHP Extension

Install TastyIgniter

There are two ways you can install TastyIgniter, either using the Quick or Command-line installation instructions.

Quick Installation

  1. Download and unzip the TastyIgniter setup wizard into an empty directory on your server.
  2. Create a MySQL user database for TastyIgniter on your database server.
  3. Upload the TastyIgniter folders and files to your server. Normally the setup.php file will be at the web root directory.
  4. Grant write permissions on the setup directory, its subdirectories and files.
  5. Run the TastyIgniter setup script by accessing setup.php in your web browser. Example, http://example.com/setup.php or http://example.com/folder/setup.php
  6. Follow all onscreen instructions and make sure all installation requirements are checked.

Command-line installation

TastyIgniter also uses composer to manage its dependencies, you’ll need to have composer installed on your machine before using the TastyIgniter command-line installation. Run this command in an empty location that you want TastyIgniter to be installed in:

composer create-project tastyigniter/tastyigniter . --stability=beta

After running the above command, run the install command and follow the instructions to complete installation

php artisan igniter:install

The install command will guide you through the process of setting up TastyIgniter for the first time. It will ask for the database configuration, application URL and administrator details.

Post-installation steps

For security reasons, if you used the Quick Installation Setup Wizard, you should delete the setup files. TastyIgniter will never automatically delete files from your system, so these files and directories should be deleted manually:

setup/      		<== Setup directory
setup.php       <== Setup script

Setting up the task scheduler

You should add the following Cron entry to your server for scheduled tasks to function properly. Crontab editing is usually done with the command crontab -e.

* * * * * php /path/to/artisan schedule:run >> /dev/null 2>&1

Be sure to replace /path/to/artisan with the absolute path to the artisan file in your TastyIgniter root directory . This Cron will call the command scheduler every minute. When executing the schedule:run command, TastyIgniter will assess your scheduled tasks and run the tasks that are due.

Task Scheduling is how scheduling time-based tasks are managed in TastyIgniter. Several core features of TastyIgniter, such as checking for updates, use the scheduler.

Setting up queue workers

Optionally, you can set up an external queue to process queued jobs, which will be handled by the platform asynchronously by default. By setting the default parameter in the config/queue.php, this behaviour can be altered.

Web server configuration

TastyIgniter has basic configuration that should be applied to your webserver. Common webservers and their configuration can be found below.

Apache configuration

There are some extra system requirements if your webserver is running Apache, mod_rewrite should be installed and enabled and the AllowOverride option should be switched on.

TastyIgniter includes a .htaccess file – make sure it’s been uploaded correctly.

You will need to uncomment this line in the .htaccess file in some cases:

## !IMPORTANT! You may need to uncomment the following line for some hosting environments,
## If your installation resides in a subdirectory, enter the name here also
##
# RewriteBase /

If you’ve created a subdirectory, you can add the subdirectory name as well:

RewriteBase /mysubdirectory/

Nginx configuration

Add the following lines to your server’s configuration block:

/etc/nginx/sites-available/default

Use the following code in server section. If you have installed TastyIgniter into a subdirectory, replace the first / in location directives with the directory TastyIgniter was installed under:

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

# Pass the PHP scripts to FastCGI server
location ~ ^/index.php {
    # Write your FPM configuration here

}

# Whitelist
## Let TastyIgniter handle if static file does not exists
location ~ ^/favicon\.ico { try_files $uri /index.php; }
location ~ ^/sitemap\.xml { try_files $uri /index.php; }
location ~ ^/robots\.txt { try_files $uri /index.php; }
location ~ ^/humans\.txt { try_files $uri /index.php; }

## Let nginx return 404 if static file does not exists
location ~ ^/assets/media { try_files $uri 404; }
location ~ ^/storage/temp/public { try_files $uri 404; }

location ~ ^/app/.*/assets { try_files $uri 404; }
location ~ ^/app/.*/actions/.*/assets { try_files $uri 404; }
location ~ ^/app/.*/dashboardwidgets/.*/assets { try_files $uri 404; }
location ~ ^/app/.*/formwidgets/.*/assets { try_files $uri 404; }
location ~ ^/app/.*/widgets/.*/assets { try_files $uri 404; }

location ~ ^/extensions/.*/.*/assets { try_files $uri 404; }
location ~ ^/extensions/.*/.*/actions/.*/assets { try_files $uri 404; }
location ~ ^/extensions/.*/.*/dashboardwidgets/.*/assets { try_files $uri 404; }
location ~ ^/extensions/.*/.*/formwidgets/.*/assets { try_files $uri 404; }
location ~ ^/extensions/.*/.*/widgets/.*/assets { try_files $uri 404; }

location ~ ^/themes/.*/assets { try_files $uri 404; }

Application configuration

Debug mode

The debug setting is found in the config/app.php configuration file with the debug parameter, and is enabled by default.

When enabled, this setting will display detailed error messages when they occur along with other debugging functions. Debug mode should always be disabled in a live production site. This prevents the display of potentially sensitive information to the end user.

CSRF protection

TastyIgniter offers an simple method to protect your application from cross-site request forgeries.

For every active user session managed by the application, TastyIgniter automatically generates a CSRF “token.” This token is used to check that the authenticated user is the one who actually makes the client requests.

Although CSRF security is enabled by default, you can disable it in the config/system.php configuration file using the enableCsrfProtection parameter.

Bleeding edge updates

TastyIgniter core and some marketplace extensions will introduce changes in two stages to ensure overall stability and integrity of the codebase. This means that besides the regular stable versions, they do have a test version.

By modifying the edgeUpdates parameter in the config/system.php configuration file you can instruct the application to choose test versions from the marketplace.

/*
|--------------------------------------------------------------------------
| Bleeding edge updates
|--------------------------------------------------------------------------
|
| If you are developing with TastyIgniter, it is important to have the latest
| code base, set this value to 'true' to tell the platform to download
| and use the development copies of core files and extensions.
|
*/

'edgeUpdates' => false,

When you are using Composer to handle updates, then replace the default TastyIgniter requirements in your composer.json file with the following to receive updates from the develop branch directly.

"tastyigniter/flame": "dev-develop as 1.0",
"laravel/framework": "5.8.*@dev",

Getting Started

You can access the administrator panel from /admin with your username and password asked during the setup process. After you’ve logged in you’ll be able to access the administration panel to configure your site.

Follow the getting started steps on the administration panel dashboard.

Getting help

Troubleshooting

  1. A 404 error page is displayed: This could be a result of the mod_rewrite module not being activated/installed or configured properly. Activate mod_rewrite for the Apache web-server. If it is already activated, check the root htaccess file in /.htaccess, to make sure the RewriteBase value is configured properly.
  2. A blank screen is displayed when opening the application: Check the file permissions are set correctly on the files and folders to 777.
  3. Setup successful but storefront links are not working: Check that the theme’s required extensions are all installed.

See a mistake? Edit this page