Download the PHP package zizther/craftcms-ddev without Composer
On this page you can find all versions of the php package zizther/craftcms-ddev. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package craftcms-ddev
A Craft CMS starter project using DDEV for local hosting and Vite for front-end bundling and HMR.
Going from zero to Vite HMR on a fresh Craft install, with only 4 CLI commands:
composer create-project...
make init
make setup
make dev
Notable Features:
- DDEV for local development
- Vite 2.x for front-end bundling & HMR
- Tailwind 3.x for utility-first CSS
- Alpine 3.x for lightweight reactivity
- Makefile for common CLI commands
Local machine prerequisites:
Getting Started
Option 1: With Composer (recommended)
If you have Composer installed on your local machine,
you can use create-project
to pull the latest tagged release.
Open terminal prompt, and run:
Make sure that PATH
is a new or existing and empty folder.
Option 2: With Git CLI
Alternatively you can clone the repo via the Git CLI. degit is the easiest way:
Make sure that PATH
is a new or existing and empty folder.
Last, clean up and set some default files for use:
If you are using git clone
You'll want to discard the existing /.git
directory. In the terminal, run:
Option 3: Manual Download
Download a copy of the repo to your local machine and move to where you want to your project to run. Similar to above, you'll then want to clean up and set some default files for use. In the terminal, run:
Configuring DDEV
Note: This section is optional. If you are simply test-driving this project, feel free to skip to the next section. ⚡
To configure your project to operate on a domain other than https://craftcms.test
, run:
Follow the prompts.
- Project name: e.g.
mysite
would result in a project URL ofhttps://mysite.test
(make note of this for later in the installation process) - Docroot location: defaults to
web
, keep as-is - Project Type: defaults to
php
, keep as-is
Installing Craft
To install a clean version of Craft, run:
Follow the prompts.
This command will:
- Set the project name and domain
- Copy your local SSH keys into the container (handy if you are setting up craft-scripts)
- Start your DDEV project
- Install Composer
- Install npm
- Do a one-time build of Vite
- Generate
CRAFT_APP_ID
and save to your.env
file - Generate
CRAFT_SECURITY_KEY
and save to your.env
file - Installing Craft for the first time, allowing you to set the admin's account credentials
- Install some of the Craft plugins
Once the process is complete, type ddev launch
to open the project in your default browser. 🚀
Local development with Vite
To begin development with Vite's dev server & HMR, run:
This command will:
- Copy your local SSH keys into the container (handy if you are setting up craft-scripts)
- Start your DDEV project
- Install Composer
- Install npm
- Do a one-time build of Vite
- Spin up the Vite dev server
Open up a browser to your project domain to verify that Vite is connected. Begin crafting beautiful things. ❤️
Makefile
A Makefile has been included to provide a unified CLI for common development commands.
make install
- Runs a complete one-time process to set the project up and install Craft.make up
- Starts the DDEV project, ensuring that SSH keys have been added, and npm & Composer have been installed.make dev
- Runs a one-time build of all front-end assets, then starts Vite's server for HMR.make build
- Builds all front-end assets.make composer xxx
- Run Composer commands inside the container, e.g.make composer install
make craft xxx
- Run Craft commands inside the container, e.g.make craft project-config/touch
make npm xxx
- Run npm commands inside the container, e.g.make npm install
make clean
- Removes thecomposer.lock
,package-lock.json
and the entirenode_modules
&vendor
directorymake nuke
- Restarts the project from scratch by runningmake clean
(above), then reinstalls composer and node packagesmake pull
- Pull remote db & assets (requires setting up craft-scripts
Tip: If you try a command like make craft project-config/apply --force
you’ll see an error, because the shell thinks the --force
flag should be applied to the make
command. To side-step this, use the --
(double-dash) to disable further option processing, like this: make -- craft project-config/apply --force
Craft CMS Plugins
- AWS S3
- CKEditor
- CP Clear Cache
- CP Field Inspect
- Craft Autocomplete
- Hyper
- Navigation
- Neo
- Quick Field
- Ray
- Retour
- SEOmatic
- Vite
Javascript Libraries
Kudos
Thanks to Andrew (nystudio107) and johndwells for the inspiration