HaaS CLI

Question

HaaS CLI

Closed this issue 3 years ago · 12 comments

cjdenio commented 3 years ago

A CLI for managing apps, streaming logs, viewing billing, etc. (basically Heroku's CLI but better)

(i wouldn't be opposed to writing this in a non-Go language)

quackduck commented 3 years ago

agreed

Answer 1 · 2021-05-03T19:27:07.000Z

So is this just a command line API client?

Answer 2 · 2021-05-03T21:34:40.000Z

Pretty much, yeah

Answer 3 · 2021-05-03T22:47:57.000Z

I could work on this in Python if that's an okay language, I like working on CLI's. (I can also help in another language, just won't be as helpful.)

Answer 4 · 2021-05-03T23:43:44.000Z

Features we want (based on this convo, feel free to edit as wanted):

Log streaming
Package apps as .tar.gz and deploy them (unsupported by API currently)
Viewing balances and creating invoices
App status checking

Answer 5 · 2021-05-04T00:48:17.000Z

I can spearhead this if you guys are cool with that. I really think that we should make it in go for a few reasons:

The API is currently written in go so it would be easy for people working on the API to help out.
go compiles binaries to a static binary right out of the box so it is easy to distribute.
go has a number of great modules for creating cli tools that are some of the best out there.
Tools like goreleaser make it super easy to distribute the cli via homebrew, releases, and even a shell script.

Answer 6 · 2021-05-04T00:56:23.000Z

I agree that keeping it all in one language makes sense. I'd like to help with this, so I'll start trying to learn Go.

Answer 7 · 2021-05-04T04:38:49.000Z

I would not recommend python since people would then have to have python installed and python has a lot of issues with versions and installing. Since a lot of the rest of the codebase is in Go, I think that would be a good option.

…

On 4 May 2021, at 2:48 AM, Cole Wilson ***@***.***> wrote: I could work on this in Python if that's an okay language, I like working on CLI's. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/hackclub/hack-as-a-service/issues/120#issuecomment-831582679>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJIU2R5K7CX2T3YHSBO5HA3TL4R23ANCNFSM44BJEC7A>.

Answer 8 · 2021-05-04T13:18:10.000Z

I would like to work on this one and build the entire thing in Go

Answer 9 · 2021-05-04T13:36:21.000Z

Is creating a different repo for the CLI really necessary?

CC @cjdenio @anirudhb @jasonappah

Answer 10 · 2021-05-04T13:39:33.000Z

Based on slack discussion it was decided we should keep it in the same repo. My concern was that the repo would get kinda confusing to navigate with more folders, but we can make issue/PR labels for frontend, cli, docs, and backend so it's easy to keep track of everything, and add a more detailed contributing guide, so that should be fine.

…

On Tue, May 4, 2021 at 8:36 AM Ishan Goel ***@***.***> wrote: Is creating a different repo for the CLI really necessary? CC @cjdenio <https://github.com/cjdenio> @anirudhb <https://github.com/anirudhb> @jasonappah <https://github.com/jasonappah> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/hackclub/hack-as-a-service/issues/120#issuecomment-831947338>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHJQZCKXMPQ6LCHSEHWSYFDTL7Z6ZANCNFSM44BJEC7A> .

Answer 11 · 2021-05-04T15:12:19.000Z

At this point, I feel like we should just stick with a monorepo setup.