["Bug"] Misleading success message for non-exposed application

Open
#108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

Start by locating the deployment success output in caprover-cli and check how it handles applications that are not exposed as web applications. Verify the behavior with a deployment of a non-web application; done means the success message no longer implies that an application is publicly available when it is not.

Written by the indexing model from the issue text.

Description

enhancement

Hi all,
I'm using caprover-cli for deployments. Some of the applications I deploy are not exposed as web-application. Nevertheless, a successful deployment is finished with message (auto-"censored" via GitHub Actions):

Deployed successfully ***
App is available at http://***.darkspirit510.de

It's just a little irritating and sounds as if this exposed my application. Therefor, the tag bug might be misleading 🙈

Dominant language
TypeScript
Stars
78
Forks
43
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from caprover/caprover-cli

All issues in caprover/caprover-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.