VinayaSathyanarayana

#
# Auth filter /etc/fail2ban/filter.d/nginx-auth.conf:
#
# Blocks IPs that makes too much accesses to the server
#
[Definition]

failregex = ^<HOST> -.*"(GET|POST).*HTTP.*"

ignoreregex =

VinayaSathyanarayana

sudo -i


apt-get update
apt-get install \
  apache2-dev \
  autoconf \
  automake \
  build-essential \
  bzip2 \

VinayaSathyanarayana

// Model
var keystone = require('keystone'),
    Types = keystone.Field.Types;
 
// Set new model
var Example = new keystone.List('Example', {
    nocreate: true
});

// Set the fields of your model 

VinayaSathyanarayana

/**
* gulp file that will restart keystonejs app and compile sass
*/
'use strict';
var gulp = require('gulp');
var watch = require('gulp-watch');
var shell = require('gulp-shell')

var sass = require('gulp-sass');

VinayaSathyanarayana

var keystone = require('keystone');
var Types = keystone.Field.Types;

/**
 * Hybrid from the model from the example contact and from SydJS example
 */

/**
 * Reservation Model
 * =============

VinayaSathyanarayana

Home > Knowledge Base

1. What coding standard should I use when contributing to KeystoneJS?
2. How to Migrate from 0.2.x to 0.3.x|0.2.x-to-0.3.x
3. How to fix 'cannot overwrite model once compiled error' error when testing Keystone|Unregister-a-Mongoose-Model
4. How to Add Keystone to an Already Existing Express App
5. Helpful Gist on how to create RESTful APIs
6. How to Submit Documentation Translations
7. User Model Examples
8. [Deployment Checklist](https://github.com/keystonejs/keystone/wiki/Deploym

VinayaSathyanarayana

I've developed a useful feature in KeystoneJS that lets you populate a relationship from either side, while only storing the data on one side, and am looking for feedback on whether it is something that could / should be brought back into mongoose itself. (It might be possible to add as a separate package but I suspect there'd be too much rewriting of mongoose internals for that to be a good idea).

I've added this as an issue in mongoose for consideration: #1888 but am leaving this gist in place because the examples are easier to read.

I've used Posts and Categories as a basic, contrived example to demonstrate what I'm talking about here; in reality you'd rarely load all the posts for a category but there are other real world cases where it's less unreasonable you'd want to do this, and Posts + Categories is an easy way to demo it.

The problem

The built-in population feature is really useful; not just for

VinayaSathyanarayana

//One-to-Many
Post.model.find().where('author', author.id).exec(function(err, posts) {
     // ...
});

//Many-to-Many
Post.model.find().where('categories').in([category.id]).exec(function(err, posts) {
     // ...
});

VinayaSathyanarayana

var keystone = require('keystone'),
	// pull in the schemaPermissions lib
	// rootRequire is a custom function that fixes the path to always be from the root of the application
	schemaPermissions = rootRequire('lib/schemaPermissions'), 
	Types = keystone.Field.Types;

/**
 * Page Model
 * ==========
 */

VinayaSathyanarayana

const getRange = (start, end) => {
  let list = []
  if (start <= end) {
    for (let i = start; i <= end; i++)
      list.push(i)
  }
  return list
}

const RepeatableField = (fields, prefix) => ({