[plt-scheme] Using PLaneT Packages in a Production Environment

On Tue, Jan 13, 2009 at 8:15 PM, Neil Van Dyke <neil at neilvandyke.org> wrote:
> If one has a system that uses PLaneT packages, and for security reasons we
> absolutely do not want the deployed system fetching anything from a public
> PLaneT repository, what's the best way to manage that?
>
> One question I'm debating is whether to: (1) have "planet" "require" specs
> in the code and to supply those packages in vetted form to a deployed system
> (via, e.g., a pre-constructed ".plt-scheme/planet/" cache);

I've done this before.

> or (2) pull
> versions of PLaneT packages into normal collections in our configuration
> management system, and use non-"planet" "require" specs for them.
>
> Our system does *not* need multiple versions of the same package, if that
> matters.

You can use technique (1) even if you do need multiple version.

> We'd also want to disable access to the PLaneT repository, such as by
> setting an environment variable or a Scheme parameter.

You can turn off access to PLaneT by editing the config.ss file and
giving it bogus URLs for the lookup.


Jay

-- 
Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University
http://teammccarthy.org/jay

"The glory of God is Intelligence" - D&C 93