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

Path dependencies #15

Open
LPGhatguy opened this issue Mar 2, 2020 · 0 comments
Open

Path dependencies #15

LPGhatguy opened this issue Mar 2, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@LPGhatguy
Copy link
Contributor

Sometimes, it's useful for projects to depend on versions of a tool that isn't managed by Foreman. This comes up when working on tools like Rojo, where I want to use the master branch by default, not any stable release.

To solve this, we could add path dependencies to Foreman, like:

[tools]
rojo = { path = "~/.cargo/bin/rojo" }

Are there any security concerns with this approach? Being able to run any binary on a user's system might be dangerous, and we might want to lock this down to the system config only.

@LPGhatguy LPGhatguy added the enhancement New feature or request label Mar 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant