我是keystone的新手,我正在尝试部署一个简单的网站模板来熟悉这项技术,我已经下载了所有的necassary模块并创建了一个keystone.js文件和package.json文件以及所有依赖项。但是,当我尝试在终端中运行keystone.js时,我得到以下内容:
Error: Invalid Configuration
CloudinaryImage fields (Gallery.heroImage) require the "cloudinary config" option to be set.
See http://keystonejs.com/docs/configuration/#cloudinary for more information.
我已经使用cloudinary建立了一个帐户并使用了npm install来确保它安装在系统中,但显然无法找到配置。我假设有一个简单的解决方案,我只需要将我的配置字段放在代码的正确位置,但我似乎无法找到有关在何处插入我的帐户详细信息的任何说明。任何帮助将不胜感激,如果我省略了任何重要的代码,请告诉我。
keystone.js:
require('dotenv').load();
// Require keystone
var keystone = require('keystone'),
handlebars = require('express3-handlebars');
// Initialise Keystone with your project's configuration.
// See http://keystonejs.com/guide/config for available options
// and documentation.
keystone.init({
'name': 'Tech Website',
'brand': 'Tech Website',
'less': 'public',
'static': 'public',
'favicon': 'public/favicon.ico',
'views': 'templates/views',
'view engine': 'hbs',
'custom engine': handlebars.create({
layoutsDir: 'templates/views/layouts',
partialsDir: 'templates/views/partials',
defaultLayout: 'default',
helpers: new require('./templates/views/helpers')(),
extname: '.hbs'
}).engine,
'auto update': true,
'session': true,
'auth': true,
'user model': 'Yes',
'cookie secret': 'pUO>=q^~Z.h]~pO"k;:]dTcTb:6pT3Xyassxdk>9K]7J0MGqSWWr;$rs6lG<XLdB'
});
// Load your project's Models
keystone.import('models');
// Setup common locals for your templates. The following are required for the
// bundled templates and layouts. Any runtime locals (that should be set uniquely
// for each request) should be added to ./routes/middleware.js
keystone.set('locals', {
_: require('underscore'),
env: keystone.get('env'),
utils: keystone.utils,
editable: keystone.content.editable
});
// Load your project's Routes
keystone.set('routes', require('./routes'));
// Setup common locals for your emails. The following are required by Keystone's
// default email templates, you may remove them if you're using your own.
// Configure the navigation bar in Keystone's Admin UI
keystone.set('nav', {
'posts': ['posts', 'post-categories'],
'galleries': 'galleries',
'enquiries': 'enquiries',
'yes': 'yes'
});
// Start Keystone to connect to your database and initialise the web server
.start();
的package.json
{
"name": "tech-website",
"version": "0.0.0",
"private": true,
"dependencies": {
"keystone": "~0.2.27",
"async": "~0.9.0",
"underscore": "~1.7.0",
"moment": "~2.8.1",
"express3-handlebars": "~0.5.0",
"handlebars": "^2.0.0-alpha.2",
"dotenv": "0.4.0"
},
"devDependencies": {
"grunt": "~0.4.4",
"grunt-express-server": "~0.4.17",
"grunt-contrib-watch": "~0.6.1",
"grunt-contrib-jshint": "~0.7.1",
"jshint-stylish": "~0.1.3",
"load-grunt-tasks": "~0.4.0",
"grunt-node-inspector": "~0.1.5",
"time-grunt": "~0.3.1",
"grunt-concurrent": "~0.5.0",
"grunt-nodemon": "~0.2.1",
"open": "0.0.5"
},
"engines": {
"node": ">=0.10.22",
"npm": ">=1.3.14"
},
"scripts": {
"start": "node keystone.js"
},
"main": "keystone.js"
}
答案 0 :(得分:5)
您可以通过多种方式在KeystoneJS应用中配置Cloudinary
。
一个选项是设置CLOUDINARY_URL
环境变量。您可以在.env
文件中执行此操作,因为您使用的是dotenv
。
CLOUDINARY_URL=cloudinary://api_key:api_secret@cloud_name
第二种方法是在Keystonejs应用中设置cloudinary config
设置。
您可以在keystone.init()
keystone.init({
...
'cloudinary config': 'cloudinary://api_key:api_secret@cloud_name',
...
});
...或使用keystone.set()
方法。
keystone.set('cloudinary config', 'cloudinary://api_key:api_secret@cloud_name' );
这些都在KeystonsJS Configuration页面上详细说明。
答案 1 :(得分:3)
添加内容 -
实际上对我有用的是当我将配置设置部分放在
中时keystone.init部分。使用setter并不适合我。
keystone.init({
...
'cloudinary config': 'cloudinary://api_key:api_secret@cloud_name',
...
});
上面的代码是唯一能够完美运行的代码。
答案 2 :(得分:1)
这是我如何部署到heroku的。在 keystone.js 中添加一个块以使用环境变量:
if (keystone.get('env') == 'production'){
keystone.set('cloudinary config', process.env.CLOUDINARY_URL);
keystone.set('cookie secret', process.env.COOKIE_SECRET);
keystone.set('mandrill api key', process.env.MANDRILL_API_KEY);
}
然后通过命令行在heroku实例上设置环境变量:
$ heroku config:set MANDRILL_API_KEY=YOUR_API_KEY
$ heroku config:set CLOUDINARY_URL=cloudinary://api_key:api_secret@cloud_name
$ heroku config:set NODE_ENV=production
$ heroku config:set COOKIE_SECRET=YOUR_COOKIE_STRING