Sergio Benitez

@hiimtaylorjones I'd love the help! I imagine that such a section would be composed of at least two subsections: 1. Deploying on a VPS (using NGINX as a reverse proxy)...

Note: This only applies to unreleased versions of Rocket, notably, the `master` and `async` branches.

I've opened https://github.com/rust-lang/rfcs/pull/2968, which would allow us to resolve this issue on stable. Edit: For posterity, besides the issue of identifying lifetimes, the `type` alias proposal and any like it...

Unfortunately, I don't see this as resolvable without support from `rustc` or an entirely new approach to `uri!`. Given that the error message emitted points to a resolution (i.e, import...

Alright, I think I have a solution. First, we add the following `impl`s to `http`: `Ignored`, which can be converted into _any_ `Ignorable` URI parameter type: ```rust pub struct Ignored;...

@edgarogh's response is exactly right. This is a doc bug. The string should be updated to reflect what @edgarogh has commented.

@piperRyan Sure, that would be great! Before you start writing code, please post a detailed description of your design plans. In particular, you should address how you're going to tackle...

@piperRyan Thanks for the write-up! > Leverage hyperlocal 0.3.0 which uses 0.10.3 hyper. Downside of using this that no logging can be added to it. Maybe it would work as...

> * We will probably want users to be able to use their own documentation format: be it OpenAPI, or RAML, or something custom. How do we allow users to...

> > The different files for the different impls are unnecessary > > Gone > > > we should start with structures that are able to describe the entirety of...