example-rest-api-sails.js:使用Sails.js MVC框架构建的Node.js中的REST API示例

  • W6_736381
    了解作者
  • 46KB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-04-05 01:13
    上传日期
Sails.js示例REST API ,一个用于Node.js和MongoDB的MVC框架。 发展 安装依赖项: npm install 启动应用程序: npm start或npm run-script watch 资料库 此示例将MongoDB用于模型,将Redis用于会话和套接字存储。 当Sails在本地运行时,它将使用默认设置连接到本地Redis和MongoDB数据库。 如有任何问题,可以创建和编辑config/local.js以覆盖默认配置并使用自己的配置。 这些设置优先于所有其他配置文件,包括config/env子文件夹中的文件。 这是一个示例文件,该文件使用内存作为套接字,使用内存作为会话,并使用MongoLab服务器作为模型。 module.exports = { connections: { mongodb: { host: 'ds02
example-rest-api-sails_js-master.zip
内容介绍
# Sails.js Example REST API [![Build Status](https://travis-ci.org/lawnchairstudios/example-rest-api-sails.js.svg)](https://travis-ci.org/lawnchairstudios/example-rest-api-sails.js) [Sails](http://sailsjs.org/), a MVC framework for Node.js, and MongoDB. ## Development 1. Install dependencies: `npm install` 2. Start the application: `npm start` or `npm run-script watch` ### Databases This example uses MongoDB for models and Redis for session and sockets stores. When Sails is run locally, it will connect to local Redis and MongoDB databases using the default settings. Should you have any issues, you can create and edit `config/local.js` to override the default config and use your own. These settings take precedence over all other config files, including those in the `config/env` subfolder. Here is an example file that uses memory for sockets, memory for sessions, and a MongoLab server for the models. ``` module.exports = { connections: { mongodb: { host: 'ds029541.mongolab.com', port: 29541, user: 'foo', password: 'bar', database: 'baz' } }, session: { adapter: 'memory' }, sockets: { adapter: 'memory' } }; ``` For more, see the Sails.js [configuration documentation](http://sailsjs.org/#/documentation/reference/sails.config/sails.config.local.html). ## Deployment Sails is deployed to an instance on Heroku, an application platform. If this is your first time deploying the app, follow steps 1-6. Otherwise, just skip to step 4. For more, see the [Heroku Documentation on Node.js applications](https://devcenter.heroku.com/articles/getting-started-with-nodejs#introduction). 1. Create new app: `heroku create app-name` 2. Add Redis: `heroku addons:add redistogo` 3. Add MongoDB: `heroku addons:add mongolab` 4. Deploy the app: `git push heroku master` 5. Set the environment to production: `heroku config:set NODE_ENV=production` 6. Insure that at least one instance is running: `heroku ps:scale web=1` Other helpful tasks: - View application logs: `heroku logs --tail` - Open the application: `heroku open` - View application configuration: `heroku config` - Add existing Heroku Git Origin: `heroku git:remote -a appname` Addons: - [Redis to Go](https://addons.heroku.com/redistogo) - [MongoLab](https://addons.heroku.com/mongolab) - [New Relic APM](https://addons.heroku.com/newrelic) The command that Heroku executes to start the application is defined in the procfile. The procfile declares a single process type, `web`, and the command needed to run it. For more, see the [Heroku documentation](https://devcenter.heroku.com/articles/getting-started-with-nodejs#define-a-procfile). ## Further Documentation ### Redis Node.js (and consequently Sails.js) apps scale horizontally. It's a powerful, efficient approach, but it involves a tiny bit of planning. At scale, you'll want to be able to copy your app onto multiple Sails.js servers and throw them behind a load balancer. One of the big challenges of scaling an application is that these sorts of clustered deployments cannot share memory, since they are on physically different machines. On top of that, there is no guarantee that a user will "stick" with the same server between requests (whether HTTP or sockets), since the load balancer will route each request to the Sails server with the most available resources. However that means that all room/pubsub/socket processing and shared memory has to be offloaded to a shared, remote messaging queue (usually Redis).Luckily, Socket.io (and consequently Sails.js) apps support Redis for sockets by default. It is worth mentioning that, when `NODE_ENV=production`, config variables are used for the Redis connection values. If these config variables are not available, Sails will try to connect to redis database 0 running on localhost via port 6379. The default password (none) will be used. The Redis connections are configured in `config/sockets.js` and `config/session.js`. [See options for the Redis adapter](https://github.com/visionmedia/connect-redis) if further configuration is needed. ### REST API Endpoints ``` # Backbone Conventions GET : /:controller => findAll() GET : /:controller/read/:id => find(id) POST : /:controller/create => create() POST : /:controller/create/:id => create(id) PUT : /:controller/update/:id => update(id) DELETE: /:controller/destroy/:id => destroy(id) # You can also explicitly state the action GET : /:controller/find => findAll() GET : /:controller/find/:id => find(id) POST : /:controller/create => create(id) PUT : /:controller/update/:id => update(id) DELETE: /:controller/destroy/:id => destroy(id) ``` --- Copyright 2015 Lawn Chair Studios. All rights reserved.
评论
    相关推荐