If netlify isn't going this route by default then it seems everything could all be packaged up with netlify, meaning a single repo gives you everything required, while side-stepping the default api.netlify.com lock-in.
Throwing everything into a directory then adding a route to look for it in this directory isn't too bad an approach. config.yml could be made to live outside this directory, while index.html too could live in the root as it requires customisation.
Then you can clone this repo, run a task, be up and running with your own front and backend.
If netlify isn't going this route by default then it seems everything could all be packaged up with netlify, meaning a single repo gives you everything required, while side-stepping the default
api.netlify.com
lock-in.Throwing everything into a directory then adding a route to look for it in this directory isn't too bad an approach.
config.yml
could be made to live outside this directory, whileindex.html
too could live in the root as it requires customisation.Then you can clone this repo, run a task, be up and running with your own front and backend.