Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open dashboard on browser after `tye run` #353

Open
giggio opened this issue Apr 10, 2020 · 4 comments
Open

Open dashboard on browser after `tye run` #353

giggio opened this issue Apr 10, 2020 · 4 comments
Assignees
Milestone

Comments

@giggio
Copy link
Contributor

@giggio giggio commented Apr 10, 2020

What should we add or change to make your life better?

After tye run, open the dashboard on a browser. Enabling this should be configurable, in a user setting and/or project setting.

Why is this important to you?

It's one less step on the development workflow.

@giggio giggio added the idea label Apr 10, 2020
@rynowak
Copy link
Member

@rynowak rynowak commented Apr 10, 2020

Thanks for the idea. It looks like someone's already working on the basic functionality. #350

Enabling this should be configurable, in a user setting and/or project setting.

We should talk more about this part @davidfowl

I like the idea of per-user options via env-vars as well as via command-line - allowing you to set env-vars to provide options like --dashboard makes things less repetative.

So like $env:TYE_RUN_ARGS="--dashboard" in your profile would toggle on this behavior all of the time.

@rynowak rynowak added this to the backlog milestone Apr 28, 2020
@rynowak
Copy link
Member

@rynowak rynowak commented Apr 28, 2020

We like the environment variable solution for making this configurable.

@qpooqp
Copy link

@qpooqp qpooqp commented Oct 27, 2020

Hello

I tried to solve this issue (initially just for myself to learn some stuff) and i think that i came up with decent solution which you could use.

Brief description
It is generic solution to apply default options to commands.
Environment variable is choosen by convention as TYE_{command name uppercase}_ARGS.
It applies all non already applied options from env-var to command.
It can be disabled with option --no-default.

Examples
User creates env-var: TYE_RUN_ARGS="--v debug --dashboard"

  • User runs command tye run --v quiet which will become tye run --v quiet --dashboard
    Option -v is already applied so we will not reapply it. Option --dashboard is applied.
  • User runs command tye run which will become tye run --v debug --dashboard
    Both options are missing so we will apply them
  • User runs command tye run --no-default which stays as tye run --no-default
    User specified the --no-default option which disables this feature
  • User runs command tye deploy which stays as tye deploy
    Env-var was not found for deploy command (expected TYE_DEPLOY_ARGS).

Is it something what you were looking for?
I would create a PR if you would like to check it out more.

@giggio
Copy link
Contributor Author

@giggio giggio commented Oct 29, 2020

@qpooqp that would work for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant