This is a document where contributors can plan and brainstorm ideas for eecli.
- run act from
Not sure if it does this but for the GitHub adder make sure it installs third party modules to correct folders?- check for merge conflicts before pushing part of the deploy script reference: http://stackoverflow.com/questions/3065650/whats-the-simplest-way-to-git-a-list-of-conflicted-files
- eecli deploy. Runs envoy or ansible whatever is specified. Pass in parameters, like -staging, or whatever. Other commands can go in eecli config file. Instead of running deploy tasks and calling eecli, run eecli deploy and call in deploy task
delete entry --name test or even pass in regex- delete channel etc
- eecli report : pass in SQL. Option for csv even.
- eecli analyze/ eecli doctor Tells about entries, and basic EE setup. Inspiration here is brew doctor. For instance: Entry id with conflicting entries. entry id 1234 in channel titles is in channel 10, but in channel data is in channel 8 Cats mis assigned. Cats not existing. Bad status. Duplicate URL titles.
Better doc wiki setup than readme better docs? Too many commands already- eecli Clone? Mimic mx cloner to clone entry
- interface with aws cli to run commands and hook in assets?
- Continuing above thought eecli to call assets? Paid license issues?
Automatically find out what the system folder is and on eecli init add that in automatically. Use something similar to the handlebars functionality in the generate add on command- create:field:text (start with just text fieldtype support)
- create:low_variable:text (start with just text fieldtype support)
- delete:channel
- delete:category
- delete:category_group
- delete:member
- delete:member_group
- delete:field_group
- delete:field
- delete:status
- delete:status_group