omarstreak

function extract(mv){
  //NodeIterators are really cool: https://developer.mozilla.org/en-US/docs/Web/API/NodeIterator
  var nodeIterator = document.createNodeIterator(
    mv.getBodyElement(),
    NodeFilter.SHOW_ELEMENT, 
    {
      acceptNode: function(node){
        //this is the main function where the interesting code occurs
        //because node iterator is a recursive tree walk you'll see every node below the body element
        //this includes nodes that contain both the html we want, and html we don't want

joewiz

On Tue Oct 27, 2015, history.state.gov began buckling under load, intermittently issuing 500 errors. Nginx's error log was sprinkled with the following errors:

2015/10/27 21:48:36 [crit] 2475#0: accept4() failed (24: Too many open files)

2015/10/27 21:48:36 [alert] 2475#0: *7163915 socket() failed (24: Too many open files) while connecting to upstream...

An article at http://www.cyberciti.biz/faq/linux-unix-nginx-too-many-open-files/ provided directions that mostly worked. Below are the steps we followed. The steps that diverged from the article's directions are marked with an *.

1. * Instead of using su to run ulimit on the nginx account, use ps aux | grep nginx to locate nginx's process IDs. Then query each process's file handle limits using cat /proc/pid/limits (where pid is the process id retrieved from ps). (Note: sudo may be necessary on your system for the cat command here, depending on your system.)
2. Added fs.file-max = 70000 to /etc/sysctl.conf

demisx

Provider	Singleton	Instantiable	Configurable
Constant	Yes	No	No
Value	Yes	No	No
Service	Yes	No	No
Factory	Yes	Yes	No
Decorator	Yes	No?	No
Provider	Yes	Yes	Yes

Constant

mikermcneil

// To disable socket.io, disable the sockets hook (you'll have to disable the pubsub hook as well)
// This is a replacement for the default app.js file:

require('sails').lift({
  hooks: {
    sockets: false,
    pubsub: false
  }

IlanFrumer

app.directive("uiSrefParams", function($state) {
  return {
    link: function(scope, elm, attrs) {
      var params;
      params = scope.$eval(attrs.uiSrefParams);
      return elm.bind("click", function(e) {
        var button;
        if (!angular.equals($state.params, params)) {
          button = e.which || e.button;
          if ((button === 0 || button === 1) && !e.ctrlKey && !e.metaKey && !e.shiftKey) {

uhho

# Load balancer configuration
upstream exampleApp {
    # Directs to the process with least number of connections.
    least_conn;

    # One failed response will take a server out of circulation for 20 seconds.
    server 127.0.0.1:10080 fail_timeout=20s;
    #server 127.0.0.1:10081 fail_timeout=20s;
    #server 127.0.0.1:10082 fail_timeout=20s;
    #server 127.0.0.1:10083 fail_timeout=20s;

erikflowers

.ul-inline-no-style() {
  margin: 0px;
  list-style: none;
  .clearfix;
  li {
    float: left;
    display: block;
  }
}

CMCDragonkai

AngularJS Directive Attribute Binding Explanation

When using directives, you often need to pass parameters to the directive. This can be done in several ways. The first 3 can be used whether scope is true or false. This is still a WIP, so validate for yourself.

1. Raw Attribute Strings

   <div my-directive="some string" another-param="another string"></div>

jamarparris

The MIT License (MIT)
Copyright (c) 2013 Jamar Parris

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE S

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---