Open allthesignals opened 6 years ago
The idea is very similar to what vue does: ember-cli-create --preset gossi/my-preset
or ember-cli-create --preset gitlab:gossi/my-private-preset
. So companies can host their own presets and are good to go. Gists can also be supported.
The hard part would be to set the schema for the preset file. Also vue does a very good job here, which can be taken as inspiration/base work.
PS. I hate environment variables, that's why I create this project :p
The idea is very similar to what vue does:
ember-cli-create --preset gossi/my-preset
orember-cli-create --preset gitlab:gossi/my-private-preset
. So companies can host their own presets and are good to go. Gists can also be supported.
Beautiful!
The hard part would be to set the schema for the preset file. Also vue does a very good job here, which can be taken as inspiration/base work.
I'd love to take a look. This seems very interesting. Could also inspire a future PR into ember-cli
, which I understand does not support this kind of functionality.
PS. I hate environment variables, that's why I create this project :p
Ditto!
It also requires a deeper look at blueprints, as they might be extendable. It's more of a research project towards a preset schema.
This would be great for small teams. I'm not sure what this would look like, though. A few possibilities:
ember-cli-create
could look at an environment variable when it installs. This could be a comma-separated list of addon names.ember-cli-create
could allow one to point to a person/team's Github fork ofember-cli-create
which prefers that fork's own list of addons to include.