That's really good to hear Fabien. The thought had occurred to me of
only having one application, but my mind (and I'm assuming everyone
elses minds) were still lingering in the symfony 1.4 mindset of
multiple apps within projects. This clears a lot up and probably saved
us a lot of pain down the r
ApiFrontend and ApiBackend ?
No, I'm kidding
You could have an administration controller in your application, who
requires some credentials to be accessed, and renders different
templates from the frontend controllers.
You could prefix them with your applicative layer : adminController,
ap
On 8/11/10 9:08 PM, Jay wrote:
Each app has different auth requirements and possibly different
configurations. Isn't that why in most of the tutorials you speak of a
"Frontend" app, which kind of implies that there would also be a
"Backend" app? And then if we were to build an api that api might
With option b) we would probably put all the article bundles into
their own directory to be a bit more organized:
Bundle\Article\FrontendArticleBundle
Bundle\Article\BackendArticleBundle
Bundle\Article\ApiArticleBundle
Bundle\Article\CommonArticleBundle
with option b you end up with up to 4 routi
Each app has different auth requirements and possibly different
configurations. Isn't that why in most of the tutorials you speak of a
"Frontend" app, which kind of implies that there would also be a
"Backend" app? And then if we were to build an api that api might have
special auth to deal with va
