craftcms / craftcms/cms

`setup/welcome` command fails because of Redis/Docker setup

Open
#6,817 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

Description

I've got a Docker setup with a Redis container, but in between running composer create-project xxxx/craft . and docker-compose up I'd like to run ./craft setup/welcome to get an App ID and a Security Key. Currently if I run it, I'm getting this error: Failed to open redis DB connection, which makes sense because Redis isn't running at this point. It would seem the welcome controller shouldn't care about my Redis connection, in the same way it doesn't care if Craft has a DB connection yet...

Steps to reproduce
  1. Add an unreachable Redis config to Craft
  2. craft setup/welcome
Additional info
  • Craft version: 3.5
  • PHP version: any
  • Database driver & version: any
  • Plugins & versions: none

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the setup/welcome command and its welcome controller, then reproduce the failure using an unreachable Redis configuration before Docker services are started. Trace why the command opens the Redis connection and make completion independent of Redis availability, verifying that ./craft setup/welcome produces the App ID and Security Key in the described setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, php, redis
Domain
backend, cli, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.