You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you have to run commands from the directory where the flow.json file is located.
It would be great if users could point to the location using a flag, in situations where it's not ideal to run the command from the same directory as the file.
eg:
flow deploy --config ../../flow.json
The text was updated successfully, but these errors were encountered:
Do you mean for project deploy? This will be solved with the current migration of the configuration we are working on. For other commands (beside project) you have a flag --config-path.
Do you mean for project deploy? This will be solved with the current migration of the configuration we are working on. For other commands (beside project) you have a flag --config-path.
Great sounds like we can close this when those changes are merged.
Currently you have to run commands from the directory where the flow.json file is located.
It would be great if users could point to the location using a flag, in situations where it's not ideal to run the command from the same directory as the file.
eg:
The text was updated successfully, but these errors were encountered: