Like we discussed in the Slack, it'd be great to have a vulcan start command that could be used instead of meteor, meteor run, or the current npm start (which is equivalent to meteor --settings settings.json).
In addition to the --settings flag, it'd be great to use the package_dirs variable to set up local package development.
Maybe when the user sets up the command line for the first time (or creates their first Vulcan project), they could be prompted with something like where would you like to store VulcanJS packages for local development? (default: ~/VulcanJS)?
Once this is done, we'll be able to split the repo in two: VulcanJS/Starter, which will contain the examples but not packages, and VulcanJS/Vulcan which only contains packages (and no .meteor directory). This should make getting started a lot easier without making it too hard to access Vulcan core code either.
Like we discussed in the Slack, it'd be great to have a
vulcan startcommand that could be used instead ofmeteor,meteor run, or the currentnpm start(which is equivalent tometeor --settings settings.json).In addition to the
--settingsflag, it'd be great to use the package_dirs variable to set up local package development.Maybe when the user sets up the command line for the first time (or creates their first Vulcan project), they could be prompted with something like
where would you like to store VulcanJS packages for local development? (default: ~/VulcanJS)?Once this is done, we'll be able to split the repo in two: VulcanJS/Starter, which will contain the examples but not packages, and VulcanJS/Vulcan which only contains packages (and no
.meteordirectory). This should make getting started a lot easier without making it too hard to access Vulcan core code either.