* Create heroku.md file
This is basically the same file from the 3.0 docs, which worked well to me to start the heroku app. Just did the needed changes to work with 4.0.
* Docs 4.0: Update mkdocs.yml
* Apply suggestions from code review
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
* Provide `ResponseEncodable` example in content.md
I wasn't able to find any documentation on how to tweak `Content-Type` header for custom response types. An example of this is added to `content.md`, which seems to fit this topic the most.
* Make HTTPHeaders reference URL HTTPS
The existing code to add MongoDB's driver didn't work because of an extra name and incomplete version on the .product().
```
Error: Could not generate Xcode project: 'hello' /Users/mgomez/Developer/Swift/TrailBucket/hello: error: declared name 'FluentMongoDriver' for package dependency 'https://github.com/vapor/fluent-mongo-driver.git' does not match the actual package name 'fluent-mongo-driver'
```
```
error: because no versions of fluent-mongo-driver match the requirement 1.0.0..<2.0.0 and root depends on fluent-mongo-driver 1.0.0..<2.0.0, version solving failed.
```
The `try_files` directive should be within a `location` block, and is
so in all example uses of `try_files` in the nginx documentation at
http://nginx.org/en/docs/http/ngx_http_core_module.html#try_files.
It is however curious that the nginx docs seem to indicate that
`try_files` can operate in either the server or location context, but
no examples show that use case.
Signed-off-by: zach wick <zach@zachwick.com>
Fixes#463
The 'trace' level of logging is the least severe level of logging in SwiftLog
and should be used only when tracing the execution flow of a program during
debugging.
This description of the 'trace' level of logging, is verbatim the description
of the 'trace' level in the SwiftLog documentation at
74d7b91cee/Sources/Logging/Logging.swift (L327)
and I will file a bug report and PR there in the upstream project.
Signed-off-by: zach wick <zach@zachwick.com>
* Fix typo in CreateStarTag migration
A bigger change would be to change the examples to use the static schema property of the model. That should probably be done for the whole file though.
* fix tag reference in StarTag example
* Add Repository pattern to "upgrading"
This adds documentation on how to use the repository pattern in Vapor 4 compared to Vapor 3. This fixes#446
* fix spacing
* indentation fix
* change diff
* Add documentation for Docker deploys.
* fill in some holes
* Address PR feedback.
* Apply suggestions from code review
Co-Authored-By: Jimmy McDermott <mcdappdev@gmail.com>
* prefer 'development machine' over 'developer machine'
* minor phrasing tweak
* Address PR feedback.
Co-authored-by: Jimmy McDermott <mcdappdev@gmail.com>