danShumway

99Designs

1-to-1 Project, Contest

description: Expert Designers Community serving Any industry, Any business. Design Logos, websites, and yes, even tattoos - there are so many (90+) categories.

AngelList

purwandi

Install Some Dependencies

apt-get install build-essential bzip2 libpcre3-dev libssl-dev mysql-server daemon libgeoip-dev

Installing Nginx with Naxsi Core

Download Nginx, Naxsi Core dan Naxsi UI. Saya berasumsi tempat download berada di /home/compile

0xjjpa

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job

marktheunissen

This playbook has been removed as it is now very outdated.

franck

###############################################################################
## Monit control file
###############################################################################
##
## Comments begin with a '#' and extend through the end of the line. Keywords
## are case insensitive. All path's MUST BE FULLY QUALIFIED, starting with '/'.
##
## Below you will find examples of some frequently used statements. For 
## information about the control file, a complete list of statements and 
## options please have a look in the monit manual.

timmyomahony

upstream uwsgi {
	ip_hash;
        server 127.0.0.1:40000;
}
server {

        listen                  80;
        server_name             www.domain.com;
        root                    /sites/mysite/;
        access_log              /sites/mysite/log/nginx/access.log;