Merry Xmas and a Happy New Year in advance, my dear friends!
Reading the various posts in the forum, I wondered so many times why the poster wanted to use the app-advanced template, while the app-basic template looks quite appropriate for his/her current project. Sometimes it looks to me that he/she is only making things complicated and tough by adopting the app-advanced template, especially when he/she is going to deploy both the front-end and the back-end apps to a shared hosting service. It doesn’t make sense.
There seems to be too many people with relatively less skill and less resource who try to use the app-advanced template only to lay an unnecessary burden to themselves.
I think we have to clear up some misunderstandings about the app-basic and the app-advanced templates.
1. The app-basic is only for the front-end.
They seem to have a misunderstanding that the app-basic can not have administrative pages, thinking that we need to use the app-advanced when we need some administrative sections.
But it’s not true, of course.
By constructing an appropriate RBAC structure, it’s fairly easy to have the administrative pages that can only be accessed by the administrators of the system along with the front-end pages for the ordinary users.
We may also have a separated administrative module for the administrators in the app-basic template.
2. The app-advanced can easily be deployed to a shared hosting service.
I have to admit it is possible to use the app-advanced template for a shared hosting environment. The document also describes how to do it.
But the modification of the app-advanced template for a shared hosting service is not very simple and easy. IMO it’s so tricky and twisted that no one with a common sense would not like to try. And it’s less efficient than the app-basic for a shared hosting.
I’d like to hear what you think about it, my dear friends.