[racket] Serving static content

I recommend using Racket behind some static server. The docs have a
FAQ entry about setting this up with Apache:

http://docs.racket-lang.org/web-server-internal/Troubleshooting_and_Tips.html#%28part._.How_do_.I_use_.Apache_with_the_.Racket_.Web_.Server_%29

Jay

On Fri, Mar 20, 2015 at 3:21 AM, Alexis King <lexi.lambda at gmail.com> wrote:
> I’m interested in creating a web application, and I plan to write the front-end in ordinary JavaScript and HTML. A large portion of the content served will just be static HTML, JavaScript, and CSS.
>
> I plan to interact with the server via a standard JSON API and WebSockets, both of which I’m interested in developing in Racket. That said, does it make any sense to use the Racket web server to serve purely static content? Would it be more worth my time to use a more traditional server infrastructure for the caching and content handling?
>
> Either way, is there a good method for serving static content via the Racket web server? Is there anything I should know to get the best performance if I did plan to go that route?
>
> Thanks,
> Alexis
> ____________________
>   Racket Users list:
>   http://lists.racket-lang.org/users



-- 
Jay McCarthy
http://jeapostrophe.github.io

           "Wherefore, be not weary in well-doing,
      for ye are laying the foundation of a great work.
And out of small things proceedeth that which is great."
                          - D&C 64:33