Thanks David,

> I think your best bet is to serve your static content via a front-end web
> server (I use Nginx) and route all the app-related requests to your
> container.

I was trying to avoid that for this project. Back to using /content/
for everything static.  Nginx is a great suggestion for this, thanks!


-Grant

On Aug 22, 8:48 pm, David Pollak <[email protected]>
wrote:
> On Sat, Aug 22, 2009 at 4:51 PM, Grant Wood <[email protected]> wrote:
>
> > How can I tell a Lift app to use an alternate webroot (holding all my
> > html, static templates, images, etc)?  Essentially, I want my
> > application to look in a folder of my choosing for content, rather
> > than in the webapp directory as it does by default.
>
> > I can't be the only person who has to manage/deploy content in a
> > separate process and system than the application,
>
> I think you're the first person that has asked for this.
>
> > so there is likely a
> > simple LiftRule I can override in Boot.scala to use content in a
> > location other than the war.
>
> I think this might be impossible (or at least very, very difficult.)
>  Mapping from resources contained in the WAR file into the application space
> is not defined by any spec that I know of and varies on a container by
> container basis.
>
> I think your best bet is to serve your static content via a front-end web
> server (I use Nginx) and route all the app-related requests to your
> container.
>
> > However, digging through the
> > documentation, discussions, and code (LiftServlet, LiftRules, etc.) I
> > don't see an obvious entry point.
>
> > Thank you for your help!
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to