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

feat: Add dart build/run arguments to dart_frog dev command #1490

Open
1 task
KhaledBasiony opened this issue Aug 23, 2024 · 2 comments
Open
1 task

feat: Add dart build/run arguments to dart_frog dev command #1490

KhaledBasiony opened this issue Aug 23, 2024 · 2 comments
Labels
feature A new feature or request p2 Important issues not at the top of the work list

Comments

@KhaledBasiony
Copy link

Description

I want to add a bunch of variables using dart's --define or -D

I can run dart_frog build then run dart build ... on the output, no problem.

But How can I pass these during development when using dart_frog dev ?

Requirements

  • pass multiple --define arguments to the dart_frog dev command

Additional Context

Add any other context or screenshots about the feature request go here.

@KhaledBasiony KhaledBasiony added the feature A new feature or request label Aug 23, 2024
@alestiago
Copy link
Contributor

Hi @KhaledBasiony 👋 ! Thanks for opening an issue, have you had the change to read through the Environments documentation? It might help to achieve what you're trying to accomplish.

@alestiago alestiago added the waiting for response Waiting for follow up label Aug 27, 2024
@KhaledBasiony
Copy link
Author

Hello @alestiago,
yes I am already using the platform environment variables, but I have some secret variables that are present at compile time (e.g. Github Actions) but should not be easily accessible (plain text) at the host machine (e.g. on-premises computer)

I know --define might not be the most secure way to achieve that but definitely better than sending my api keys in a .env file 😅

I have already worked around this on my dev environment with dart_frog build then dart run -D... i am just missing out on the auto restart feature

If you have another solution for the original problem I am open for ideas.

@alestiago alestiago removed the waiting for response Waiting for follow up label Aug 27, 2024
@tomarra tomarra added the p2 Important issues not at the top of the work list label Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new feature or request p2 Important issues not at the top of the work list
Projects
Status: Backlog
Development

No branches or pull requests

3 participants