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

vargo new --neon #8

Open
dherman opened this issue Nov 17, 2017 · 2 comments
Open

vargo new --neon #8

dherman opened this issue Nov 17, 2017 · 2 comments

Comments

@dherman
Copy link
Contributor

dherman commented Nov 17, 2017

I'd like to see a proposal for a command-line flag for vargo new that lets you specify a local path to a local development tree of neon, so that you can easily build neon projects with a custom build or fork of neon. This would be useful in particular for testing.

@nixpulvis
Copy link

nixpulvis commented Nov 17, 2017

I'm a little confused by the naming here. vargo is going to be the new name of the project, then why are we still referencing neon. I'd expect this flag to be called something like --src or --use-local... Maybe I miss-understood, and neon will remain the name of project, and vargo will just be the CLI. Gotta love renaming things 😈

There's also a question of what exactly can be referenced, for example maybe we want to allow [email protected]:<username>/neon.git or other protocols. Food for thought.

@dherman
Copy link
Contributor Author

dherman commented Nov 17, 2017

Maybe I miss-understood, and neon will remain the name of project, and vargo will just be the CLI.

Right. The project is still and will always be neon. vargo is a temporary name for the CLI, until we can get to a point where cargo has enough extension hooks and we don't need a wrapper script at all.

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

No branches or pull requests

2 participants