Serve the site with `lx serve`

[chriskrycho]

I want to be able to do two things:

• [ ] run the site as a dev server, with live updating of themes and content, for development: lx serve --dev or perhaps lx develop?
• [ ] run the app on a server, watching for changes and republishing accordingly: lx serve

This second is an ancillary goal: I don't need it for this project to work. But there are a lot of potential upsides to that approach, including the ability to just add a piece of content from any location (e.g. with mapped folders, or a web interface, or whatever other approach) and have it updated automatically.

This is probably only 1.0 functionality if I get some help!

[chriskrycho]

cc. @oluseyi

[oluseyi]

We could emulate Node projects and have lx start launch in development, while lx start --production launches a production-ready environment. The choice of verb is open; I'm not particularly enthused about either start or serve.

[chriskrycho]

Your suggestion made me realize there's another option: yarn does a default; lx could too (in this case, serving the site). Worth having on the table, at least.

[oluseyi]

lx strike! 😝

[chriskrycho]

Ooooh, I like the idea of lightning-inspired command names (with clear/obvious aliases).