mirror of
https://github.com/directus/directus.git
synced 2026-02-02 11:35:11 -05:00
* Add Quickstart Guide * Update installation * Remove unused files * Update support/backing * Tweaks in concepts * Setup file structure for API reference 2.0 * Setup page layout for reference * Add clean-urls plugin * getting started updates * Finish authentication rest * getting started updates * Render stylus in 2 spaces * Various * Various * Finish activity docs * Add collections reference * Add extension reference * concepts updates * Fields/tweaks * Add files doc * Add revisions * concepts docs * More api reference * Finish rest api reference (finally) * initial concepts * More things * Add assets api ref * Move sections from file to assets * Add environment variables * contributing docs * Add field transforms page * Left align table headers * concept links * Add API config * Fix mobile nav * Add migrating a project * doc link fixes Co-authored-by: Ben Haynes <ben@rngr.org>
488 B
488 B
Accessing Data
TK
Storing Sensitive Extension Variables
If your extension requires storing sensitive data, such as an API Key, you can store that information in custom environment variables. This data can then be accessed globally by server-side extensions (eg: custom hooks or endpoints). If you need access to that private data on the client-side (eg: custom interfaces or displays), then you would expose that env variable via a custom endpoint with proper limitations.