Download the PHP package yejune/bootapp without Composer

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

bootapp

Docker CLI Plugin for multi-project Docker networking made easy.

Automatically manages:

Installation

Method 1: Using Homebrew (macOS)

Homebrew automatically:

Method 2: Using install script (Linux/macOS)

The install script automatically:

Method 3: Using go install

Or build locally:

The install command automatically:

Method 4: Manual installation

Usage

Start containers

If multiple compose files are found, you'll be prompted to select interactively:

Supported file patterns:

Options:

This will:

  1. Allocate unique subnet for the project (172.18-31.x.x range)
  2. Parse docker-compose file for DOMAIN/SSL_DOMAINS configuration
  3. Generate SSL certificates for SSL_DOMAINS (if not exists)
  4. Install certificates to system trust store (macOS Keychain / Linux ca-certificates)
  5. Start containers with docker-compose up
  6. Discover container IPs from default compose network
  7. Add /etc/hosts entries for containers with domain config
  8. Setup routing if needed (macOS)

Stop containers

Options:

List projects

Domain Configuration

Supported Environment Variables

All of these environment variables are used for both:

Supported variables (duplicates removed, each supports single, comma, space, or newline separated values):

Container-to-Container Communication

Domains set via DOMAIN/DOMAINS are automatically registered as Docker network aliases, allowing containers to reach each other:

This replaces the deprecated external_links and works automatically with Docker's built-in DNS.

Traefik Labels

Traefik router rules are also supported:

Result

Only services with explicit domain configuration get /etc/hosts entries:

Services without DOMAIN config (like redis above) are not added to /etc/hosts.

SSL Certificates

Automatic Generation

bootapp automatically generates self-signed SSL certificates for domains specified in SSL_DOMAINS:

Certificates are:

Certificate Files

Force Regenerate

To delete and regenerate certificates:

The -F flag will:

  1. Remove existing certificates from trust store
  2. Delete local certificate files
  3. Generate new certificates
  4. Install to trust store
  5. Force recreate containers

nginx Configuration Example

macOS Networking

docker-mac-net-connect is required for direct container IP access on macOS.

Docker Desktop runs containers inside a Linux VM, so macOS cannot directly access container IPs without a network tunnel.

Installation

bootapp will check for docker-mac-net-connect and show installation instructions if not found.

Linux

✅ All features work natively on Linux!

Linux support includes:

  1. Docker Networking

    • Unique subnet per container
    • Direct container IP access (no additional tools needed)

  2. SSL Certificate Auto-generation & Trust

    • Debian/Ubuntu: update-ca-certificates
    • RHEL/CentOS: update-ca-trust
    • Self-signed certificates automatically trusted system-wide

  3. Automatic /etc/hosts Management

    • Domain → Container IP mapping
    • Auto register/cleanup per project
  4. Standalone Binary + Docker Plugin
    • Use bootapp or docker bootapp commands

Installation:

Unlike macOS, Linux doesn't need additional network tools (docker-mac-net-connect) - everything works out of the box!

Domain TLD Recommendations

Recommended TLDs:

Avoid:

Configuration

Global configuration is stored in ~/.bootapp/projects.json:

Each project gets a unique subnet (172.18.x.x through 172.31.x.x) to prevent IP conflicts between projects.

License

MIT

All versions of bootapp with dependencies

PHP Build Version
Package Version
Requires php Version >=8
symfony/process Version 6.*
symfony/finder Version 6.*
symfony/yaml Version 6.*
react/child-process Version ^0.5
mkraemer/react-pcntl Version ^2
herrera-io/phar-update Version ^2.0
peanut/console Version dev-master
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 yejune/bootapp contains the following files

Loading the files please wait ...