The ./flitter Command

Documentation has moved.

The documentation for Flitter has moved. You probably want to be here:

By default, Flitter ships with the flitter-cli package, which enables use of the ./flitter command. This command is designed to aid development on Flitter. This command should only be run from the root of the application, as it depends on relative paths.

Launch a Development Server
./flitter up

While not designed for use in production, ./flitter can start a Flitter server quickly for testing your app.

Run a Deployment
./flitter deploy <deployment name>

Flitter units can define special functions called deployments. These deployments are designed to be one-time, non-reversible functions that set up the unit's necessary files and configuration, etc. For example, the flitter-auth package provides the auth deployment which creates the controllers, models, views, and middleware to enable flitter-auth.

Create a New File From a Template
./flitter new <template name> <file name>

Flitter units can also define templates for files that are used regularly in Flitter. For example, libflitter provides several templates like the controller template, which creates a new controller with the given <file name> in the base controllers/ directory.

Launch the Flitter Shell
./flitter shell

Sometimes, when you're developing a feature for your app, it's useful to be able to test things out and interact with Flitter directly, without having to interact with Flitter through a web-browser. As such, this command will start an interactive prompt that has access to the entire Flitter context. It behaves just like an interactive Node prompt, but it is started from within Flitter, so you can access all the same resources that your app can directly.

Revision #3
Created Sat, Mar 2, 2019 2:27 AM by Garrett Mills
Updated Fri, Apr 19, 2019 12:59 PM by Garrett Mills