Alik Aslanyan In-line

Let's say you have a SysV Init Script named foo

Copy the file to /etc/init.d/foo
Enable the SysV service: chkconfig --add foo
Enable the SysV service: chkconfig foo on
Start the service: service foo start. After this, systemd-sysv-generator will generate this file /run/systemd/generator.late/foo.service, copy this file to /etc/systemd/system by running: cp /run/systemd/generator.late/foo.service /etc/systemd/system/foo.service
Edit /etc/systemd/system/foo.service by running systemctl edit foo.service, add in the following line to foo.servie (this makes the service installable)

[Install]

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

	<?php

	/**
	* Class Bezier
	*
	* @package nstdio\svg\util
	* @author Edgar Asatryan <[email protected]>
	*/
	class Bezier
	{

	# On slow systems, checking the cached .zcompdump file to see if it must be
	# regenerated adds a noticable delay to zsh startup. This little hack restricts
	# it to once a day. It should be pasted into your own completion file.
	#
	# The globbing is a little complicated here:
	# - '#q' is an explicit glob qualifier that makes globbing work within zsh's [[ ]] construct.
	# - 'N' makes the glob pattern evaluate to nothing when it doesn't match (rather than throw a globbing error)
	# - '.' matches "regular files"
	# - 'mh+24' matches files (or directories or whatever) that are older than 24 hours.
	autoload -Uz compinit