coolify icon indicating copy to clipboard operation
coolify copied to clipboard

Coolify CLI

Open kosheeta opened this issue 4 years ago • 7 comments

Start, stop, get current status and other via Coolify CLI. For example:

$ coolify start
[INFO] Starting Coolify...
[INFO] Coolify successfulity started at admin.example.com!

$ coolify start
[INFO] Starting Coolify...
[ERROR] Coolify already started!

$ coolify stop
[INFO] Stopping Coolify...
[INFO] Shutting down all app containers...
[INFO] Good buy!

$ coolify status
[INFO] Coolify already started at admin.example.com. Now running 2 apps and 1 database.

kosheeta avatar Jun 07 '21 14:06 kosheeta

Great idea, but I do not see the benefit of a CLI. Why do you think it will be the benefit of a CLI tool like this?

andrasbacsai avatar Jun 11 '21 09:06 andrasbacsai

Great idea, but I do not see the benefit of a CLI. Why do you think it will be the benefit of a CLI tool like this?

Via this tool you can easily start and stop Coolify, which is now quite problematic.

kosheeta avatar Jun 16 '21 13:06 kosheeta

Why do you would like to start/stop Coolify? If you don't stop it by hand, it should start automatically on server restart, for example.

I would like to understand the use-case a bit better.

andrasbacsai avatar Jun 17 '21 12:06 andrasbacsai

I could help you with this, build it in go, if you want.

inluxc avatar Jul 05 '21 18:07 inluxc

Why do you would like to start/stop Coolify? If you don't stop it by hand, it should start automatically on server restart, for example.

I would like to understand the use-case a bit better.

I would believe that it is useful when deploying Coolify locally for staging environments; beyond this even in production there may be use cases where there cases over port overlaps between multiple applications and a restart of Coolify may be necessary.

badlanguage avatar Jul 26 '21 14:07 badlanguage

I can see the benefits of having a CLI for this project. Having to rely on dashboard, it is more resource saver if we use CLI to control things using CLI like for example, deploying a new application or services using the CLI only. Which is in my opinion much faster to do it via dashboard.

Based on my experience with the dashboard, when I create a new local docker it just hangs, no info or pop-ups that the docker has been set up. So having a CLI would be more beneficial for some CLI users.

warengonzaga avatar Mar 31 '22 09:03 warengonzaga

I absolutely agree with @warengonzaga, take the example of Vercel CLI , I can deploy apps at my will directly from my local terminal.

themodernpk avatar May 15 '22 19:05 themodernpk

CLI for v4 is in progress.

I'm closing this issue, because tracking features will be moved to GitHub discussions. Github issues will be only for bugs.

Version 4 is in full focus. v3 related issues will be closed, if it is not a critical bug.

Thanks for your understanding.

andrasbacsai avatar Sep 08 '23 07:09 andrasbacsai