Download the PHP package saucebase/installer without Composer

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

Saucebase Installer

Tests PHP Saucebase

The official CLI for creating Saucebase applications — a globally-installed Composer package, like laravel/installer.

saucebase new creates a new project and runs the full install flow (environment, database, frontend, modules) in one pass. No PHP yet? Use the one-command bootstrap at install.saucebase.dev.

Requirements

The CLI checks and instructs for prerequisites — it never installs them for you.

Installation

Make sure Composer's global bin directory is on your PATH (composer global config bin-dir --absolute).

Commands

saucebase new <name>

Creates a new Saucebase application and installs it end to end.

Runs a self-update check, then collects every choice upfront (driver → SSL if Docker → stack → modules) so the install runs unattended. It scaffolds the app via laravel/installer (using the saucebase/saucebase starter kit), then runs the full install flow against it. Your driver choice is remembered in ~/.config/saucebase/config.json as the default for next time.

Options

Option Description
--driver=docker\|native Environment driver (skips the prompt)
--stack=vue\|react Frontend stack (skips the prompt)
--ssl=yes\|no Enable HTTPS via mkcert, Docker only (skips the prompt)
--modules=auth,billing Install specific modules by name, or none to skip modules
--all-modules Install every module compatible with the stack
--using=vendor/skeleton Use a different starter kit instead of saucebase/saucebase
--fresh Run migrate:fresh instead of migrate (destructive)
--force Overwrite an existing directory and skip confirmations
--dev Contributor mode (uses the skeleton's dev branch, skips modules)

Examples

saucebase install

Runs the install flow against an existing Saucebase app. This is what new calls under the hood; run it standalone to (re)provision an app you already have.

Takes an optional stack argument (vue/react) and the same --driver, --ssl, --modules, --fresh, --force options as new, plus --path to target a directory other than the current one.

Docker driver — copies the Docker stubs (docker-compose.yml, Dockerfile, nginx.conf, …), generates SSL certs if enabled, patches .env with MySQL/Mailpit/APP_URL defaults, brings up docker compose, then generates APP_KEY, migrates, wires the frontend, and installs modules.

Native driver — copies .env.example → .env, generates APP_KEY, migrates and seeds, wires the frontend, installs modules, and links storage.

saucebase stack <vue|react>

Selects or switches the frontend framework for an app.

Copies the framework-specific source, config (package.json, vite.config.js, tsconfig.json, …), lockfile, and blade layout into place, removes the unused framework's directory, and records the choice in frontend.json.

Options

Option Description
--path=<dir> Target app directory (defaults to the current directory)
--dev Contributor mode — config only, keeps both source dirs, uses git skip-worktree, runs npm install
--reset Reverts generated files to their pre-selection state

Note: Framework selection is permanent for a given installation. To switch, start a new project or use --reset (dev mode).

How it works

saucebase is a standalone Illuminate\Console\Application (not a Laravel package — no service provider). It operates on a target directory via --path, running artisan steps as subprocesses (php <path>/artisan …). Project creation is delegated to laravel/installer; everything after — environment, database, frontend, modules — is the Saucebase install flow.

License

MIT

All versions of installer with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
composer-runtime-api Version ^2.2
guzzlehttp/guzzle Version ^7.8
illuminate/console Version ^13.0
illuminate/container Version ^13.0
illuminate/events Version ^13.0
illuminate/filesystem Version ^13.0
illuminate/http Version ^13.0
illuminate/support Version ^13.0
laravel/installer Version ^5.14
laravel/prompts Version ^0.3
symfony/process 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 saucebase/installer contains the following files

Loading the files please wait ...