Download the PHP package ignislabs/freighter without Composer

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

Freighter

Easy docker development environment management for PHP and Laravel.

You don't need to have a Laravel project to use Freighter.
You have more toys if you're using Laravel, but you certainly don't require to do so.

It does come with Laravel-oriented commands, but you don't need to use them.

It also does use the database environment variables names as defined by Laravel, but as long as you have an .env file with those variables declared, it's more than enough.

Installation

You install it with composer:

Then you need to run init just this first time (or when a new version is released):

init copies the freighter binary to the root of your repo, makes it executable and adds it to .gitignore, since you don't need to track it.

And now you're ready to use it:

The Stack

The stack provided is comprehensive, but we try to keep it as minimal as possible by using Alpine Linux whenever possible.

Ports

Inside your containers, the ports will remain the default ones. But when accessing them from the host machine it's a different story.

Freighter plays nice with other services that you might be already running by using easy to remember non-standard ports by default:

You can override these defaults by setting the appropriate environment variables in your .env file to the desired values:

Hosts

Inside your containers the host names will correspond to the services names as defined in the Compose file, so you'll need to replace them in your .env file:

If using Laravel you'll probably also need to add QUEUE_HOST in your config/queue.php manually since Laravel comes with it hardcoded by default. Just add 'host' => env('QUEUE_HOST', 'localhost'), to the beanstalkd connection.

MySQL

Freighter uses the credentials from environment variables defined in your.env file, so you can use those to connect from your host machine.

Just remember to use the correct port (33060 by default).

The variable names follow the Laravel convention:

Commands

Freighter comes with a few native commands, and more will be coming.

Any unrecognized command will be handed down to docker-compose.

You can see any command's help by passing -h. Some commands will also show help if you omit all arguments.

Start and stop your environment

Customize services

If you want to customize the compose file, you can copy the one in vendor to your repo manually or by running ./freighter copy-services.

If a compose file is found here, Freighter will use this one instead of the one in vendor.

This way Youy can add services or customize the existing ones. As long as you keep te same service names, you should be fine.

Composer

Artisan

Laravel logs

Testing

Shell access

MySQL

Running Docker Compose commands

As I mentioned earlier, any unrecognized command will be handed down to docker-compose. So you can run any docker-compose command, with the added benefit of having the environment variables in place.

Custom commands

Freighter is incredibly easy to extend (as long as you know your way around bash scripting :bowtie:).

Just create a directory named freighter.d at the root of your repo and add shell scripts in it, Freighter will be pick them up immediately.

These files need to declare functions prefixed as _fcmd_, for example: _fcmd_artisan.

Take a look at the native ones in vendor/ignislabs/freighter/freighter.d so you have an idea of how to write them.

An artisan command to generate custom Freighter commands even quicker is in the works.

All versions of freighter 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 ignislabs/freighter contains the following files

Loading the files please wait ....