PHPackages                             stakkr/docker-symfony - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. stakkr/docker-symfony

ActiveLibrary

stakkr/docker-symfony
=====================

Simple Docker dev environments

1.0.0(7y ago)114MITShell

Since Jun 19Pushed 7y ago1 watchersCompare

[ Source](https://github.com/zadil/stakkr-docker)[ Packagist](https://packagist.org/packages/stakkr/docker-symfony)[ RSS](/packages/stakkr-docker-symfony/feed)WikiDiscussions master Synced today

READMEChangelogDependenciesVersions (2)Used By (0)

stakkr-docker
=============

[](#stakkr-docker)

Up and running with small Docker dev environments.

Documentation
-------------

[](#documentation)

Full documentation can be found at .

Install
-------

[](#install)

Stakkr is just a small set of files that sets up a local Docker-based dev environment per project. There is nothing to install globally, except Docker itself!

This is all there is to using it:

```
composer require stakkr/docker-symfony

# Run this once to initialize project
# Must run with "bash" until initialized
bash stakkr init

./stakkr start
```

Head to `http://localhost` in your browser and see your Laravel site!

ou can do this with this command:

```
cp -R vendor/shipping-docker/vessel/docker-files/{vessel,docker-compose.yml,docker} .

```

and then you'll be able to install and continue as normal.

Multiple Environments
---------------------

[](#multiple-environments)

Stakkr attempts to bind to port 80 and 3306 on your machine, so you can simply go to `http://localhost` in your browser.

However, if you run more than one instance of Vessel, you'll get an error when starting it; Each port can only be used once. To get around this, use a different port per project by setting the `APP_PORT` and `MYSQL_PORT` environment variables in one of two ways:

Within the `.env` file:

```
APP_PORT=8080
MYSQL_PORT=33060

```

Or when starting Stakkr:

```
APP_PORT=8080 MYSQL_PORT=33060 ./stakkr start
```

Then you can view your project at `http://localhost:8080` and access your database locally from port `33060`;

Common Commands
---------------

[](#common-commands)

Here's a list of built-in helpers you can use. Any command not defined in the `vessel` script will default to being passed to the `docker-compose` command. If not command is used, it will run `docker-compose ps` to list the running containers for this environment.

### Starting and Stopping Vessel

[](#starting-and-stopping-vessel)

```
# Start the environment
./stakkr start

## This is equivalent to
./stakkr up -d

# Stop the environment
./stakkr stop

## This is equivalent to
./stakkr down
```

### Development

[](#development)

```
# Use composer
./stakkr composer
./stakkr comp  # "comp" is a shortcut to "composer"

# Use artisan
./stakkr bin/console
./stakkr console  # "console" is a shortcut to "bin/console"

# Run phpunit tests
./stakkr test

## Example: You can pass anything you would to phpunit to this as well
./stakkr test --filter=some.phpunit.filter
./stakkr test tests/Unit/SpecificTest.php

# Run npm
./stakkr npm

## Example: install deps
./stakkr npm install

# Run yarn

./stakkr yarn

## Example: install deps
./stakkr yarn install

# Run gulp
./stakkr gulp
```

### Docker Commands

[](#docker-commands)

As mentioned, anything not recognized as a built-in command will be used as an argument for the `docker-compose` command. Here's a few handy tricks:

```
# Both will list currently running containers and their status
./stakkr
./stakkr ps

# Check log output of a container service
./stakkr logs # all container logs
./stakkr logs app # nginx | php logs
./stakkr logs mysql # mysql logs
./stakkr logs redis # redis logs

## Tail the logs to see output as it's generated
./stakkr logs -f # all logs
./stakkr logs -f app # nginx | php logs

# Start a bash shell inside of a container
# This is just like SSH'ing into a server
# Note that changes to a container made this way will **NOT**
#   survive through stopping and starting the vessel environment
#   To install software or change server configuration, you'll need to
#     edit the Dockerfile and run: ./vessel build
./stakkr exec app bash
```

What's included?
----------------

[](#whats-included)

The aim of this project is simplicity. It includes:

- PHP 7.2
- MySQL 5.7
- Redis ([latest](https://hub.docker.com/_/redis/))
- NodeJS ([latest](https://hub.docker.com/_/node/)), with Yarn & Gulp

How does this work?
-------------------

[](#how-does-this-work)

If you're unfamiliar with Docker, try out this [Docker in Development](https://serversforhackers.com/s/docker-in-development) course, which explains important topics in how this is put together.

If you want to see how this workflow was developed, check out [Shipping Docker](https://serversforhackers.com/shipping-docker) and signup for the free course module which explains building this Docker workflow.

Supported Systems
-----------------

[](#supported-systems)

Stakkr requires Docker, and currently only works on Windows, Mac and Linux.

> Windows requires running Hyper-V. Using Git Bash (MINGW64) and WSL are supported. Native Windows is still under development.

MacLinuxWindowsInstall Docker on [Mac](https://docs.docker.com/docker-for-mac/install/)Install Docker on [Debian](https://docs.docker.com/engine/installation/linux/docker-ce/debian/)Install Docker on [Windows](https://docs.docker.com/docker-for-windows/install/)Install Docker on [Ubuntu](https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/)Install Docker on [CentOS](https://docs.docker.com/engine/installation/linux/docker-ce/centos/)

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity7

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity62

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

2883d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/4b92d4bf57c4d1b1068c3b1338829ae4fca2fab9d5f0b0041b62a20b0b871c4a?d=identicon)[zadil](/maintainers/zadil)

---

Top Contributors

[![zadil](https://avatars.githubusercontent.com/u/5960466?v=4)](https://github.com/zadil "zadil (4 commits)")

### Embed Badge

![Health badge](/badges/stakkr-docker-symfony/health.svg)

```
[![Health](https://phpackages.com/badges/stakkr-docker-symfony/health.svg)](https://phpackages.com/packages/stakkr-docker-symfony)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)