In Installation, we described how to install roswell from the source. However, it assumed the global installation.
Local installation is available by specifying --prefix option to ./configure. The default location is /usr/local. Actual binary is installed in $PREFIX/bin and supporting files are installed into $PREFIX/etc/roswell/.
This is useful when using roswell as a backend of CI services (e.g. travis): When you specify a directory accessible without root permission, then you can switch to the new container-based infrastructure for faster startup (of the tests). We already provide such a script for Travis, CircleCI and Coverall using this feature.
Another usage is for bundling roswell in a standalone project which does not alter the user environment at all.
Example:
$ git clone -b release https://github.com/roswell/roswell.git
$ cd roswell
$ sh bootstrap
$ ./configure --prefix=$HOME/.local/
$ make && make install ### in this case, no sudo is required!
$ ~/.local/bin/ros
Another issue related to local installation is the resource directory ($HOME/.roswell) that contains downloaded lisp binaries, quicklisp libraries and so forth. To customize this location, modify ROSWELL_HOME environment variable when invoking ros. For example,
$ mkdir tmp-roswell-home
$ ROSWELL_HOME=tmp-roswell-home/ ros setupHome
Getting started / Tutorials
- Installation
- Initial Recommended Setup
- Roswell as a Scripting Environment
- ros template
- Set up guide for Anaconda virtual env
Advanced Installation
Roswell as a scripting environment
- Roswell as a Scripting Environment
- Advanced scripting
- Reducing Startup Time
- List of Roswell Installable Scripts
- Practical Usecases
- Building images and executables
Roswell as an implementation manager
Roswell as a Testing Environment
- Roswell as a Testing Environment
- Travis CI
- Circle CI
- GitHub Actions
- Coveralls
- Roswell in Virtual Environments