| title |
|---|
Topics |
This part of the guide provides pages dedicated to specific topics.
: The Stack root is a directory where Stack stores important information
: Stack work directories are directories within a local project or package directory in which Stack stores files created during the build process.
: How to specify the location of snapshots.
: How to specify the location of packages.
: How to specify the contents of a snapshot.
: The difference between Stack's project-level configuration file and a Cabal file describing a Haskell package.
: How to use Stack's script interpreter.
: Stack has support for automatically performing builds inside a Docker container.
: Stack can be configured to integrate with Nix, a purely functional package manager.
Non-standard project initialization
: You may need to configure Stack to work with an existing project that has one or more Cabal files but no Stack project-level configuration file.
: Advice on debugging using Stack.
: Advice on intergrating Stack with code editors.
: Advice on using Stack with Visual Studio Code and its Haskell extension.
: Advice on using Stack on Windows.
: Adding support for the tab completion of standard Stack arguments to the shell programs Bash, Zsh (the Z shell) and fish.
: Advice on using Stack with CI.
: Advice on using Stack on Travis CI.
: Advice on using Stack on Azure CI.
: The contents of Stack's lock files, how they are used, and how they are created and updated.
: Advice on using Stack with Haskell packages that include C source code,
including those with a C main function.