Configuring Pak

On startup, Pak reads configuration from a pakrc file. This file defines the default configuration for Pak. To show the pak configuration, type:pak config

This displays something like:

{ catalogs: { pak: { lookup: "http://localhost:4000/search/${NAME}", query: "http://localhost:4000/search/${NAME}", publish: "http://localhost:4000/pak/publish", download: "${OWNER}/${NAME}/archive/${TAG}.tar.gz", overrides: "" }, bower: { list: "", query: "${NAME}", download: "${OWNER}/${NAME}/archive/${TAG}.tar.gz" }, npm: { query: "${NAME}", download: "${NAME}/-/${NAME}-${TAG}.tgz" } }, directories: { files: "files", export: "lib", paks: "paks", pakcache: "/Users/guest/.paks", top: "." } }

The catalogs property specifies the web sites that host Pak or Bower catalogs.


The paks directory is the name of the local application sub-directory in which to store paks. The pakcache directory defines where to cache paks on the local system. The export directory is to where Pak will export installed pacakge contents. The top directory refers to the current directory.


The Pak configuration may be modified by defining properties in a pakrc file or in the application's package.json file. Pak locates a pakrc file by searching in order until it finds a suitable configuration file. This is the search order:

The package.json is always loaded after any pakrc file. In this manner, the package.json may override default configuration.

© Embedthis Software, 2003-2015. All rights reserved.