<%= i18n('That\'s right-- you can use either i18n() or __()') %>
21 | ``` 22 | 23 | ## Configuration 24 | Localization/internationalization config can be found in `config/i18n.js`, from where you can set your supported locales. -------------------------------------------------------------------------------- /config/locales/de.json: -------------------------------------------------------------------------------- 1 | { 2 | "Welcome": "Wilkommen" 3 | } -------------------------------------------------------------------------------- /config/locales/en.json: -------------------------------------------------------------------------------- 1 | { 2 | "Welcome": "Welcome" 3 | } 4 | -------------------------------------------------------------------------------- /config/locales/es.json: -------------------------------------------------------------------------------- 1 | { 2 | "Welcome": "Bienvenido" 3 | } 4 | -------------------------------------------------------------------------------- /config/locales/fr.json: -------------------------------------------------------------------------------- 1 | { 2 | "Welcome": "Bienvenue" 3 | } 4 | -------------------------------------------------------------------------------- /config/log.js: -------------------------------------------------------------------------------- 1 | /** 2 | * Logger configuration 3 | * 4 | * Configure the log level for your app, as well as the transport 5 | * (Underneath the covers, Sails uses Winston for logging, which 6 | * allows for some pretty neat custom transports/adapters for log messages) 7 | * 8 | * For more information on the Sails logger, check out: 9 | * http://sailsjs.org/#documentation 10 | */ 11 | 12 | module.exports = { 13 | 14 | // Valid `level` configs: 15 | // i.e. the minimum log level to capture with sails.log.*() 16 | // 17 | // 'error' : Display calls to `.error()` 18 | // 'warn' : Display calls from `.error()` to `.warn()` 19 | // 'debug' : Display calls from `.error()`, `.warn()` to `.debug()` 20 | // 'info' : Display calls from `.error()`, `.warn()`, `.debug()` to `.info()` 21 | // 'verbose': Display calls from `.error()`, `.warn()`, `.debug()`, `.info()` to `.verbose()` 22 | // 23 | log: { 24 | level: 'info' 25 | } 26 | 27 | }; 28 | -------------------------------------------------------------------------------- /config/policies.js: -------------------------------------------------------------------------------- 1 | /** 2 | * Policy mappings (ACL) 3 | * 4 | * Policies are simply Express middleware functions which run **before** your controllers. 5 | * You can apply one or more policies to a given controller, or protect just one of its actions. 6 | * 7 | * Any policy file (e.g. `authenticated.js`) can be dropped into the `/policies` folder, 8 | * at which point it can be accessed below by its filename, minus the extension, (e.g. `authenticated`) 9 | * 10 | * For more information on policies, check out: 11 | * http://sailsjs.org/#documentation 12 | */ 13 | 14 | 15 | module.exports.policies = { 16 | 17 | // Default policy for all controllers and actions 18 | // (`true` allows public access) 19 | '*': true 20 | 21 | /* 22 | // Here's an example of adding some policies to a controller 23 | RabbitController: { 24 | 25 | // Apply the `false` policy as the default for all of RabbitController's actions 26 | // (`false` prevents all access, which ensures that nothing bad happens to our rabbits) 27 | '*': false, 28 | 29 | // For the action `nurture`, apply the 'isRabbitMother' policy 30 | // (this overrides `false` above) 31 | nurture : 'isRabbitMother', 32 | 33 | // Apply the `isNiceToAnimals` AND `hasRabbitFood` policies 34 | // before letting any users feed our rabbits 35 | feed : ['isNiceToAnimals', 'hasRabbitFood'] 36 | } 37 | */ 38 | }; 39 | 40 | 41 | /** 42 | * Here's what the `isNiceToAnimals` policy from above might look like: 43 | * (this file would be located at `policies/isNiceToAnimals.js`) 44 | * 45 | * We'll make some educated guesses about whether our system will 46 | * consider this user someone who is nice to animals. 47 | * 48 | * Besides protecting rabbits (while a noble cause, no doubt), 49 | * here are a few other example use cases for policies: 50 | * 51 | * + cookie-based authentication 52 | * + role-based access control 53 | * + limiting file uploads based on MB quotas 54 | * + OAuth 55 | * + BasicAuth 56 | * + or any other kind of authentication scheme you can imagine 57 | * 58 | */ 59 | 60 | /* 61 | module.exports = function isNiceToAnimals (req, res, next) { 62 | 63 | // `req.session` contains a set of data specific to the user making this request. 64 | // It's kind of like our app's "memory" of the current user. 65 | 66 | // If our user has a history of animal cruelty, not only will we 67 | // prevent her from going even one step further (`return`), 68 | // we'll go ahead and redirect her to PETA (`res.redirect`). 69 | if ( req.session.user.hasHistoryOfAnimalCruelty ) { 70 | return res.redirect('http://PETA.org'); 71 | } 72 | 73 | // If the user has been seen frowning at puppies, we have to assume that 74 | // they might end up being mean to them, so we'll 75 | if ( req.session.user.frownsAtPuppies ) { 76 | return res.redirect('http://www.dailypuppy.com/'); 77 | } 78 | 79 | // Finally, if the user has a clean record, we'll call the `next()` function 80 | // to let them through to the next policy or our controller 81 | next(); 82 | }; 83 | */ 84 | -------------------------------------------------------------------------------- /config/routes.js: -------------------------------------------------------------------------------- 1 | /** 2 | * Routes 3 | * 4 | * Sails uses a number of different strategies to route requests. 5 | * Here they are top-to-bottom, in order of precedence. 6 | * 7 | * For more information on routes, check out: 8 | * http://sailsjs.org/#documentation 9 | */ 10 | 11 | 12 | 13 | /** 14 | * (1) Core middleware 15 | * 16 | * Middleware included with `app.use` is run first, before the router 17 | */ 18 | 19 | 20 | /** 21 | * (2) Static routes 22 | * 23 | * This object routes static URLs to handler functions-- 24 | * In most cases, these functions are actions inside of your controllers. 25 | * For convenience, you can also connect routes directly to views or external URLs. 26 | * 27 | */ 28 | 29 | module.exports.routes = { 30 | 31 | // By default, your root route (aka home page) points to a view 32 | // located at `views/home/index.ejs` 33 | // 34 | // (This would also work if you had a file at: `/views/home.ejs`) 35 | '/': { 36 | view: 'home/index' 37 | }, 38 | 39 | // Custom CRUD Rest Routes 40 | 'get /sleep/:id?': 'SleepController.find', 41 | 'post /sleep': 'SleepController.create', 42 | 'put /sleep/:id?': 'SleepController.update', 43 | 'delete /sleep/:id?': 'SleepController.destroy' 44 | 45 | /* 46 | // But what if you want your home page to display 47 | // a signup form located at `views/user/signup.ejs`? 48 | '/': { 49 | view: 'user/signup' 50 | } 51 | 52 | 53 | // Let's say you're building an email client, like Gmail 54 | // You might want your home route to serve an interface using custom logic. 55 | // In this scenario, you have a custom controller `MessageController` 56 | // with an `inbox` action. 57 | '/': 'MessageController.inbox' 58 | 59 | 60 | // Alternatively, you can use the more verbose syntax: 61 | '/': { 62 | controller: 'MessageController', 63 | action: 'inbox' 64 | } 65 | 66 | 67 | // If you decided to call your action `index` instead of `inbox`, 68 | // since the `index` action is the default, you can shortcut even further to: 69 | '/': 'MessageController' 70 | 71 | 72 | // Up until now, we haven't specified a specific HTTP method/verb 73 | // The routes above will apply to ALL verbs! 74 | // If you want to set up a route only for one in particular 75 | // (GET, POST, PUT, DELETE, etc.), just specify the verb before the path. 76 | // For example, if you have a `UserController` with a `signup` action, 77 | // and somewhere else, you're serving a signup form looks like: 78 | // 79 | // 84 | 85 | // You would want to define the following route to handle your form: 86 | 'post /signup': 'UserController.signup' 87 | 88 | 89 | // What about the ever-popular "vanity URLs" aka URL slugs? 90 | // (you might remember doing this with `mod_rewrite` in Apache) 91 | // 92 | // This is where you want to set up root-relative dynamic routes like: 93 | // http://yourwebsite.com/twinkletoez 94 | // 95 | // NOTE: 96 | // You'll still want to allow requests through to the static assets, 97 | // so we need to set up this route to ignore URLs that have a trailing ".": 98 | // (e.g. your javascript, CSS, and image files) 99 | 'get /*(^.*)': 'UserController.profile' 100 | 101 | */ 102 | }; 103 | 104 | 105 | 106 | /** 107 | * (3) Action blueprints 108 | * These routes can be disabled by setting (in `config/controllers.js`): 109 | * `module.exports.controllers.blueprints.actions = false` 110 | * 111 | * All of your controllers ' actions are automatically bound to a route. For example: 112 | * + If you have a controller, `FooController`: 113 | * + its action `bar` is accessible at `/foo/bar` 114 | * + its action `index` is accessible at `/foo/index`, and also `/foo` 115 | */ 116 | 117 | 118 | /** 119 | * (4) Shortcut CRUD blueprints 120 | * 121 | * These routes can be disabled by setting (in config/controllers.js) 122 | * `module.exports.controllers.blueprints.shortcuts = false` 123 | * 124 | * If you have a model, `Foo`, and a controller, `FooController`, 125 | * you can access CRUD operations for that model at: 126 | * /foo/find/:id? -> search lampshades using specified criteria or with id=:id 127 | * 128 | * /foo/create -> create a lampshade using specified values 129 | * 130 | * /foo/update/:id -> update the lampshade with id=:id 131 | * 132 | * /foo/destroy/:id -> delete lampshade with id=:id 133 | * 134 | */ 135 | 136 | /** 137 | * (5) REST blueprints 138 | * 139 | * These routes can be disabled by setting (in config/controllers.js) 140 | * `module.exports.controllers.blueprints.rest = false` 141 | * 142 | * If you have a model, `Foo`, and a controller, `FooController`, 143 | * you can access CRUD operations for that model at: 144 | * 145 | * get /foo/:id? -> search lampshades using specified criteria or with id=:id 146 | * 147 | * post /foo -> create a lampshade using specified values 148 | * 149 | * put /foo/:id -> update the lampshade with id=:id 150 | * 151 | * delete /foo/:id -> delete lampshade with id=:id 152 | * 153 | */ 154 | 155 | /** 156 | * (6) Static assets 157 | * 158 | * Flat files in your `assets` directory- (these are sometimes referred to as 'public') 159 | * If you have an image file at `/assets/images/foo.jpg`, it will be made available 160 | * automatically via the route: `/images/foo.jpg` 161 | * 162 | */ 163 | 164 | 165 | 166 | /** 167 | * (7) 404 (not found) handler 168 | * 169 | * Finally, if nothing else matched, the default 404 handler is triggered. 170 | * See `config/404.js` to adjust your app's 404 logic. 171 | */ -------------------------------------------------------------------------------- /config/session.js: -------------------------------------------------------------------------------- 1 | /** 2 | * Session 3 | * 4 | * Sails session integration leans heavily on the great work already done by Express, but also unifies 5 | * Socket.io with the Connect session store. It uses Connect's cookie parser to normalize configuration 6 | * differences between Express and Socket.io and hooks into Sails' middleware interpreter to allow you 7 | * to access and auto-save to `req.session` with Socket.io the same way you would with Express. 8 | * 9 | * For more information on configuring the session, check out: 10 | * http://sailsjs.org/#documentation 11 | */ 12 | 13 | module.exports.session = { 14 | 15 | // Session secret is automatically generated when your new app is created 16 | // Replace at your own risk in production-- you will invalidate the cookies of your users, 17 | // forcing them to log in again. 18 | secret: 'a8c65509b5ab6e387f134cedb3fa3079' 19 | 20 | 21 | // In production, uncomment the following lines to set up a shared redis session store 22 | // that can be shared across multiple Sails.js servers 23 | // adapter: 'redis', 24 | // 25 | // The following values are optional, if no options are set a redis instance running 26 | // on localhost is expected. 27 | // Read more about options at: https://github.com/visionmedia/connect-redis 28 | // 29 | // host: 'localhost', 30 | // port: 6379, 31 | // ttl:
50 | 64 | Why might this be happening? 65 |
66 |
71 |
72 | 
50 | 60 | Why might this be happening? 61 |
62 |
67 |
68 | 
53 | 
54 |
65 | <%
66 | _.each(errors, function (error) { %>
67 | <%= error %>
68 | <%
69 | }); %>
70 |
74 | A team of highly trained sea bass is working on this as we speak.
75 | If the problem persists, please contact the system administrator and inform them of the time that the error occured, and anything you might have done that may have caused the error.
76 |
83 | 
18 | Don't worry, we've got your back.
26 |33 | Run sails generate foo. This will create a model Foo and controller FooController 34 |
35 |44 | Run sails lift to start up your app. If you visit http://localhost:1337/foo in your browser, you'll see a socket.io-compatible REST API was generated for your 'Foo' model. 45 |
46 |From here, you can modify your models, create custom controller methods as Express middleware, and create custom routes (routes are set up in config/routes.js). Visit the Sails website for more information on next steps.
55 |