When I run (nsv) I get the same "ready to serve port 8080," which is a good sign, though I'm almost sure that my server (via shared hosting) isn't going to route everything automatically and properly...
In other words, I expect that there's some config I have to do and I'm not sure what it is.
The port for HTTP should really be port 80. However, I think most of the people here who have deployed the Arc server generally put Apache (serving on port 80) between the real world and the Arc server (serving on port 8080). This is generally done because nobody trusts the Arc server to be hackproof yet, especially not the Anarki version, which has been touched by quite a few people and may not be perfectly secure (but at least has a few more abilities than the Arc2 version).
If you're willing to risk it, then try (nsv 80), which forces the Arc server to listen on 80; you might need to run as root though.
I don't have root access, so naturally (nsv 80) gives "listen on 80 failed (Permission denied..." error.
Apache is up, but I'm not sure what I can do with it. Is there a simple redirect I need to run?
To be precise, I've loaded arc2 into a directory [mydomain]/news corresponding to news.[mydomain].com, with the news.arc specifying "news.[mydomain].com" as the site url; I launch the Arc REPL from there ("mzscheme -m -f as.scm") and do "(nsv)"... to no avail.
Try accessing news.[mydomain].com:8080. If you have some sort of terminal access on your remote computer, try lynx http://news.mydomain.com:8080/
As for the Apache <-> Arc talking thing, you'll have to wait for someone else to answer that question; I honestly don't know, because I haven't deployed one yet.
