This forum has moved to a new location and is in read-only mode. Please visit talk.octobercms.com to access the new location.

gavin13433
gavin13433

I would like October to pull as much data as possible from an external API. I want a dedicated (non-October) API framework to serve my data, using REST, RPC, DDP, or GraphQL.

I do realize October, and most other CMSs, want to pull data from a relational database. Even so, I'd really prefer to have a dedicated API framework serving this application data, whenever possible. At the same time, I love the Backend, Plugin, Theme structure of October. I want to be able to combine both of these worlds.

For instance, I would want to store as much config data for APIs in YAML files. I have multiple clients (and I have many co-workers), and I want a October + External API project structure which is consistent across many distinct projects.

Does anyone have advice for dividing an application into October + External API?

Vojta Svoboda

1-2 of 2

You cannot edit posts or make replies: the forum has moved to talk.octobercms.com.