mohamedmansour

using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using Microsoft.AspNetCore.Html;
using Newtonsoft.Json;

namespace HtmlHelpers
{
    /// <summary>

aeris

# Licence : AGPLv3+
# rule:[Privacy]
if anyof (
        address :is :domain "From" "gmail.com",
        address :is :domain "From" "live.com",
        address :is :domain "From" "msn.com",
        address :is :domain "From" "hotmail.com",
        address :is :domain "From" "hotmail.fr",
        address :is :domain "From" "yahoo.com",
        address :is :domain "From" "yahoo.fr"

hardware

#######################
## GENERALS SETTINGS ##
#######################

smtpd_banner         = $myhostname ESMTP $mail_name (Debian/GNU)
biff                 = no
append_dot_mydomain  = no
readme_directory     = no
delay_warning_time   = 4h
mailbox_command      = procmail -a "$EXTENSION"

barryo

auth_mechanisms = plain login
!include auth-sql.conf.ext

plentz

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

Thermionix

auth_basic              "Restricted";
auth_basic_user_file    /etc/nginx/htpasswd;

mikeygee

<!-- using the truncate filter -->
{% for post in site.posts limit:10 %}
   <h2><a href="{{ post.url }}">{{ post.title }}</a></h2>
   <span class="post-date">{{ post.date | date: "%B %d, %Y" }}</span>
   {% if post.content.size > 2000 %}
      {{ post.content | truncatewords: 300 }} <!-- bad! content gives you rendered html and you will truncate in the middle of a node -->
      <a href="{{ post.url }}">read more</a>
   {% else %}
      {{ post.content }}
   {% endif %}

CristinaSolana

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

mtigas

Client-side SSL

For excessively paranoid client authentication.

---

Updated Apr 5 2019:

because this is a gist from 2011 that people stumble into and maybe you should AES instead of 3DES in the year of our lord 2019.

some other notes: