A GraphQL API for Binda CMS.

Binda is a headless CMS with an intuitive out-of-the-box interface which makes very easy creating application infrastructures. For more info about Binda structure please visit the official documentation

Install Binda APi via terminal

gem install binda-api

alternatively add the gem to your application's Gemfile:

gem 'binda-api'

Then execute:

bundle install

Setup database credentials and create a database.

To complete Binda installation run the installer from terminal. Binda will take you through a short configuration process where you will setup the first user and some basic details.

rails generate binda:install

Master version only: run rails generate binda:api:install after having installed Binda.

Now you are good to go. Good job!

We don't want everything stored inside Binda database to be accessible via API: there might be phone numbers, email addresses, credentials for external services that need to be secret and unaccessible. Binda API is only accessible for admin created users, each one with an API KEY and a specific set of accessible contents.

Binda API is based on GraphQL. A valid API KEY must be sent along every request.

Here below an example of a simple query that retrives the name of all post components using Axios library.

axios
	.post(
		"http://my.domain.com/graphql",
		{ api_key: "SECRET-API-KEY", query: "{ components(slug: \"post\"){ edges { node { name } } }}" },
		{ headers: { "Content-Type": "application/json" } }
	)
	.then(response => response.data)
	.catch(error => {
		throw error;
	})

This is one of the possible approaces to access Binda content with GraphQL. Feel free to make requests to GraphQL as you prefer.

Binda API documentation is integrated in the GraphiQL panel which is accessible from /admin_panel/graphiql. In your local environment this would be http://localhost:3000/admin_panel/graphiql (if you use port 3000). Since you can't customize request parameters, you should send the API KEY using the QUERY VARIABLES panel like this:

{ "api_key": "SECRET-API-KEY" }

If Binda is using a CDN to store all assets you should already receive a proper absolute URL. If insted you are storing assets inside public folder (see Carrierwave documentation) Binda API will give you a relative path.

You can fix this issue modify few lines of the CMS application on which Binda is installed.

Set a environmental variable BINDA_ASSET_HOST with your app domain

BINDA_ASSET_HOST=http://your.domain.com

Add this line to config/environments/production.rb (or to development.rb if you are in a development environment)

config.action_controller.asset_host = ENV['BINDA_ASSET_HOST']

Add also this line to config/initializers/carrierwave.rb

config.asset_host = ActionController::Base.asset_host

If you are setting up a Rails application with Binda API, but you don't want it to handle your frontend interface, then might be useful to redirect the / route to admin_panel which is the entry point where the login page is.

To achieve this behaviour add the following line to config/routes.rb

root to: redirect('/admin_panel')

IMPORTANT: don't delete/modify the following file spec/test_app/migrate/00000000000000_create_binda_tables.binda.rb

If you are testing and you want to submit a PR be aware that Travis (which is responsible for the test validation) will complain if you have a duplicated migrations. To avoid this problem run the following command from the gem root:

rm spec/test_app/migrate/*_create_binda_api_tables.rb

If you need to update a migration run the following command:

rm spec/test_app/migrate/*_create_binda_api_tables.rb
cd spec/test_app
rails generate binda:api:install