webteractive/devstack

Devstack

v1.1.8 2023-05-19 08:06 UTC

Requires

• guzzlehttp/guzzle: ^7.5.1
• illuminate/support: ^10.3
• league/flysystem: ^3.0
• symfony/console: ^6.2
• symfony/finder: ^6.2
• symfony/process: ^6.2
• vlucas/phpdotenv: ^5.5

Requires (Dev)

• mockery/mockery: ^1.5.1
• pestphp/pest: ^1.22.3
• symfony/var-dumper: ^6.2

MIT

• Glen Gringgo Bangkila

• cli
• console
• devstack

README

Requirements

• PHP 8+
• Composer

Installation

This assumes that PHP and Composer is already installed. This also assumes that the Composer's bin is already added to your path (Add export PATH=~/.composer/vendor/bin:$PATH to your .zshrc ). To install the command do:

• Open the terminal and run composer global require webteractive/devstack. This will install a CLI command devstack.
• Running the devstack command should list all available commands that you can use.

Initializing Runtimes

There are to ways to initialize runtimes.

1. By running devstack init https://github.com/vendor/the-name-of-the-runtime.
2. By using a private repository. This good for runtimes that you don't want to share to the world.

Using Private Runtimes

You can do this by following the steps below:

1. Run the devstack config command, this will ask the repository url, the branch, and token. The token here is your personal access token. Visit this page for more details on how to obtaine one.
2. Once the configuration is done, you may now initialize runtimes from your private repository by doing devstack init the_runtime_name.
3. To download the latest runtimes in your repository, run devstack download.

Running Docker Compose Commands

1. If your are greeted by "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" after running a command, this means that your docker or docker desktop is not running.
2. If you are greeted by "no configuration file provided: not found" after running a command, this means that your current directory doesn't have the docker-compose.yml file.
3. If you are greeted by "service "<service>" is not running container #1" after running the following commands devstack redis, devstack mysql, devstack php, devstack shell, and devstack composer, this means that the containers are not yet up. Run devsatck up -d to start.
4. If your are greeted by "Could not open input file: artisan" after running devstack artisan, this means that the current runtime you are running has no Laravel Artisan command or is not a Laravel project.