-
Enable
#enable-devtools-experiments
flag inchrome://flags
section. -
Open Chorme Devtools and check
Settings > Experiments > Allow extensions to load custom stylesheets
. -
Create the following four files in a dedicated folder.
3.1.
devtools.html
<html> <head></head> <body><script src="devtools.js"></script></body>
#!/usr/bin/env sh | |
## update.sh - manage a OpenWRT LetsEncrypt https instalation | |
# HOWTO: | |
# - put update.sh in its own directory (like /root/.https) | |
# - run ./update.sh your.domain.com (that domain needs to point to your router) | |
# * this get an issued cert from letsencrypt.org using the webroot verification method | |
# * also installs curl and ca-certificates packages | |
# - use crontab -e; add the line `0 0 * * * "/root/.https/update.sh" >>/root/.https/log.txt 2>&` | |
# * this runs the update every day, logging everything to log.txt | |
# |
# files/env: | |
Defaults env_keep += "SSH_AUTH_SOCK" | |
# tasks/main.yml | |
- name: ensure sudo keeps SSH_AUTH_SOCK in environment | |
copy: src=env | |
dest=/etc/sudoers.d/env | |
mode=0440 | |
owner=root | |
group=root |
This set of commands is for setting up an open trip planner instance for New York City. OTP requires GTFS data and OSM streets data to build a graph, which it uses for trip planning.
Lucky for us, someone here dockerhub has left a nice CLI command to build the graph and run the container, but we need to get the data first.
The data are downloaded on the host machine. For me, this is a digitalocean droplet running ubuntu 14.
First, get GTFS for the New York City Subway from the MTA's downloads page: wget http://web.mta.info/developers/data/nyct/subway/google_transit.zip
Next, get OSM city extract for NYC. Thanks Mapzen! https://s3.amazonaws.com/metro-extracts.mapzen.com/new-york_new-york.osm.pbf
Finally, run the following docker command: docker run -it -v $(pwd):/var/otp/graphs opentripplanner/opentripplanner --build /var/otp/graphs --analyst
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
<!-- | |
EmojiOne Color SVGinOT Font | |
Author: Santiago Saavedra <[email protected]> | |
License: CC0 | |
Year: 2016 | |
Install: |
A week ago I was CC'd in on a thread about Linux packaging, and how to avoid doing it the wrong way (i.e. RPM, Deb, etc.). I've always used MojoSetup and I've never forced distributions to do any additional work, but this is still a new concept to a lot of people. Additionally, Amos suggested that I expand on Itch's FNA appendix, so here's a guide on how I package my games.
This is a bit of an expansion on my MAGFest 2016 presentation, which you can find here:
http://www.flibitijibibo.com/magfest2016/
https://www.youtube.com/watch?v=B83CWUh0Log
I would recommend looking at that first! After that, read on...
from time import sleep | |
from twisted.internet import reactor | |
from twisted.internet.defer import inlineCallbacks | |
from twisted.internet.task import deferLater | |
@inlineCallbacks | |
def a(): | |
yield deferLater(reactor, 1, lambda: None) # Now the blocking function is made async, we need to yield it. |
We need to PEPify a static format for writing down bootstrap information in Python source trees. The initial target is a list of PEP 508 package requirement strings. It's possible that in the future we might want to add more features like a build system backend specification (as in PEPs 516, 517), or an extension namespace feature to allow third-party developer tools (flit, pytest, coverage, flake8, etc.) to consolidate their configuration in this file in a systematic