* Update queues.md
- adds a warning about trying to scheduled jobs outside of boot up
* Update docs/advanced/queues.md
---------
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
* Make custom Leaf tag examples complete
As reported in [vapor/vapor#2942](https://github.com/vapor/vapor/issues/2942), UnsafeUnescapedLeafTag is going unnoticed.
To bring more attention to it, I moved the tip to the top section in all languages, updated the HelloTag to use the protocol (since it was rendering garbage since the LeafKit update).
Plus, all the code samples are now directly copiable, as they have a common structure and indentation.
* Hardcode RediStack 1.3.2 doc URLs to fix dead links
* WIP: Add docs for deployment on Fly
* Fix typo
* Add Fly to mkdocs.yml
* Remove trailing newlines
* Replace "We recommend" with "It is recommended"
* Remove "managed"
Fly doesn't describe the DBs as such and they aren't as much "managed" as other platforms currently
* Change config.swift to configure.swift
* Fix typos and improve wording
* Improve last section
* Explain how to find the name of the Postgres app
* Replace "This command" by a clearer reference
* Clarity: Change tense to present
* Improve the last sentence
* Improve last sentence again
* Various improvements
* Apply changes from feedback of @BennyDeBock and @0xTim
* Add details about the possibility of using other types of databases
* Converts quotes to special !!! syntax and mention fly secrets import
* Also mention how to create a template from GitHub templates based on @BennyDeBock suggestion
* Apply suggestions from code review
* Switch toolbox and templates
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
* Use of regular expressions for MongoDB
The API allows to create a Document with a regular expression to query for items, but there's no documentation about it.
Ideally the key "name" is created using FieldKey.makeMongoKey(), but the extension is internal, so we must hardcode it for now.
* Apply suggestions from code review
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
* Add release notes
* Add bash instructions to insert into release-notes
* change package name
* Add all packages with releases to the release-notes file