-
Notifications
You must be signed in to change notification settings - Fork 64
Fn CLI Docs Plan
This document defines the curent plans for the CLI documentation developed by for the Fn project. The structure and parts of the CLI are defined here.
The CLI Documentation will be composed of three parts.
- Fn CLI Help Text Reference (LA)
- Fn CLI How-to (LA)
- Fn Command Reference (TBD)
These Markdown documents will be built from the text ouput of the Fn CLI. Each content page will correspond with the output from a CLI command So for example, each of the following pages would be examples:
- fn --help
- fn init --help
- fn call --help
- and so on.
The pages will follow the same structure as the CLI commands. The Fn command output will at the top of the tree. Commands and subcommands will be linked from here.
The Markdown documents will be built using a tool or a Ruby Script or another kind of script. This is necessary so the building of the pages can be automated and update with each new version of the Fn CLI client.
These Markdown documents will focus on realistic usage examples. The focus will be on tasks and getting things done.
If we decide we need a detailed command reference, this set of documents would be generated from metadata defined in the Fn source code.
The How-to The CLI how-to documentation is organized by tasks.
- fn start
- fn start on different port
- Env var changes required
- fn stop
- fn init and all development commands
- fn run
- Deploy and Create an App locally
- Deploy with Docker Hub
- Call deployed function
- Build, bump, push, test
- List apps, routes, calls
- Create, delete, update
- Set FN_REGISTRY
- Set FN_API_URL
- Using help and CLI
- Create a context
- Set up multiple contexts
- Switch contexts
- Connect to different fn servers