You have my vote. A feature like this will certainly attract ‘hardcode’ developers who don’t like pretty user interfaces. At the moment I have a hard time convincing back-end developers to migrate, whereas Front-End devs are easily convinced thanks to Local’s attractive design.
I think @alexclst is on the right track with lbf start etc. commands…
Something like lbf new to create a new site, the user would then be presented with options, i.e. title, directory, server type, php/mysql versions, multisite etc… Have a look at how Lando does it - https://docs.devwithlando.io/
Some commands:
-
lbf new- Create site -
lbf start- Start site -
lbf stop- Turn site off -
lbf status- Check run status of site -
lbf remove- Delete site, also presented with confirmation, and option to remove files from dir. -
lbf edit- Update server, php or mysql options -
lbf update core- Update WordPress -
lbf update plugins- Update All Plugins -
lbf update plugin contact-form-7- Update specific plugin, i.e. “contact-form-7” (directory slug) -
lbf update themes- Update All Themes -
lbf update theme twentyseventeen- Update specific theme, i.e. “twentyseventeen” (directory slug) -
lbf update all- Update WordPress, plugins and themes -
lbf mysql- Open database in preffered tool (i.e. Sequel Pro) -
lbf mail- Open MailCatcher -
lbf push- Push to Flywheel (presented with option for database) -
lbf pull- Pull from Flywheel (presented with option for database) -
lbf export- Zip and export site -
lbf import- Import site
Just some examples…