On Thu, Dec 29, 2011 at 8:07 PM, Robby Findler
wrote:
> I think that a minor variation on Neil's strategy should not be too
> difficult to do (but I'll certainly agree that it is not an ideal
> situation). What you'd do is first just download (via the "Bam" method
> below :) the planet packages yo
On Fri, Dec 30, 2011 at 9:45 AM, Neil Van Dyke wrote:
> It's good to see interest in Racket from cloud people. Feel free to ask
> lots of questions on the Racket "users" and "dev" email lists as you work
> through your solution.
Well, this a side-interest for personally, but *anyone* can make a
Another variation, if you're thinking about cloud infrastructure today:
you could pretty easily make your own faux PLaneT server that either is
for a single app or takes the identity/profile of the app as part of the
URL the app uses to access the PLaneT server.
The faux server can be a tiny H
I think that a minor variation on Neil's strategy should not be too
difficult to do (but I'll certainly agree that it is not an ideal
situation). What you'd do is first just download (via the "Bam" method
below :) the planet packages you want. Then, if you look inside this
directory:
(build-pat
Daniel Farina wrote at 12/29/2011 07:59 PM:
The goal is that a program written, say, three
years ago should be able to run the same way it did when it was
written, so it's really useful to freeze all the dependencies into the
file system somehow and preserve it.
Someone else can comment on
Hello list,
I've been playing with Racket. I'm impressed, especially with the
documentation (both its content and its presentation), the contract
system, and its performance. I have been investigating writing a
build pack for Heroku to attempt deploying Racket projects with ease.
A blocker, tho
6 matches
Mail list logo
