Thanks, that's helpful (I have been using Ctrl-C on my local machine, but
when I want the site to be up all the time, that doesn't seem like an
option).
Cheers,
Marc
On Thu, Mar 10, 2016 at 3:53 PM, Jay McCarthy
wrote:
> I agree. Also, I don't think you should use the 'web-server' command at
>
I agree. Also, I don't think you should use the 'web-server' command at
all. I think of (require web-server) as a library for making your own Web
server, rather than an independent application with a configuration
language (like Apache). I highly suggest thinking of it that way and using
either Ctr
> On Mar 10, 2016, at 12:46 PM, 'John Clements' via Racket Users
> wrote:
>
>
>> On Mar 10, 2016, at 12:26 PM, Marc Kaufmann
>> wrote:
>>
>> Hi,
>>
>> tl;dr : What is the 'best' way to start and stop a web server? Is there a
>> "racket-server die" or similar command which does not use 'ki
On Thu, Mar 10, 2016 at 03:26:28PM -0500, Marc Kaufmann wrote:
> In case you are wondering why I start the server with root privileges, it
> seems that I need those to listen to ports 80 and 443.
On Linux, you can use setcap to enable specific executable to bind low
ports even when running as non-r
> On Mar 10, 2016, at 12:26 PM, Marc Kaufmann wrote:
>
> Hi,
>
> tl;dr : What is the 'best' way to start and stop a web server? Is there a
> "racket-server die" or similar command which does not use 'kill’?
The web server is a standard process, not daemonized or doing anything strange,
so it
Hi,
tl;dr : What is the 'best' way to start and stop a web server? Is there a
"racket-server die" or similar command which does not use 'kill'?
Some background:
I am finally deploying lists of spaghetti-code (aka my website) to a real
web server. I do not have the permissions to do 'sudo kill ra
6 matches
Mail list logo
