Download the PHP package palantirnet/the-vagrant without Composer

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

"The" Vagrant

Add a customizable vagrant environment into a Drupal project. This may be used in conjunction with the drupal-skeleton and the-build, or it may be used to retrofit an existing project with a VM-based development environment.

Note: If you are setting up a new project, you likely want to start with drupal-skeleton.

Why the-vagrant?

Dependencies

Installation

To use the-vagrant on a project, you will need to:

  1. Use composer to add the package to your project:

  2. Run the-vagrant's install script to add and configure the Vagrantfile:

    • This will prompt you for project-specific configuration:
    • The project hostname
    • The project web root
    • Enable Solr
    • Enable HTTPS
    • Add a project-specific Ansible playbook to be run in addition to the default playbook
  3. Check in and commit the new Vagrantfile to git

If you need to change your configuration later, you can re-run the install script, or edit the Vagrantfile directly.

Updating

To update an existing installation of the-vagrant in a project, you will need to:

  1. composer update palantirnet/the-vagrant
  2. Follow any steps from the release notes.

Note: If you need to update the underlying VM (the Vagrant box drupalbox, which includes PHP, Apache, MySQL, and Solr), you will need to run vagrant destroy then vagrant box update and vagrant up. Updating the VM doesn't always require updating the-vagrant, and vice versa.

Customizing your environment

Several things can be configured during the interactive installation:

A few more things can be customized directly in your Vagrantfile:

By default, the-vagrant references ansible roles from the package at vendor/palantirnet/the-vagrant/conf/vagrant/provisioning. If your project needs configuration beyond what is provided via in the Vagrantfile, you can re-run the install script and update the provisioning.

Run a custom playbook in addition to the defaults

  1. Re-run the install script: vendor/bin/the-vagrant-installer
  2. When you are prompted to copy the Ansible roles, reply n
  3. When you are prompted to add an additional Ansible playbook to your project, reply Y

    Copy Ansible roles into your project for customization (Y,n) [n]? n

    OR add an additional Ansible playbook to your project (Y,n) [n]? Y

  4. This will create a new provisioning directory in your project that contains a simple Ansible playbook and example role. Your Vagrantfile will refer to this playbook in addition to the one in the vendor directory.
  5. Check in and commit this new provisioning directory and updated Vagrantfile to git
  6. Add or update the roles and playbook as necessary.

Tips for developing Ansible playbooks and roles

Default Software

the-vagrant uses Vagrant boxes built with palantirnet/devkit. Releases of this Vagrant base box are on Vagrant Cloud. You can find more information about the specifics of accessing default software like MySQL, Solr, and Mailhog in the Drupalbox README.

Compatibility between the-vagrant and base boxes

Some versions of the-vagrant are coordinated with releases of the palantir/drupalbox Vagrant box:

the-vagrant version palantir/drupalbox version Vagrant provider Vagrant version
2.2.0 >= 1.2.0, < 2.0 virtualbox >= 2.1.0
2.1.0 >= 1.2.0, < 2.0 virtualbox
2.0.1 1.1.1, 1.2.0 virtualbox
2.0.0 1.1.0, 1.1.1 virtualbox, vmware_desktop (drupalbox v1.1.0 only)
0.6.0 - 1.1.1 >= 0.2.4, < 1.0 virtualbox, vmware_desktop

* Note that version 1.2.0 of the palantir/drupalbox VM requires updating to version 2.0.1 of palantirnet/the-vagrant.


Copyright 2016 - 2020 Palantir.net, Inc.


All versions of the-vagrant with dependencies

PHP Build Version
Package Version
Requires phing/phing Version ^2.14
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/the-vagrant contains the following files

Loading the files please wait ....