Package: plumber2 0.2.0.9000

Handlers | Handler methods | Paths | Path parameters | Path wildcard | Path priority | Handler input | Handler arguments | query | body | request | Cookies | Headers | response | server | client_id | Type casting input | Defaults | Required parameters | Static File Handler

The _server.yml file | Creating a _server.yml file | Testing your _server.yml file | Posit Connect | DigitalOcean | Prerequisites | Basic Deployment | Learn More | Docker | Choosing a Base Image | System Dependencies | Example Dockerfile | pm2 | Setting up pm2 for plumber2 | Starting Your API with pm2 | Managing Your API | Running Multiple Instances | Automatic Startup on Boot | Using an Ecosystem File | Monitoring and Logs | systemd | Creating a systemd Service | Setting Up Your Application | Managing the Service | Viewing Logs | Service Management Commands

Annotations | Annotation settings | Use roxygen prefix | Annotations example | Equivalent programmatic usage | Specifying route name | Specifying route order | Specifying root url for the whole file | Global annotations | Handler annotations | Endpoint | More details on Type | Asset annotation | Equivalent programmatic usage (note that argument order is reversed) | Auth guard annotation | Datastore annotation | plumber2 annotation | Forwards and redirects | Annotation example | Shiny | Reports

What does it mean to extend plumber2 | Adding new tags | Tag registration | New block type | Existing block type | apply_plumber2_block methods | Single main class | Subclass | Adding a programmatic interface | New parsers, serializers, and async engines | Serializers | Graphics output | Parsers | Asynchronous engines | The Plumber2 object and its extension points

Traces | Subtraces | Metrics | Logs

Specifying the Inputs | Customizing The Output

The Response Object | Serializers | Standard serializers | Boxed vs Unboxed JSON | Graphics serializers | Bypassing Serialization | Custom serializers | Error Handling | Setting Cookies | Setting Unencrypted Cookies | Setting Encrypted Cookies | Documenting responses

Networking & Firewalls | HTTPS | Denial Of Service (DoS) | Sanitization & Injection | Security Headers | Cross-Origin Resource Sharing (CORS) | Resource Isolation Policies | Cookies

The standard | The _server.yml file | The engine | The server | Recommendations for _server.yml engines | File paths | Options | Case study: plumber2 | YAML content | launch_server() | Supported frameworks

Execution Model | Environments | Performance & Request Processing | Managing State | In-Memory | File System | Cookies | External Data Store | Exit Handlers

Web APIs

Creating and Controlling routers | Defining handlers | Listening for and triggering events | Static File Routers

Debugging | Print Debugging | Router Stage Debugging | Interactive Debugging | Port Range

Moving from plumber | pr_*() to api_*() | Only path arguments are passed as named arguments to your handler | No more filter and preempt | forward replaced by Next and Break | New Request and Response objects | New Plumber object | Added @query and @body tags