Jakob Ackermann efb36b7193 Merge pull request #14698 from overleaf/bg-sg-use-node-watch 2 years ago
..
.dockerignore 8945373715 Merge pull request #5724 from overleaf/jpa-lean-docker-build 4 years ago
.gitignore a797fb2be7 Merge pull request #14138 from overleaf/bg-em-jpa-mj-node-18 3 years ago
.nvmrc a2cf7b459c Merge pull request #14902 from overleaf/jpa-node-18-18-0 2 years ago
LICENSE 9c0dbbc5c8 Remove CoffeeScript 5 years ago
README.md 955c9162c0 Rename to @overleaf/settings 5 years ago
Settings.js 0a12c47b35 Merge pull request #10815 from overleaf/em-esm-chat 3 years ago
buildscript.txt efb36b7193 Merge pull request #14698 from overleaf/bg-sg-use-node-watch 2 years ago
index.js 4de9c98d2f Merge pull request #6132 from overleaf/jpa-settings-linting 4 years ago
merge.js 4de9c98d2f Merge pull request #6132 from overleaf/jpa-settings-linting 4 years ago
package.json ae0c347f27 Merge pull request #6542 from overleaf/jpa-em-code-sharing-workspaces 4 years ago

README.md

@overleaf/settings

A small module to allow global config settings to be set for all services within the Overleaf architecture.

Settings file location

You can specify a custom location for the settings file by setting the SHARELATEX_CONFIG environment variable. E.g.

$ export SHARELATEX_CONFIG=/home/james/config/settings.development.js

Otherwise, the settings will be loaded from config/settings.NODE_ENV.js, where NODE_ENV is another environment variable, or defaults to development.

The config directory is first looked for in the current directory, and then relative to the settings module directory.