Looks like the API documentation has not been regenerated since 3.0.2, as the maxBodySize value typo is still present here:

https://api.vapor.codes/vapor/latest/Vapor/Structs/NIOServerConfig.html#/s:5Vapor15NIOServerConfigV7defaultACSS8hostname_Si4portSi7backlogSi11workerCountSi11maxBodySizeSb12reuseAddressSb10tcpNoDelaytFZ

Right now the Docs only explain how to set up Fluent inside your Vapor application, the docs should also contains explanation of using Fluent without Vapor apps, so you can use it for general ORM purposes too

Please add a checkboxes to mark constraint as correct. It' ll help to figure out the problem whet there are more than 15 constrains

We'll want to write a document outlining some major changes from Redis 3 -> Redis 4, with an overview of how some of the commands are now done (zadd comes to mind)

I don't have a clear understanding of the usage of $ with with Fluent's property wrappers. It'd be nice if an explanation of this were added to both the "Fluent - Overview" and "Upgrading - Fluent" sections of the docs.

I know we're early in the docs process, but I wanted to point it out. If someone can explain it quickly or point me in the right direction to gain an understanding I'd be hap

https://apple.github.io/swift-nio/docs/current/NIO/Classes/ClientBootstrap.html mentions:

Usually you re-use a ClientBootstrap once you set it up and called connect multiple times on it. This way you ensure that the same EventLoops will be shared across all your connections.

HTTPClient is tied to an event loop, so this should be possible.

Running the command line vapor-beta update results in an error due to no longer intentionally existing.

Steps to reproduce

Run vapor-beta update command line

Expected behavior

Output a nicer error message stating the preference of using swift package update instead compared to the usage of vapor update within Vapor 3.

Actual behavior

Outputs an unfriendly error m

Event list under the http://www.swifttube.co/events should be sorted by "startDate" of the events. Newest event should be listed at the top of the list.

Writing unit tests with Vapor with nio has changed and it would be helpful to include an example of how this is to be done for those starting with a new project.