You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decap CMS docs provide instructions for setting up the Github backend and explains why a netlify site, even if unused for hosting, is necessary for authentication. When providing instructions for this setup the docs direct devs to the Netlify docs (paragraph 3, step 1.). The Netlify docs assume Netlify is the hosting service and so a crucial step is not provided to devs who want to host their site on Github Pages (and I assume other services but I haven't confirmed this) but use Netlify for auth services.
The missing steps are as follows:
Change the CMS site_domain configuration to the domain of the Netlify dummy site
Register your Github Pages' site domain name within Netlify's "Domain Management" settings.
Without these steps your login into Decap on your Github Pages site will result in a "Not Found" message.
The text was updated successfully, but these errors were encountered:
daniel-keller
changed the title
Docs are incomplete when using Netlify for auth but not hosting with github backend
Docs are incomplete when using Netlify for auth but not hosting (using Github Backend)
Jun 7, 2024
Decap CMS docs provide instructions for setting up the Github backend and explains why a netlify site, even if unused for hosting, is necessary for authentication. When providing instructions for this setup the docs direct devs to the Netlify docs (paragraph 3, step 1.). The Netlify docs assume Netlify is the hosting service and so a crucial step is not provided to devs who want to host their site on Github Pages (and I assume other services but I haven't confirmed this) but use Netlify for auth services.
The missing steps are as follows:
Without these steps your login into Decap on your Github Pages site will result in a "Not Found" message.
Sources are the Netlify Discord and this blog post
Could you update the docs to include these steps?
The text was updated successfully, but these errors were encountered: