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
Parameters location should be decided based on their portability.
For example for flatbuffers-generator: flatcc binary path is always the same? No, in github actions flatcc a musl precompiled binary pulled from a repo, placed in a directory that is not in PATH.
On the other hand network.json is in a standard path for the whole project, it doesn't matter if you run the project on a workstation, over github actions or on your own laptop, thus it should be specified on the config.py.
As a rule of thumb parameters that might change MUST be implemented as running parameters in such a way to avoid edits to config.py that might result to a commit that modifies the remote config.py.
The text was updated successfully, but these errors were encountered:
Parameters location should be decided based on their portability.
For example for flatbuffers-generator: flatcc binary path is always the same? No, in github actions flatcc a musl precompiled binary pulled from a repo, placed in a directory that is not in PATH.
On the other hand network.json is in a standard path for the whole project, it doesn't matter if you run the project on a workstation, over github actions or on your own laptop, thus it should be specified on the config.py.
As a rule of thumb parameters that might change MUST be implemented as running parameters in such a way to avoid edits to config.py that might result to a commit that modifies the remote config.py.
The text was updated successfully, but these errors were encountered: