@webresto/graphql 1.3.0

package/test/fixtures/v0.12-app/config/cors.js

@@ -0,0 +1,78 @@
+/**
+ * Cross-Origin Resource Sharing (CORS) Settings
+ * (sails.config.cors)
+ *
+ * CORS is like a more modern version of JSONP-- it allows your server/API
+ * to successfully respond to requests from client-side JavaScript code
+ * running on some other domain (e.g. google.com)
+ * Unlike JSONP, it works with POST, PUT, and DELETE requests
+ *
+ * For more information on CORS, check out:
+ * http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
+ *
+ * Note that any of these settings (besides 'allRoutes') can be changed on a per-route basis
+ * by adding a "cors" object to the route configuration:
+ *
+ * '/get foo': {
+ *   controller: 'foo',
+ *   action: 'bar',
+ *   cors: {
+ *     origin: 'http://foobar.com,https://owlhoot.com'
+ *   }
+ *  }
+ *
+ *  For more information on this configuration file, see:
+ *  http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.cors.html
+ *
+ */
+
+module.exports.cors = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Allow CORS on all routes by default? If not, you must enable CORS on a   *
+  * per-route basis by either adding a "cors" configuration object to the    *
+  * route config, or setting "cors:true" in the route config to use the      *
+  * default settings below.                                                  *
+  *                                                                          *
+  ***************************************************************************/
+
+  // allRoutes: false,
+
+  /***************************************************************************
+  *                                                                          *
+  * Which domains which are allowed CORS access? This can be a               *
+  * comma-delimited list of hosts (beginning with http:// or https://) or    *
+  * "*" to allow all domains CORS access.                                    *
+  *                                                                          *
+  ***************************************************************************/
+
+  // origin: '*',
+
+  /***************************************************************************
+  *                                                                          *
+  * Allow cookies to be shared for CORS requests?                            *
+  *                                                                          *
+  ***************************************************************************/
+
+  // credentials: true,
+
+  /***************************************************************************
+  *                                                                          *
+  * Which methods should be allowed for CORS requests? This is only used in  *
+  * response to preflight requests (see article linked above for more info)  *
+  *                                                                          *
+  ***************************************************************************/
+
+  // methods: 'GET, POST, PUT, DELETE, OPTIONS, HEAD',
+
+  /***************************************************************************
+  *                                                                          *
+  * Which headers should be allowed for CORS requests? This is only used in  *
+  * response to preflight requests.                                          *
+  *                                                                          *
+  ***************************************************************************/
+
+  // headers: 'content-type'
+
+};

package/test/fixtures/v0.12-app/config/csrf.js

@@ -0,0 +1,64 @@
+/**
+ * Cross-Site Request Forgery Protection Settings
+ * (sails.config.csrf)
+ *
+ * CSRF tokens are like a tracking chip.  While a session tells the server that a user
+ * "is who they say they are", a csrf token tells the server "you are where you say you are".
+ *
+ * When enabled, all non-GET requests to the Sails server must be accompanied by
+ * a special token, identified as the '_csrf' parameter.
+ *
+ * This option protects your Sails app against cross-site request forgery (or CSRF) attacks.
+ * A would-be attacker needs not only a user's session cookie, but also this timestamped,
+ * secret CSRF token, which is refreshed/granted when the user visits a URL on your app's domain.
+ *
+ * This allows us to have certainty that our users' requests haven't been hijacked,
+ * and that the requests they're making are intentional and legitimate.
+ *
+ * This token has a short-lived expiration timeline, and must be acquired by either:
+ *
+ * (a)		For traditional view-driven web apps:
+ *			Fetching it from one of your views, where it may be accessed as
+ *			a local variable, e.g.:
+ *			<form>
+ *				<input type="hidden" name="_csrf" value="<%= _csrf %>" />
+ *			</form>
+ *
+ * or (b)	For AJAX/Socket-heavy and/or single-page apps:
+ *			Sending a GET request to the `/csrfToken` route, where it will be returned
+ *			as JSON, e.g.:
+ *			{ _csrf: 'ajg4JD(JGdajhLJALHDa' }
+ *
+ *
+ * Enabling this option requires managing the token in your front-end app.
+ * For traditional web apps, it's as easy as passing the data from a view into a form action.
+ * In AJAX/Socket-heavy apps, just send a GET request to the /csrfToken route to get a valid token.
+ *
+ * For more information on CSRF, check out:
+ * http://en.wikipedia.org/wiki/Cross-site_request_forgery
+ *
+ * For more information on this configuration file, including info on CSRF + CORS, see:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.csrf.html
+ *
+ */
+
+/****************************************************************************
+*                                                                           *
+* Enabled CSRF protection for your site?                                    *
+*                                                                           *
+****************************************************************************/
+
+// module.exports.csrf = false;
+
+/****************************************************************************
+*                                                                           *
+* You may also specify more fine-grained settings for CSRF, including the   *
+* domains which are allowed to request the CSRF token via AJAX. These       *
+* settings override the general CORS settings in your config/cors.js file.  *
+*                                                                           *
+****************************************************************************/
+
+// module.exports.csrf = {
+//    grantTokenViaAjax: true,
+//    origin: ''
+// }

package/test/fixtures/v0.12-app/config/env/development.js

@@ -0,0 +1,10 @@
+module.exports = {
+  models: {
+   connection: 'memory'
+
+  },
+  port: process.env.PORT === undefined ? 42772 : process.env.PORT,
+  log: {
+    level: process.env.LOG_LEVEL === undefined ? 'silent' : process.env.PORT
+   }
+};

package/test/fixtures/v0.12-app/config/env/production.js

@@ -0,0 +1,16 @@
+module.exports = {
+  models: {
+    connection: 'memory',
+    migrate: 'safe'
+  },
+  adminpanel:{
+    auth: true
+  },
+  log: {
+    level: 'info'
+  },
+  port: process.env.PORT === undefined ? 42772 : process.env.PORT,
+  log: {
+   level: "silent"
+  }
+};

package/test/fixtures/v0.12-app/config/globals.js

@@ -0,0 +1,63 @@
+/**
+ * Global Variable Configuration
+ * (sails.config.globals)
+ *
+ * Configure which global variables which will be exposed
+ * automatically by Sails.
+ *
+ * For more information on configuration, check out:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.globals.html
+ */
+module.exports.globals = {
+
+  /****************************************************************************
+  *                                                                           *
+  * Expose the lodash installed in Sails core as a global variable. If this   *
+  * is disabled, like any other node module you can always run npm install    *
+  * lodash --save, then var _ = require('lodash') at the top of any file.     *
+  *                                                                           *
+  ****************************************************************************/
+
+	// _: true,
+
+  /****************************************************************************
+  *                                                                           *
+  * Expose the async installed in Sails core as a global variable. If this is *
+  * disabled, like any other node module you can always run npm install async *
+  * --save, then var async = require('async') at the top of any file.         *
+  *                                                                           *
+  ****************************************************************************/
+
+	// async: true,
+
+  /****************************************************************************
+  *                                                                           *
+  * Expose the sails instance representing your app. If this is disabled, you *
+  * can still get access via req._sails.                                      *
+  *                                                                           *
+  ****************************************************************************/
+
+	// sails: true,
+
+  /****************************************************************************
+  *                                                                           *
+  * Expose each of your app's services as global variables (using their       *
+  * "globalId"). E.g. a service defined in api/models/NaturalLanguage.js      *
+  * would have a globalId of NaturalLanguage by default. If this is disabled, *
+  * you can still access your services via sails.services.*                   *
+  *                                                                           *
+  ****************************************************************************/
+
+	// services: true,
+
+  /****************************************************************************
+  *                                                                           *
+  * Expose each of your app's models as global variables (using their         *
+  * "globalId"). E.g. a model defined in api/models/User.js would have a      *
+  * globalId of User by default. If this is disabled, you can still access    *
+  * your models via sails.models.*.                                           *
+  *                                                                           *
+  ****************************************************************************/
+
+  models: true
+};

package/test/fixtures/v0.12-app/config/hookTimeout.js

@@ -0,0 +1,8 @@
+module.exports.orm = {
+  _hookTimeout: 100000000
+};
+
+module.exports.pubsub = {
+  _hookTimeout: 100000000
+};
+

package/test/fixtures/v0.12-app/config/http.js

@@ -0,0 +1,93 @@
+/**
+ * HTTP Server Settings
+ * (sails.config.http)
+ *
+ * Configuration for the underlying HTTP server in Sails.
+ * Only applies to HTTP requests (not WebSockets)
+ *
+ * For more information on configuration, check out:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.http.html
+ */
+
+module.exports.http = {
+
+  /****************************************************************************
+  *                                                                           *
+  * Express middleware to use for every Sails request. To add custom          *
+  * middleware to the mix, add a function to the middleware config object and *
+  * add its key to the "order" array. The $custom key is reserved for         *
+  * backwards-compatibility with Sails v0.9.x apps that use the               *
+  * `customMiddleware` config option.                                         *
+  *                                                                           *
+  ****************************************************************************/
+
+  middleware: {
+
+  /***************************************************************************
+  *                                                                          *
+  * The order in which middleware should be run for HTTP request. (the Sails *
+  * router is invoked by the "router" middleware below.)                     *
+  *                                                                          *
+  ***************************************************************************/
+
+    // order: [
+    //   'startRequestTimer',
+    //   'cookieParser',
+    //   'session',
+    //   'myRequestLogger',
+    //   'bodyParser',
+    //   'handleBodyParserError',
+    //   'compress',
+    //   'methodOverride',
+    //   'poweredBy',
+    //   '$custom',
+    //   'router',
+    //   'www',
+    //   'favicon',
+    //   '404',
+    //   '500'
+    // ],
+
+  /****************************************************************************
+  *                                                                           *
+  * Example custom middleware; logs each request to the console.              *
+  *                                                                           *
+  ****************************************************************************/
+
+    // myRequestLogger: function (req, res, next) {
+    //     console.log("Requested :: ", req.method, req.url);
+    //     return next();
+    // }
+
+
+  /***************************************************************************
+  *                                                                          *
+  * The body parser that will handle incoming multipart HTTP requests. By    *
+  * default as of v0.10, Sails uses                                          *
+  * [skipper](http://github.com/balderdashy/skipper). See                    *
+  * http://www.senchalabs.org/connect/multipart.html for other options.      *
+  *                                                                          *
+  * Note that Sails uses an internal instance of Skipper by default; to      *
+  * override it and specify more options, make sure to "npm install skipper" *
+  * in your project first.  You can also specify a different body parser or  *
+  * a custom function with req, res and next parameters (just like any other *
+  * middleware function).                                                    *
+  *                                                                          *
+  ***************************************************************************/
+
+    // bodyParser: require('skipper')({strict: true})
+
+  },
+
+  /***************************************************************************
+  *                                                                          *
+  * The number of seconds to cache flat files on disk being served by        *
+  * Express static middleware (by default, these files are in `.tmp/public`) *
+  *                                                                          *
+  * The HTTP static cache is only active in a 'production' environment,      *
+  * since that's the only time Express will cache flat-files.                *
+  *                                                                          *
+  ***************************************************************************/
+
+  // cache: 31557600000
+};

package/test/fixtures/v0.12-app/config/i18n.js

@@ -0,0 +1,57 @@
+/**
+ * Internationalization / Localization Settings
+ * (sails.config.i18n)
+ *
+ * If your app will touch people from all over the world, i18n (or internationalization)
+ * may be an important part of your international strategy.
+ *
+ *
+ * For more informationom i18n in Sails, check out:
+ * http://sailsjs.org/#!/documentation/concepts/Internationalization
+ *
+ * For a complete list of i18n options, see:
+ * https://github.com/mashpie/i18n-node#list-of-configuration-options
+ *
+ *
+ */
+
+module.exports.i18n = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Which locales are supported?                                             *
+  *                                                                          *
+  ***************************************************************************/
+
+  // locales: ['en', 'es', 'fr', 'de'],
+
+  /****************************************************************************
+  *                                                                           *
+  * What is the default locale for the site? Note that this setting will be   *
+  * overridden for any request that sends an "Accept-Language" header (i.e.   *
+  * most browsers), but it's still useful if you need to localize the         *
+  * response for requests made by non-browser clients (e.g. cURL).            *
+  *                                                                           *
+  ****************************************************************************/
+
+  // defaultLocale: 'en',
+
+  /****************************************************************************
+  *                                                                           *
+  * Automatically add new keys to locale (translation) files when they are    *
+  * encountered during a request?                                             *
+  *                                                                           *
+  ****************************************************************************/
+
+  // updateFiles: false,
+
+  /****************************************************************************
+  *                                                                           *
+  * Path (relative to app root) of directory to store locale (translation)    *
+  * files in.                                                                 *
+  *                                                                           *
+  ****************************************************************************/
+
+  // localesDirectory: '/config/locales'
+
+};

package/test/fixtures/v0.12-app/config/log.js

@@ -0,0 +1,29 @@
+/**
+ * Built-in Log Configuration
+ * (sails.config.log)
+ *
+ * Configure the log level for your app, as well as the transport
+ * (Underneath the covers, Sails uses Winston for logging, which
+ * allows for some pretty neat custom transports/adapters for log messages)
+ *
+ * For more information on the Sails logger, check out:
+ * http://sailsjs.org/#!/documentation/concepts/Logging
+ */
+
+module.exports.log = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Valid `level` configs: i.e. the minimum log level to capture with        *
+  * sails.log.*()                                                            *
+  *                                                                          *
+  * The order of precedence for log levels from lowest to highest is:        *
+  * silly, verbose, info, debug, warn, error                                 *
+  *                                                                          *
+  * You may also set the level to "silent" to suppress all logs.             *
+  *                                                                          *
+  ***************************************************************************/
+
+   level: 'verbose'
+
+};

package/test/fixtures/v0.12-app/config/models.js

@@ -0,0 +1,3 @@
+module.exports.models = {
+   migrate: 'drop'
+};

package/test/fixtures/v0.12-app/config/policies.js

@@ -0,0 +1,51 @@
+/**
+ * Policy Mappings
+ * (sails.config.policies)
+ *
+ * Policies are simple functions which run **before** your controllers.
+ * You can apply one or more policies to a given controller, or protect
+ * its actions individually.
+ *
+ * Any policy file (e.g. `api/policies/authenticated.js`) can be accessed
+ * below by its filename, minus the extension, (e.g. "authenticated")
+ *
+ * For more information on how policies work, see:
+ * http://sailsjs.org/#!/documentation/concepts/Policies
+ *
+ * For more information on configuring policies, check out:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.policies.html
+ */
+
+
+module.exports.policies = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Default policy for all controllers and actions (`true` allows public     *
+  * access)                                                                  *
+  *                                                                          *
+  ***************************************************************************/
+
+  // '*': true,
+
+  /***************************************************************************
+  *                                                                          *
+  * Here's an example of mapping some policies to run before a controller    *
+  * and its actions                                                          *
+  *                                                                          *
+  ***************************************************************************/
+	// RabbitController: {
+
+		// Apply the `false` policy as the default for all of RabbitController's actions
+		// (`false` prevents all access, which ensures that nothing bad happens to our rabbits)
+		// '*': false,
+
+		// For the action `nurture`, apply the 'isRabbitMother' policy
+		// (this overrides `false` above)
+		// nurture	: 'isRabbitMother',
+
+		// Apply the `isNiceToAnimals` AND `hasRabbitFood` policies
+		// before letting any users feed our rabbits
+		// feed : ['isNiceToAnimals', 'hasRabbitFood']
+	// }
+};

package/test/fixtures/v0.12-app/config/restoapi.js

@@ -0,0 +1,3 @@
+module.exports.restoapi = {
+  prefix: '/api/0.5/'
+};

package/test/fixtures/v0.12-app/config/restocore.js

@@ -0,0 +1,39 @@
+module.exports.restocore = {
+  project: "Test",
+  project_slug: "test",  
+  timeSyncBalance: 30, // seconds
+  timeSyncMenu: 5 * 60 , // seconds
+  timeSyncStreets: 12, // hours
+  images: {
+    adapter: 'imagemagick-local',
+    dish: {
+      format: 'png',
+      path: '/images',
+      resize: {
+        small: {
+          width: 200,
+          height: 200
+        },
+        large: {
+          width: 600
+        }
+      }
+    },
+    group: {
+      format: 'png',
+      path: '/imagesG',
+    }
+  },
+  development: true,
+  masterKey: 'test',
+  city: 'Xlan',
+  defaultName: "name",
+  defaultNumber: "77777777777",
+  timezone: 'Asia/Yekaterinburg',
+  timeSyncMap: 15 * 60, //seconds
+  checkType: 'native', //'rms',
+  groupShift: '',
+  rmsAdapter: '',
+  prefix: '/api/0.5/'
+
+};

package/test/fixtures/v0.12-app/config/routes.js

@@ -0,0 +1,49 @@
+/**
+ * Route Mappings
+ * (sails.config.routes)
+ *
+ * Your routes map URLs to views and controllers.
+ *
+ * If Sails receives a URL that doesn't match any of the routes below,
+ * it will check for matching files (images, scripts, stylesheets, etc.)
+ * in your assets directory.  e.g. `http://localhost:1337/images/foo.jpg`
+ * might match an image file: `/assets/images/foo.jpg`
+ *
+ * Finally, if those don't match either, the default 404 handler is triggered.
+ * See `api/responses/notFound.js` to adjust your app's 404 logic.
+ *
+ * Note: Sails doesn't ACTUALLY serve stuff from `assets`-- the default Gruntfile in Sails copies
+ * flat files from `assets` to `.tmp/public`.  This allows you to do things like compile LESS or
+ * CoffeeScript for the front-end.
+ *
+ * For more information on configuring custom routes, check out:
+ * http://sailsjs.org/#!/documentation/concepts/Routes/RouteTargetSyntax.html
+ */
+
+module.exports.routes = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Make the view located at `views/homepage.ejs` (or `views/homepage.jade`, *
+  * etc. depending on your default view engine) your home page.              *
+  *                                                                          *
+  * (Alternatively, remove this and add an `index.html` file in your         *
+  * `assets` directory)                                                      *
+  *                                                                          *
+  ***************************************************************************/
+
+  '/': {
+    view: 'homepage'
+  }
+
+  /***************************************************************************
+  *                                                                          *
+  * Custom routes here...                                                    *
+  *                                                                          *
+  * If a request to a URL doesn't match any of the custom routes above, it   *
+  * is matched against Sails route blueprints. See `config/blueprints.js`    *
+  * for configuration options and examples.                                  *
+  *                                                                          *
+  ***************************************************************************/
+
+};