There are two ways you can install Winter, either using the Wizard installer or Command-line installation instructions. Before you proceed, you should check that your server meets the minimum system requirements.

Minimum system requirements

Winter CMS has some server requirements for web hosting:

  1. PHP version 7.2 or higher
  2. PDO PHP Extension (and relevant driver for the database you want to connect to)
  3. cURL PHP Extension
  4. OpenSSL PHP Extension
  5. Mbstring PHP Extension
  6. ZipArchive PHP Extension
  7. GD PHP Extension
  8. SimpleXML PHP Extension

Some OS distributions may require you to manually install some of the required PHP extensions.

When using Ubuntu, the following command can be run to install all required extensions:

sudo apt-get update &&
sudo apt-get install php php-ctype php-curl php-xml php-fileinfo php-gd php-json php-mbstring php-mysql php-sqlite3 php-zip

When using the SQL Server database engine, you will need to install the group concatenation user-defined aggregate.

Wizard installation (available soon)

The wizard installation is the recommended way to install Winter for non-technical users. It is simpler than the command-line installation and doesn't require any special skills.

Note: If you are a developer, we recommend that you install via Composer instead

  1. Prepare a directory on your server that is empty. It can be a sub-directory, domain root or a sub-domain.
  2. Download the installer archive file (available soon).
  3. Unpack the installer archive to the prepared directory.
  4. Grant writing permissions on the installation directory and all its subdirectories and files.
  5. Navigate to the install.php script in your web browser.
  6. Follow the installation instructions.


Troubleshooting installation

  1. An error 500 is displayed when downloading the application files: You may need to increase or disable the timeout limit on your webserver. For example, Apache's FastCGI sometimes has the -idle-timeout option set to 30 seconds.

  2. A blank screen is displayed when opening the application: Check the permissions are set correctly on the /storage files and folders, they should be writable for the web server.

  3. An error code "liveConnection" is displayed: The installer will test a connection to the installation server using port 80. Check that your webserver can create outgoing connections on port 80 via PHP. Contact your hosting provider or this is often found in the server firewall settings.

  4. The back-end area displays "Page not found" (404): If the application cannot find the database then a 404 page will be shown for the back-end. Try enabling debug mode to see the underlying error message.

Note: A detailed installation log can be found in the install_files/install.log file.

Command-line installation

If you feel more comfortable with a command-line or want to use composer, there is a CLI install process on the Console interface page.

Post-installation steps

There are some things you may need to set up after the installation is complete.

Delete installation files

If you have used the Wizard installer, for security reasons you should verify the installation files have been deleted. The Winter installer attempts to cleanup after itself, but you should always verify that they have been successfullly removed:

install_files/      <== Installation directory
install.php         <== Installation script

Review configuration

Configuration files are stored in the config directory of the application. While each file contains descriptions for each setting, it is important to review the common configuration options available for your circumstances.

For example, in production environments you may want to enable CSRF protection. While in development environments, you may want to enable bleeding edge updates.

While most configuration is optional, we strongly recommend disabling debug mode for production environments. You may also want to use a public folder for additional security.

Setting up the scheduler

For scheduled tasks to operate correctly, you should add the following Cron entry to your server. Editing the crontab is commonly performed 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 the root directory of Winter. This Cron will call the command scheduler every minute. Then Winter evaluates any scheduled tasks and runs the tasks that are due.

Note: If you are adding this to /etc/cron.d you'll need to specify a user immediately after * * * * *.

Setting up queue workers

You may optionally set up an external queue for processing queued jobs, by default these will be handled asynchronously by the platform. This behavior can be changed by setting the default parameter in the config/queue.php.

If you decide to use the database queue driver, it is a good idea to add a Crontab entry for the command php artisan queue:work --once to process the first available job in the queue.

Keep informed

Sign up to our newsletter to receive updates on Winter CMS releases, new features in the works, and much more.
We'll never spam or give this address away.

Latest blog post

October CMS as you know it is Dead

Published April 12, 2021
We regret to inform you that October CMS as you have known it for the past 7 years is no more. The founders have decided to make it a paid proprietary product; unfortunately abandoning the open source community in the process as "source partially available" is not open source. The core maintainers of the project have forked, and will continue development as Winter CMS....

View this post Read all posts

Latest Winter CMS release


Released April 26, 2021
3 UX/UI Improvements, 19 API Changes, 23 Bug Fixes, 3 Security Improvements, 4 Translation Improvements, 1 Community Improvement, 2 Dependencies

View details View all releases