Eloquent driver (aka content in DB) vs files for huge project #4716
Unanswered
torian257x
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So we are making a strategic decision whether or not to use files. I was kind of slightly leaning files, just because it's easier to do maintenance.
The project will have, I guess, 10'000 files or more.
Idea was having an integration server, where clients enter content. Once they are done, they can deploy themselves to production. They don't edit anything on production (as there is load balancer).
The files are kept in git. And the plan was, to never have conflicts (that wouldnt be achievable I fear).
so many files, does sound slowwww to me. Like, especially search or other things where you cannot pin point the file.
Other approach would be eloquent driver. Problem is, does not work for everything, nav, globals... forms? we would have to create our own repositories. Would that work though?
is statamic even the right approach, or maybe something else?
Beta Was this translation helpful? Give feedback.
All reactions