purwandi purwandi

##Chrome Packaged Apps

Introduction

Introduced at Google I/O 2012, Chrome packaged apps are a new way to develop apps that are running 'natively' within Chrome on the desktop as well as on Chrome mobile in the near future. I'm currently in the middle of a project where I develop a Chrome packaged app and in this article I would like to share my experience with the development of packaged apps.

Please note: This article should give you a basic insight of topics that I think are helpful to know for developing packaged apps. Furthermore I will give links to each topic, so you can dive deeper into that specific topic if you want to. It's not the goal of this article to act as a complete introduction to Chrome packaged apps, for a much more detailed overview of packaged apps development, please look at the official packaged app documentation.

What are Chrome Packaged Apps

Chrome packaged apps are applic

Prerequisites : the letsencrypt CLI tool

This method allows your to generate and renew your Lets Encrypt certificates with 1 command. This is easily automatable to renew each 60 days, as advised.

You need nginx to answer on port 80 on all the domains you want a certificate for. Then you need to serve the challenge used by letsencrypt on /.well-known/acme-challenge. Then we invoke the letsencrypt command, telling the tool to write the challenge files in the directory we used as a root in the nginx configuration.

I redirect all HTTP requests on HTTPS, so my nginx config looks like :

server {

Let's Encrypt on Ubuntu 14.04, nginx with webroot auth

This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.

As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).

Configuration

For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:

Intro

This is a basic collection of things I do when setting up a new headless ubuntu machine as a webserver. Following the steps below should give you a reasonable secure server with HTTP/2 support (including ALPN in chrome) and the fast NGINX server. I am happy to add things so leave a comment.

Basics

After creating the server (droplet on DigitalOcean) log in with

Switching to DNS over TLS on macOS

How to configure your Mac to use DNS over TLS in five easy steps:

Install Stubby with Homebrew (https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Daemon+-+Stubby):
```
 brew install stubby
```
Edit the configuration file:

	# start/stop/restart atmail
	/etc/init.d/atmailserver start
	/etc/init.d/atmailserver stop
	/etc/init.d/atmailserver restart

	# count of messages in queue
	/usr/local/atmail/mailserver/bin/exim -bpc

	# list of messages in queue
	/usr/local/atmail/mailserver/bin/exim -bp

	var Browser = require('zombie'),
	url = require('url'),
	fs = require('fs'),
	$q = require('Q'),
	saveDir = __dirname + '/_snapshots';


	var scriptTagRegex = /<script\b[^<](?:(?!<\/script>)<[^<])*<\/script>/gi;

	var stripScriptTags = function(html) {

	#!/bin/bash

	curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.26.1/install.sh \| bash
	. ~/.nvm/nvm.sh
	nvm install 0.12
	nvm alias default 0.12
	npm config set cache-min 86400
	npm config set cache /cache/node_modules/
	npm install -g gulp
	npm install

	# Before Tests
	before_script:
	- bash ci/docker_install.sh > /dev/null
	- composer self-update
	- composer install --prefer-dist > /dev/null
	- cp .env.gitlab .env
	- php artisan key:generate
	- php artisan migrate:refresh

	# Services

	1) Install cloudflared using homebrew:

	brew install cloudflare/cloudflare/cloudflared

	2) Create /usr/local/etc/cloudflared/config.yaml, with the following content

	proxy-dns: true
	proxy-dns-upstream:
	- https://1.1.1.1/dns-query
	- https://1.0.0.1/dns-query