Buckets provides a few ways to set configuration options when starting up. You can provide these settings directly to the
buckets function, or you can set ENV variables. Buckets will also look for two JSON files at the root of your project, both a
config.json and an
_environment_.json (where environment is whatever environment is currently active).
Here are the settings:
Set to false to include Buckets as Middleware.
The URL segment at which the server will serve the Buckets admin interface.
The URL segment at which the server will serve the Buckets API.
The file to where builds are stored (Buckets will look for a "staging" directory here, the others are created on the fly). This is going to be better.
The connection URL for Cloudinary. Set up for default Heroku installation.
A MongoDB connection string. The env variable is set up for a default Heroku installation.
NODE_ENV 'development' [production|development|test]
The app environment.
Fastly CDN support for a default Heroku installation.
Port at which Buckets serves the website.
The level at which the logger reports. Possible values are "none", "debug", "verbose", "info", "warn", and "error".
Path to where plugins are loaded from. All plugins are node modules with a naming convention of "buckets-name".
smtp.service 'gmail' (or
mandrill in production)
For local development, you can use a Gmail username/password (or any other format supported by Nodemailer). For our default Heroku setup, we currently support Mandrill.