92621429ee
* add docs to eslint
* update prettier ignore
* fix vitepress linting
* eslint ignore fixes
* prettier run
* update prettier ignore
* fix formatting
* enable linting of markdown files
* revert format command change
* fix irregular whitespace
* update dictionary
* (Changelog) Create four-boxes-shake.md
* Rework ESLint / Prettier setup
- Disable js/ts/vue files for Prettier to ensure linting/formatting is
only happening via ESLint
- Rework formatting of code blocks in md files
- Disable formatting of code blocks in md files under '/docs' by Prettier
- Instead use "eslint-plugin-markdown" to format & __lint__ js*/ts*/vue such code blocks
- Replace unmaintained "eslint-plugin-md" plugin by official "eslint-plugin-markdown" plugin
- I'll check whether we can use this to format other code blocks
(json, html, ...) as well
- Restructure, clean-up and apply some fixes to the ESLint config
(Note: Not ready for flat config yet since not supported by
vscode-eslint)
- Enable cache for ESLint / Prettier in scripts
- Clean-up ignore file
- Explicit folder declaration (.../)
- Don't ignore all 'extensions' folders in ESLint (only
'/api/extensions/')
- Enable formatting in '/.github' folder
* Fix all formatting issues with Prettier
* Update md files under /docs/.typedocs
* Fix lint issues in vue/js files
* ESLint / Prettier config revision v2
Enable Prettier for md code blocks, but only as warnings since it can
get into the way with Vitepress md extensions like '[!code ...]'
comments
* Remove prettier-ignore comments
* Make spellchecker happy
* Remove changeset
* Revert lint setup for code blocks
There are many cases in the docs where linting / formatting of code
blocks doesn't make
sense:
- Code block is only an excerpt - linter fails
- Code block contains special comments (e.g. markdown extensions) which
needs to remain at the same place - formatting would break it
- ...
* Apply lint issues / formatting from temp lint setup
* Run formatter
* Fix merge failure
* Simplify & modernize ESLint / Prettier setup
No longer run Prettier via ESLint. Nowadays, this is the recommended
setup. There's no real need to run it this way, it's just an additional
layer.
Add VS Code settings to make the work with the new setup easier.
* Remove unused eslint disable directives
* Make editorconfig more useful
* Fix formatting issues reported by editorconfig
* Format files with Prettier
* Enable formatting of source translations file
* Format source translations file
* Remove unnecessary console error
* Remove unnecessary line
* Only ignore md files under .changeset
* Add CI reporter for Prettier
* Fail job on wrongly formatted files
* Fix format
* Test Prettier action on changed/added file
* Use simple CI format check for now & no cache
* Revert "Test Prettier action on changed/added file"
This reverts commit 4f7d8826ad.
* Introduce code blocks check for docs
* Fix code block issues
* Ignore auto-generated packages dir
* Fix comment position
* Also lint `/app/.storybook`
* Reformat modified files
---------
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
3.0 KiB
description, readTime
| description | readTime |
|---|---|
| Creating an Account is easy and free. Your Account gives you SuperAdmin access to your Teams and Projects on Directus Cloud, enabling you to create and manage Teams, Team Members, Projects, and Project Billing. | 3 min read |
Managing Cloud Accounts
An Account is your portal to Directus Cloud. You can use it to manage your Teams, Team Members, Projects and billing. To avoid confusion, "User" is the term for user profiles in a Directus Project, while the terms "Account" and "Team Member" are used in the context of Directus Cloud. Accounts on Directus Cloud and Users in a Directus Project are two separate systems.
Create Account and Login
Creating an Account is easy and free. As we talked about in the Overview, we've made life easy for you by giving you the option to create and log in to your free Cloud Account automatically with GitHub. If you don't have a GitHub account or prefer not to use this login method, email-and-password login is available, as well. In either case, simply go to the Login Page and follow the prompts.
Manage Account
To update your name or email:
- Click account_circle in the Dashboard Header to enter your Account page.
- Toggle edit to allow edits.
- Change your name and email as desired.
- Click the "Save" button.
Reset Password
To reset your password:
- Click account_circle in the Dashboard Header to enter your Account page.
- Click "Send Reset Link". An email will be sent to reset password.
- Log in to the email associated with your Account.
- Open the email and click "Reset Password". You will be directed to the Password Reset page.
- Reset the password as desired and click "Reset Password".
Destroy Account
To destroy your Directus Cloud Account:
- Click account_circle in the Dashboard Header to enter your Account page.
- Toggle local_fire_department and an input box will appear.
- Type in your password, then click the "Destroy Account" button.
::: danger
Destroying your Account completely removes your Account and data from Directus Cloud. This action is permanent and irreversible. Proceed with caution!
:::
::: tip Must leave all Teams before deleting
You cannot destroy your Account if you are a Member of one or more Teams. Leave all associated Teams before destroying your Account.
:::