A minimal HTTP server in python. It sends a JSON Hello World for GET requests, and echoes back JSON for POST requests.
python server.py 8009
Starting httpd on port 8009...
curl http://localhost:8009
{"received": "ok", "hello": "world"}
A minimal HTTP server in python. It sends a JSON Hello World for GET requests, and echoes back JSON for POST requests.
python server.py 8009
Starting httpd on port 8009...
curl http://localhost:8009
{"received": "ok", "hello": "world"}
upstream transmission { | |
server 127.0.0.1:9091; #Transmission | |
} | |
server { | |
listen 443 ssl http2; | |
server_name example.com; | |
auth_basic "Server Restricted"; | |
auth_basic_user_file /var/www/myWebSite/web/.htpasswd; | |
# Path to the root of your installation |
Below you is my build instructions for GnuPG 2.1.20 released on 03-Apr-2017. These instructions are built for a headless Ubuntu 16.04 LTS server.
Or if you wish, you may use the install script to install GnuPG 2.1.20 by entring the following:
curl -sL "https://gist.github.com/mattrude/3883a3801613b048d45b/raw/install-gnupg2.sh" |sh
apt-get -y install libgnutls-dev bzip2 make gettext texinfo gnutls-bin \
/var/lib/lxc/mycontainer/config
$HOME/.local/share/lxc/mycontainer/config
lxc.mount
directive, that follows the format below. Substitute proper paths as necessary:
lxc.mount.entry = /path/to/folder/on/host /path/to/mount/point none bind 0 0
So you want to create a pex that packages your script and its dependencies?
Ok - first to make our script! Call it foo.py:
import requests
if __name__ == '__main__':
req = requests.get("https://raw.githubusercontent.com/pantsbuild/pex/master/README.rst")
print req.text.split("\n")[0]
These use separate document structures instead of HTML, some are more modular libraries than full editors
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with 7668
lines of CSS (and just 2 !important
).
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
sensor: | |
- platform: rest | |
resource: http://api.luftdaten.info/v1/sensor/1777 | |
value_template: > | |
{% if value_json is sequence %} | |
{% set sensor = value_json | last %} | |
{% else %} | |
{% set sensor = value_json %} | |
{% endif %} | |
{% for sdv in sensor.sensordatavalues %} |
/* Semantic UI has these classes, however they're only applicable to*/ | |
/* grids, containers, rows and columns.*/ | |
/* plus, there isn't any `mobile hidden`, `X hidden` class.*/ | |
/* this snippet is using the same class names and same approach*/ | |
/* plus a bit more but to all elements.*/ | |
/* see https://github.com/Semantic-Org/Semantic-UI/issues/1114*/ | |
/* Mobile */ | |
@media only screen and (max-width: 767px) { | |
[class*="mobile hidden"], |