Download the PHP package savvywombat/pilot without Composer

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

Informations about the package pilot

Pilot

A lightweight wrapper to help run PHP projects in Docker.

Pilot wraps the docker-compose command line tool to allow you to use .env files and inject environment variables into your docker-compose.yml and Dockerfile, making it easier to set up and run projects.

Pilot includes Dockerfiles to set up and run PHP 8.1 and 8.2, although with minimal extensions. You can use your own docker-compose.yml and Dockerfiles configuration with Pilot if you need more than this.

Pilot is designed to help work with Docker containers in development environments, and is not recommended for use in production.

Getting started

Requirements

You will need to have Docker and docker-compose installed on your machine for Pilot to work.

Installation

Pilot is available through Composer:

To get started, you can copy the docker-compose.yml file shipped with Pilot:

Or you can use your own docker-compose.yml to configure the services you need for your project.

Environment variables

If you have a .env file in the same location as your docker-compose.yml, Pilot will import them, allowing you to use them in docker-compose.yml and Dockerfiles.

Pilot uses the following environment variables with its default configuration:

Environment variables in docker-compose.yml

You can use environment variables within your docker-compose.yml. It is recommended that you also define a default value to fall back on in case the variable is not defined in your .env.

For example, in the default Pilot configuration, we define the ports on the default service like this:

If no HTTP_PORT has been defined in the environment when starting the services with pilot up, then the port would default to 80.

However, if you defined HTTP_PORT=8080 in your .env, then 8080 be the port exposed for forwarding.

Environment variables in Dockerfiles

Similarly, it is possible to use environment variables in your Dockerfiles, so that you can build your services to run with specific configurations.

Commands

Installing and building services

Copy the default docker-compose.yml from Pilot into your project's root directory.

Build the services defined in docker-compose.yml. This command is proxy for docker-compose build and so will accept the same arguments, such as --no-cache.

Accessing docker-compose commands

Apart from build, all docker-compose commands are proxied without modification, and can be used with the same arguments. Using Pilot ensures that environment variables defined in your .env are honoured when running these commands.

Run the services, or start them in listening mode:

Stop the services.

Stop the services and remove any volumes used by them:

Building and serving assets and content

To build any assets in your project. By default, it runs the npm run dev command. However, you can substitute another command line script with the BUILD_COMMAND environment variable:

To serve content as you develop. This command wraps the PHP built-in webserver and should not be used as a production webserver. The command automatically sets the host and port for the webserver, and accepts the root directory and router script arguments:

Additional commands

Open a terminal session on the main service:

Run a php script on the main service:

Run a Composer commands on the main service:

Run an npm command on the node service (this is by default the main service, but you can define a separate service in your docker-compose.yml for Node and set NODE_SERVICE to the name of your Node service):

Support

Please report issues using the GitHub issue tracker. You are also welcome to fork the repository and submit a pull request.

Licence

This package is licensed under The MIT License (MIT).

All versions of pilot with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0
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 savvywombat/pilot contains the following files

Loading the files please wait ....