You are not logged in.
Pages: 1
Thanks, this'll be a handy reference in the meantime!
I started using bigtree a few months back, and it's been great!
The hitch that I ran into was the project structure, the example site was a nice reference but I never found documentation specifically about what to find where or how the project itself was organized.
Does that exist somewhere already? (if not, would it be troublesome to add?)
I'm moving an app from a rails backend to (hopefully) BigTree. The app just needs json and static content, but hosting changes demand php. BigTree has a nice admin interface and cuts out the frills that come with a lot of other CMSes; I'm hoping to use BigTree's admin interface with the already-built front end.
I've got my fingers crossed this is something BigTree can take in stride. Since I don't know the internals too well, some confirmation or direction would be helpful:
Right now my plans are to put BigTree behind `/api` in BigTree's www_root configuration and serve up the app's index page to anything that's not `^/api`
Are the any attendant pitfalls I should watch out for on the BigTree side of things?
Pages: 1