Download the PHP package kanopi/saplings-demo-events without Composer

On this page you can find all versions of the php package kanopi/saplings-demo-events. 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?

Informations about the package saplings-demo-events

saplings

Saplings - Events Demo Content Recipe

This recipe provides content the Saplings Events recipe.

How it was created.

We used the Default Content module to export content we created on a local environment. The Default Content module should only be used as a --dev module. It is not needed in production.

Recipe application

Pantheon

terminus drush site.env -- ev "passthru('php core/scripts/drupal recipe path/to/recipe');"

Drush 13+

drush recipe path/to/recipe

PHP script

php core/scripts/drupal recipe path/to/recipe

Instructions on how to use the Default Content module to create a recipe.

Require the module in dev. We don't need it in production.

fin composer require --dev 'drupal/default_content:^2.0@alpha'

Enable the module.

fin drush en -y default_content

Export all nodes and dependencies. dcer gets all the dependencies of the entity you are exporting.

fin drush dcer node --folder=recipes/saplings-content/content

Export all Menu links.

fin drush dcer menu_link_content --folder=recipes/saplings-content/content

Export all taxonomy terms.

fin drush dcer taxonomy_term --folder=recipes/saplings-content/content

You can add an ID or bundle to each if you want to pick and choose.

fin drush dcer menu_link_content 42 --folder=recipes/saplings-content/content

Disable the module when done.

fin drush pmu -y default_content

Notes

This should not be used as a tool for deployments. Use Workspaces for that.

The IDs on the destination site could differ from those on your dev site.

All versions of saplings-demo-events with dependencies

PHP Build Version
Package Version
No informations.
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 kanopi/saplings-demo-events contains the following files

Loading the files please wait ....