Download the PHP package palantirnet/drupal-skeleton without Composer

On this page you can find all versions of the php package palantirnet/drupal-skeleton. 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 drupal-skeleton

Drupal Skeleton

This is a template for starting Drupal projects using the composer create-project command.

Quick start

This "quick start" section will show you how to set up a local server accessible at http://example.local with Drupal ready to install.

Preface

You should have the development dependencies installed on your Mac before you begin. These dependencies are not project-specific, and you may have some or all of them already installed. If you don't, find a location with good internet and set aside at least an hour to complete this step.

The development dependencies are:

On Macs, Docker and ddev can be installed with homebrew:

Once you have your dependencies installed, setting up this skeleton will take at least another hour, depending on your internet connection.

Some of the commands below will prompt you for a response, with the default answer in brackets. For this quick start, hit return to accept each default answer:

Steps

  1. Create a new Drupal project called "example" based on this template:

  2. Go into your new project directory and update the ddev configuration in .ddev/config.yml:

  3. From inside the ddev environment, run the script from palantirnet/the-build to set up the default Drupal variables and install Drupal:

  4. In your web browser, visit http://example.ddev.site

  5. Optional: While you are logged into the ddev environment, you can run Drush commands like drush status.

Extra Credit

Note: Make sure your project directory is in the right place / named correctly, because renaming or moving the project directory (e.g. example/) after starting can break your ddev setup.

Full Project Setup

Create a project with a custom name

Use composer to create a new project based on this skeleton, replacing PROJECTNAME with the short name for your project:

Update your documentation

Update the README:

Project-specific documentation at docs/technical_approach.md

Update the LICENSE.txt:

Update the composer.json:

Update the package.json:

Configure your ddev development environment

Go into your new project directory and update the ddev configuration in .ddev/config.yml.

Run the installers

From inside ddev, run the script from palantirnet/the-build to set up a base Drupal installation:

Commit your work to git

Initialize a git repository and commit your work to the develop branch:

Create an empty repository on GitHub for your work. Then, push your work up to the repository:

Manage your ddev environment

Replace "the-build" with [something else]

If you're allergic to phing and Benadryl isn't helping, you can also remove the-build:

  1. composer remove --dev palantirnet/the-build
  2. rm -r .the-build
  3. rm build.xml
  4. This will remove drush, coder, and phpmd -- if you want those dependencies, you'll need to add them back to your project:

  5. Install your build tooling of choice... or nothing at all...
  6. Update your project's README

See also: Documentation on using the-build

Install Drupal from the command line

When using drush or phing to manage your Drupal site, you will need to log into the ddev environment (ddev ssh).

If you've run vendor/bin/the-build-installer from within ddev, Drupal will be installed and the initial config exported to config/sites/default/.

You can use the phing scripts provided by palantirnet/the-build to reinstall the site from config at any time:

Or, you can use drush directly:

Manage your configuration in code

In Drupal development, all (or most) Drupal configuration should be exported and treated as part of the codebase. We use Drupal's "install from config" installer option to allow us to use the exported configuration as the basis for a repeatable, automation-friendly build and install process. We also use config_split to manage environment-specific configuration.

  1. Log into Drupal in your browser and do some basic config customizations:
    • Set the site timezone
    • Disable per-user timezones
    • Disable user account creation
    • Remove unnecessary content types
    • Set the admin email address (your development environment will trap all emails)
    • Turn the Cron interval down to "never"
    • Uninstall unnecessary modules (e.g. Search, History, Comment)
  2. Export your config:

  3. You should have a ton of new *.yml files in config/sites/default/. Add them, and this config change, to git:

  4. Reinstall your site and verify that your config is ready to go:

More information


Copyright 2016 - 2025 Palantir.net, Inc.


All versions of drupal-skeleton with dependencies

PHP Build Version
Package Version
Requires composer/installers Version ^1.9
drupal/admin_toolbar Version ^3.0
drupal/config_split Version ^1.7
drupal/core-composer-scaffold Version ^9
drupal/core-recommended Version ^9
drupal/devel Version >=4.1
drupal/workbench Version ^1.3
drupal/workbench_tabs Version ^1.5
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 palantirnet/drupal-skeleton contains the following files

Loading the files please wait ....