docs: use api_token option in crowdin configuration file

[mpfeil]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

I was following the Crowdin internationalization guide and configured the crowdin.yml as described.
Running npm run crowdin upload results in the following error.

Test Plan

I have checked the crowdin.yml configuration file reference and found that the personal access token must be passed by using api_token.

"api_token": "personal-access-token"          #open profile settings and go to API > New Token > create Token

A simple configuration can be found here.

This was tested with crowdin cli version: 3.7.8

Test links

Crowdin.yml reference: https://support.crowdin.com/configuration-file/
Deploy preview: https://deploy-preview-7413--docusaurus-2.netlify.app/

Related issues/PRs

[facebook-github-bot]

Hi @mpfeil!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	ab3d338
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/627e52f3bd2a2e000966cfc0
😎 Deploy Preview	https://deploy-preview-7413--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟢 95	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 88	🟢 99	🟢 100	🟢 100	🟢 90	Report

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[slorber]

Hi

You can use both

• api_token for hardcoded value
• api_token_env for env variable name to read

https://support.crowdin.com/configuration-file/#api-credentials-from-environment-variables

https://docusaurus.io/docs/i18n/crowdin#access-token

It is not very recommended to commit secrets to Git so we document the usage of an env variable for security reasons.

Now if you want to hardcode and commit the secret to your repo, you can still do it, but we don't really want to recommend that the default