* Added missing data field to sessions yaml
* rebased sessions.yaml
* Initial commit
* Initial complete guide
* Added LOGGER_LEVELS addition
* Removed redundant VPC cost aspect
* Added login details after deployment
* Minor textual changes
* Made requested changes by @azrikahar
* Changed github repo link from keesvanbemmel to gcp-example in community
* Added Run on Google Cloud button to readme.
Added a link to Cleavr's instructions for deploying Directus to a VPS. Or, if you prefer to have a guide on docs.directus.io, let me know and would be happy to do so.
* Rename API Endpoints docs to Endpoints to align with Hooks
* Add a Creating Extensions page to the docs
* Update individual extension docs pages
* Apply latest changes to hook docs
* Move available events to a dedicated section in hook docs
* move title input up for dividers
* WIP
* simplify key id
* add contrast to notices in field configuration
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* first half of broken links fixed
* next chunk of broken links resolved
* next chunk of urls
* last chunk of links
* one more
* filter rules
* homepage links
* removed localhost
* filter rules for query
* updated links
* relationships link
* changed links from references to glossary
This slightly nicer syntax was introduced back in "npm@6.1.0".
"node@12.20.0", which is the minimum version we require, ships with "npm@6.14.8".
"npm@6" versions below "6.1.0" were never actually shipped with any node version, so it should be very safe to use this syntax.
* Make spinner success message bold in extension cli
* Expose extension-sdk cli functions
* Add create-directus-extension package
* Bump version
* Fix type fun times
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Unique operationIds for users/me methods
* Fix specs for /users/invite/accept and rename files
* Add missing parameters definition for /utils/sort
* Add .yaml to lint-staged and format cmd
* Format .yaml files
* Fix small linting issue
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Add support for _FILE environment variables
* Enhance processing of _FILE env vars
* Same processing as with other env vars (do not simply treat as string)
- tested successfully
* Warn if both variables are set (EXAMPLE and EXAMPLE_FILE)
* Add comments to make it easier to understand the code
* Set newKey only after file read was successful
* Don't convert value > MAX_SAFE_INTEGER to number
Thanks to @skizer!
As stated by @skizer (from #6119):
Altho it seems that we do have a numerical value
it can happen that its outside of Number.MAX_SAFE_INTEGER
thus resulting in a change of the original intended value
e.g oauth -> discord -> client_id
* Fix recursive logger-env import
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
