---

What's the difference between Tina Cloud and TinaCMS?

TinaCMS is an open source toolkit that enables developers to create a live editing experience on their site.

Tina Cloud adds a GraphQL API to Tina's open-source content editor allowing it to read and write content stored in your Github repository (ie. Markdown and soon JSON). It also grants authorization for other users (content creators, editors, marketers, etc) to login and edit their site without needing to grant direct access to the repository in GitHub

Where do I start?

• Have a look at the updated Tina Cloud docs and try out a starter.
• Sign up for Tina Cloud!
• Find us on Discord

Does Tina Cloud only work with GitHub repositories?

Currently, yes, the first Git provider that Tina Cloud integrates with is GitHub. Other Git providers may be available in the future.

How can I share an idea or get help using Tina Cloud?

• If you haven't checked yet, the docs may have the answer you are looking for!
• Connect with us on Discord.
• We can help you at support@tina.io. Email us if you would like to schedule a chat!
• Chat with us from your Tina Cloud dashboard (there's a chat widget on the bottom right of the browser window).

What is the pricing for Tina Cloud?

There will be no cost for small teams to use Tina Cloud while it is in Beta.

A fair use policy will be coming soon.

We will contact you if we believe your use case may eventually fit within our post-beta paid plans.

Does Tina Cloud work with Monorepos?

It does! Tina Cloud can work with sites inside monorepos by specifying the path to your tina folder in your Project configuration.

If your repo is not a monorepo, there's no need to do any configuration. We'll expect your tina folder at the root of your repo.

Here's an example monorepo structure that works with Tina Cloud:

/projects/site-a /projects/site-b /projects/site-c

See Path To Tina for more information.

How do I resolve the Unable to find record 'tina/__generated__/_graphql.json' error?

Tina Cloud's GraphQL API returns this error when it cannot find a file in your GitHub repository. This may occur under the following circumstances:

• The tina folder (and __generated__ subfolder) is not in your GitHub repository remote.
  • If the folder is in your local repository, but not in your remote, make sure there isn't a .gitignore file excluding it.
• Tina is configured with a branch that doesn't exist or a branch that doesn't contain the tina folder.
  • The referenced branch should be created and should contain the tina folder.
• The apiURL prop is misconfigured on the TinaCMS component.
  • Check the apiURL and make sure it looks like https://content.tinajs.io/content/{tina_client_id}/github/{branch} where {tina_client_id} matches the Client ID on the Project in Tina Cloud and {branch} is a valid branch.

Tina.io login window doesn't close when logging in from a site

When a user logs in from your site, we will pop open a login window. When login is complete, we will attempt to send a message back to the main window.

The most common reasons for this issue are:

• The Site URL is not properly set for the Tina project. The main window's base URL will need to match the Tina project's Site URL setup in the Tina Cloud Dashboard.
• The Client ID setup in your site's environment variables does not match the Client ID in your project's settings on the Tina Cloud dashboard.
• The user attempting to login to Tina Cloud does not have access to edit this site. Ensure that this user is authorized on the Tina Cloud dashboard.

Make sure to include https in the Site URL eg: https://forestry.io or if you are testing locally, it might be something like http://localhost:3000

How do I resolve "The local GraphQL schema doesn't match the remote GraphQL schema." errors?

If you are getting this error in your build logs, it means that the tina/tina-lock.json in your deployed site doesn't match the version that is in Tina Cloud. To resolve it, make sure you have latest versions of @tinacms/cli and tinacms in your project, and then run the dev command locally. Commit any changes to the tina/tina-lock.json and push those to the git repository linked in Tina Cloud.

If you are getting this error when access the TinaCMS interface, it can be caused by a mismatch between the version of tinacms and @tinacms/cli on the project. Update both dependencies to the latest versions and run the dev command locally. Commit any changes to the tina/tina-lock.json and push those to the git repository linked in Tina Cloud.

How do I resolve errors caused by unindexed branches?

If you receive an error like The specified branch, 'my-branch-name', has not been indexed by Tina Cloud, first verify that the correct branch has been specified in the config properties passed to defineConfig in tina/config.ts. Note, that this value may be set as an environment variable in your CI build process. Second, verify that the branch exists in the GitHub repository. Lastly, you can force a reindexing of a particular branch by making a whitespace change to the tina/tina-lock.json file in that branch, commit the change, and push it to GitHub. This will initiate indexing for the branch and (after a few minutes) the error should be resolved.

How do I resolve "Failed loading TinaCMS assets" error

This error means that the TinaCMS admin HTML file failed to load the JavaScript bundle. This generally happens for a few reasons:

User has pushed the development admin/index.html to production

When you run tinacms dev locally, Tina will generate a development admin/index.html file, which loads its assets from localhost. For production, this file should be built in CI using tinacms build. If a developer manually removes the admin/index.html file from their .gitignore, they may run into this issue.

Site is building on a sub-path

A known limitation is that tinacms doesn't load assets correctly when the admin is deployed to a subpath: (e.g: https://jamespohalloran.github.io/my-site-root/admin/). We have an incoming update to support this use-case.

Last Edited: January 24, 2022