✨ Shared Environment - Provide copyable environment configuration for Tina-docs

[ssw-yakshaver]

Requested by: @isaaclombardssw via YakShaver.ai 🦬
cc: @isaaclombardssw, @Calinator444, @Marxoz, @joshbermanssw

Hi Team!

  🟥  Watch the video (2 min 5 sec)

Pain

Create a shared, copyable environment configuration for internal developers working on Tina-docs. This should include required environment variables (e.g., GitHub token and TinaCloud settings) so developers can quickly run the project locally after cloning/F5, avoid GitHub rate limits when fetching commit metadata, and align with the configuration used in Vercel. Public contributors may run with the feature disabled or supply their own credentials.

Acceptance Criteria

1. A shared location exists (e.g., env template file or secure store reference) with all required environment variables for Tina-docs.
2. The configuration includes a GitHub token used for fetching commit data to display last-updated information.
3. The configuration includes required TinaCloud environment variables.
4. Internal developers can copy the environment configuration and run Tina-docs locally without GitHub rate limiting.
5. Sensitive values are stored securely (e.g., Keeper) and not committed to the repository.
6. Documentation clearly states that the provided configuration is for internal developers only and that public contributors must provide their own credentials or run with the feature disabled.
7. The setup aligns with the existing Vercel environment variables used by the tina GitHub account.