Using Laravel Valet to Develop a Concrete CMS Site

This is a community-contributed tutorial. This tutorial is over a year old and may not apply to your version of Concrete CMS.
Aug 15, 2016

Laravel Valet is a development environment for Mac developers. It's a fast, low impact alternative to setting up Apache and the hosts file on your machine.

Valet Installation

Install Laravel Valet by following the instructions on that site.

Installation will add a .valet directory to your profile folder.

Concrete CMS Valet Driver Installation

Once Valet installation is complete, you can install the driver.

  1. Download the driver from GitHub.
  2. Copy the driver, ConcreteValetDriver.php, to the Drivers folder under .valet

Concrete CMS Installation

After you have installed Valet and the concrete driver, you're ready to install concrete itself.

  1. Download the lastest version of concrete
  2. Unzip the concrete file
  3. Copy the folder, such as concrete5.7.5.9) and it's contents to the Parked directory you setup in Valet
  4. Access your site by going to the name of the folder appended with '.dev.', such as > concrete5.7.5.9.dev
Recent Tutorials
Customize locale icons
Oct 29, 2024
By myq.

How to customize locale (language region) flags

Concrete CMS Caching Guide
Oct 16, 2024

An overview of types of caching in Concrete and considerations when using them.

Redirect all requests to HTTPS
Oct 9, 2024
By myq.

How to follow best practices for a secure web

Upgrade Concrete versions 9.3.1 and 9.3.2
Sep 10, 2024
By myq.

How to get past a bug in versions 9.3.1 and 9.3.2 that prevents upgrading the Concrete core through the Dashboard

How to use Composer with Marketplace extensions
Aug 22, 2024

Composer can be used to manage third-party extensions from the marketplace

Controlling Google Tag Manager Tags Based on Concrete CMS Edit Toolbar Visibility
Aug 13, 2024

This document provides a step-by-step guide on how to control the firing of Google Tag Manager (GTM) tags based on the visibility of the Concrete CMS edit toolbar. It explains how to create a custom JavaScript variable in GTM to detect whether the edit toolbar is present on a page and how to set up a trigger that ensures GTM tags only fire when the toolbar is not visible. This setup is particularly useful for developers and marketers who want to ensure that tracking and analytics tags are not activated during content editing sessions, thereby preserving the accuracy of data collected.

Improvements?

Let us know by posting here.