Document using database-driven backends

[ramkumarkb]

- Do you want to request a feature or report a bug?
Feature

- What is the current behavior?
Only Git based backend repo like GitHub, GitLab, or Bitbucket is supported

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?
It will be fantastic if there are some pointers to create a custom backend with S3 compatible storage like Minio

• There seems to be a prior discussion in Question: Would writing a backend for PostgREST be feasible? decap-cms#616
• Another related discussion on a PR File System API (Final On-Hold) See Comments decap-cms#786
• But with v2.0, will the customization be isolated to a particular package? Any pointers or tips would be really useful. Thank you !

[talves]

@ramkumarkb this is very possible. I have written a backend for the file-system that allows for a registering in backend. I have also written a backend to connect to Firebase/Firestore which I have to convert to an open-source project.

As I write this, there is not an official starter for creating a backend. The best way to get started is to create a library and use one of the existing backends in the packages as an example of the Class and Methods you need. Also make sure to add your class to global scope, so you can register it as a backend in the cms.

[snoopdouglas]

Putting things straight into an S3 bucket would be very useful, as we already have a CDN for ours, so would prefer to keep uploads together with our other sites rather than opening eg. a Cloudinary account. So... bump

[erquhart]

The comment by @talves explains that this is already possible.

@talves should we close this? Or maybe leave it open until there's something in the docs about creating custom backends?

[talves]

My first inclination was to close it, since the netlify-cms wouldn't have an official S3 backend. I then felt the same way as you, maybe wait until the backend API is out of beta and documentation is complete.

[erquhart]

Just for posterity, the only reason we're avoiding a database driven backend is that we're 100% focused on Git based content management with Netlify CMS. Agreed on leaving open for docs 👍

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.