Download the PHP package kilroyweb/homeboy without Composer

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

Informations about the package homeboy

Homeboy

Tool for automating sites using Laravel Homestead. With one command, Homeboy will be able to:

You can also use homeboy to provision non-laravel websites!

Table of Contents

Requirements

On your local (non homestead) machine, Homeboy requires:

Installation

Install as a global composer package

Make sure to place the $HOME/.composer/vendor/bin directory (or the equivalent directory for your OS) in your $PATH so the laravel executable can be located by your system.

Once installed, you can use homeboy command from anywhere on your system.

Run the setup command to generate a .env file

Install using git clone

Run the setup command to generate a .env file

By this point, you should be able to run homeboy within the directory using the command:

On mac (in ~/.bash_profile) add:

On windows, an alias can be added using something like if using a tool like Cmder

be sure to edit the path based on where homeboy is installed

Setting Configuration

After running , you should have a .env file in your homeboy directory with a few defaults that have been generated.

These options will likely need to be updated based on your particular setup, details about each available setting are listed below:

USE_COMPOSER

Default option to determine if homeboy should create a new composer project

DEFAULT_COMPOSER_PROJECT

Default package used when creating a composer project

DEFAULT_FOLDER_SUFFIX

When hosting a new project, the default directory that nginx would define as the document root. For Laravel projects, by default this is "/public"

DEFAULT_DOMAIN_EXTENSION

When creating development domains, the default domain suffix given when a domain is generated

HOSTS_FILE_PATH

The location to your local hosts file that homeboy will add to when hosting new projects

This file will need to have permissions adjusted to be editable by homeboy

HOMESTEAD_HOST_IP

The ip address given to your homestead virtual machine. This is likely found in your Homestead.yaml file

HOMESTEAD_FILE_PATH

The location to your Homestead.yaml file. Homeboy will update this file's sites list and database list when creating new projects

HOMESTEAD_SITES_PATH

The root path to your websites in your homestead virtual machine

HOMESTEAD_BOX_PATH

The path to your Homestead directory

LOCAL_SITES_PATH

The path on your local machine to where you store your projects. Homeboy will cd into this directory when running "composer create-project ..."

HOMESTEAD_ACCESS_DIRECTORY_COMMAND

In Windows if you are running Homestead on a different drive, an extra command may be required to switch drives before cd'ing into your directory.

This option will cause Homeboy to ignore the option: HOMESTEAD_BOX_PATH

ACCESS_LOCAL_SITES_DIRECTORY_COMMAND

Similar to HOMESTEAD_ACCESS_DIRECTORY_COMMAND, In Windows if your root project directory is on a different drive, an extra command may be required to switch drives before cd'ing into your directory.

This option will cause Homeboy to ignore the option: LOCAL_SITES_PATH

Homeboy Commands

Host

Because this is the default command, you can run host by simply running:

Running this command automates the task of creating a new composer project, updating your hosts file and vagrant files when provisioning a new website

When the command runs, it prompts for the sites directory name, database name, and dev url to update the needed files and then provisions vagrant

A few options have been added to speed up the command. However because the command "homeboy" is simply a shortcut for "homeboy host" (allowing us to add additional commands in the future), options only work when calling "homeboy host" rather than just "homeboy".

Some options available:

The following example will run all tasks automatically without any question prompts:

Vagrant

Homeboy also contains the "vagrant:run" command, allowing you to quickly run any vagrant command without having to cd into that directory, ie:

File

Quickly view a file contents by running:

or

Domain

The domain command lets you quickly add a new domain record to your hosts file.

Composer

The composer:create-project command prompts you details on running a "composer create-project [composer-project] [project-name]" command

Troubleshooting

hosts file is not writable

Your host file will need to be writable by homeboy. In many cases this can be solved with a command like:

This may vary depending on your platform / environment

Homeboy is running composer install within my current directory, rather than my defined LOCAL_SITES_PATH

A common cause of this on Windows is when LOCAL_SITES_PATH is in a different drive than where the homeboy command is being run. Since Windows must first change drives before cd'ing into the directory, you can use the "ACCESS_LOCAL_SITES_DIRECTORY_COMMAND" to overwrite how homeboy accesses this directory. For example:

Vagrant returns "A Vagrant environment or target machine is required to run this command"

This message will be displayed when Homeboy is unable to cd into the proper vagrant directory when running vagrant commands. Please verify your "HOMESTEAD_BOX_PATH" value to ensure it is correct.

On Windows, if your HOMESTEAD_BOX_PATH is in a different drive than the drive you are running your homeboy command, you may need to add the "HOMESTEAD_ACCESS_DIRECTORY_COMMAND" to add any additional commands (such as switching drives) when accessing the directory. For example:

All versions of homeboy with dependencies

PHP Build Version
Package Version
Requires symfony/console Version ^3.3
vlucas/phpdotenv Version ^2.4
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 kilroyweb/homeboy contains the following files

Loading the files please wait ....