Docker setup not working: add special flag and utilize --web option

[warengonzaga]

Problem:
Docker is not working as expected. When running Docker, the CLI appears, but users cannot proceed with the setup.

Steps to Reproduce:

1. Run Docker for the project.
2. Observe that the CLI opens, but setup cannot be completed as a user.

Expected Behavior:
Users should be able to configure the project via the Docker CLI setup.

Proposed Solution:

• Add a special flag to the CLI specifically for Docker installation.
• Create/extend the setup flag to utilize the --web option to support Docker-specific installations.

Notes:
This improvement will enhance usability for users running the project in Docker environments and streamline setup procedures.

[warengonzaga]

@youhanasheriff are you taking this or I'll take this?

[youhanasheriff]

Hey @warengonzaga,
I got busy the whole weekend. I still can't make time to look into it.
Either you can take this or I can take this up tomorrow.

[warengonzaga]

Hey @warengonzaga, I got busy the whole weekend. I still can't make time to look into it. Either you can take this or I can take this up tomorrow.

No worries!

[youhanasheriff]

Hey @warengonzaga,

What's the status?

[warengonzaga]

Haven't check this @youhanasheriff I can assign it to you need to fix the dev branch first.

[youhanasheriff]

Starting this today guys!. Will update on the progress later tonight.

[lustsazeus-lab]

Nice issue write-up. Since this is already assigned, a low-risk implementation detail is to parse Docker detection early and route setup into a non-interactive web-safe path.

Concretely: expose one explicit --docker mode (can internally map to --web) and skip TTY-only prompts when CI/container env is detected. That usually prevents the “CLI opens but cannot proceed” dead-end.

[warengonzaga]

Nice issue write-up. Since this is already assigned, a low-risk implementation detail is to parse Docker detection early and route setup into a non-interactive web-safe path.

Concretely: expose one explicit --docker mode (can internally map to --web) and skip TTY-only prompts when CI/container env is detected. That usually prevents the “CLI opens but cannot proceed” dead-end.

@youhanasheriff you might want to consider this ^