Download the PHP package centarro/commerce-kickstart-project without Composer

On this page you can find all versions of the php package centarro/commerce-kickstart-project. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of centarro/commerce-kickstart-project

Informations about the package commerce-kickstart-project

Centarro Commerce Kickstart 5.x project template

Use Composer to get Drupal + Centarro Commerce Kickstart 4.0.x.

Usage

First you need to install composer.

Note: The instructions below refer to the global composer installation. You might need to replace composer with php composer.phar (or similar) for your setup.

After that you can create the project:

Done! Use composer require ... to download additional modules and themes. For example, if you want to install the certified Centarro modules you'd change into the target directory and require centarro/certified-projects:

The composer create-project command passes ownership of all files to the project that is created. You should create a new git repository, and commit all files not excluded by the .gitignore file.

Demo content

Starting from Commerce Kickstart 5, this project includes the Kickstart Demo recipe by default. The full demo is designed specifically for evaluating Drupal Commerce or Commerce Kickstart and should only be installed on new Kickstart instances. It is not intended for existing Drupal installations. Installing the Kickstart Demo is optional.

If you don't need the demo, you can remove it using the following command:

What does the template do?

Updating Drupal Core

This project will attempt to keep all of your Drupal Core files up-to-date; the project drupal/core-composer-scaffold is used to ensure that your scaffold files are updated every time drupal/core is updated. If you customize any of the "scaffolding" files (commonly .htaccess), you may need to merge conflicts if any of your modified files are updated in a new release of Drupal core.

Follow the steps below to update your core files.

  1. Run composer update drupal/core drupal/core-dev --with-dependencies to update Drupal Core and its dependencies.
  2. Run git diff to determine if any of the scaffolding files have changed. Review the files for any changes and restore any customizations to .htaccess or robots.txt.
  3. Commit everything all together in a single commit, so web will remain in sync with the core when checking out branches or running git bisect.
  4. In the event that there are non-trivial conflicts in step 2, you may wish to perform these steps on a branch, and use git merge to combine the updated core files with your customized files. This facilitates the use of a three-way merge tool such as kdiff3. This setup is not necessary if your changes are simple; keeping all of your modifications at the beginning or end of the file is a good strategy to keep merges easy.

Generate composer.json from existing project

With using the "Composer Generate" drush extension you can now generate a basic composer.json file from an existing project. Note that the generated composer.json might differ from this project's file.

FAQ

Should I commit the contrib modules I download?

Composer recommends no. They provide argumentation against but also workrounds if a project decides to do it anyway.

Should I commit the scaffolding files?

The Drupal Composer Scaffold plugin can download the scaffold files (like index.php, update.php, …) to the web/ directory of your project. If you have not customized those files you could choose to not check them into your version control system (e.g. git). If that is the case for your project it might be convenient to automatically run the drupal-scaffold plugin after every install or update of your project. You can achieve that by registering @composer drupal:scaffold as post-install and post-update command in your composer.json:

How can I apply patches to downloaded modules?

If you need to apply patches (depending on the project being modified, a pull request is often a better solution), you can do so with the composer-patches plugin.

To add a patch to drupal module foobar insert the patches section in the extra section of composer.json:

How can I add js/css libraries using composer.json?

It is possible to install JavaScript libraries with Composer using custom packages as this project does, downloading the packages outside of the docroot and copying over just the necessary files into the Drupal libraries directory. We previously relied on asset-packagist to do this but had to change our approach after the repository went defunct. Refer to this tutorial for more information.

How do I specify a PHP version ?

This project supports PHP 8.3 as minimum version (see Drupal PHP requirements), however it's possible that a composer update will upgrade some package that will then require a newer version.

To prevent this you can add this code to specify the PHP version you want to use in the config section of composer.json:

All versions of commerce-kickstart-project with dependencies

PHP Build Version
Package Version
Requires php Version >=8.3
ext-curl Version *
centarro/certified-projects Version ^1.0
centarro/commerce_kickstart Version ^5.0
composer/installers Version ^2.0
cweagans/composer-patches Version ^1.7
drupal/commerce_kickstart_demo Version ^1
drupal/core-composer-scaffold Version ^11
drupal/core-project-message Version ^11
drupal/core-recommended Version ^11
drush/drush Version ^13
vlucas/phpdotenv Version ^5.1
webflo/drupal-finder Version ^1.2
webmozart/path-util Version ^2.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package centarro/commerce-kickstart-project contains the following files

Loading the files please wait ....