philshem

real-time

The measurement data behind this page https://www.meteoswiss.admin.ch/home/measurement-values.html can be found as json format from these endpoints (includes geocoordinates for each measurement station, although seems not a valid geojson). To switch languages, replace en in the URL with de, fr or it.

Air temperature (10 minutes): https://data.geo.admin.ch/ch.meteoschweiz.messwerte-lufttemperatur-10min/ch.meteoschweiz.messwerte-lufttemperatur-10min_en.json

Precipitation (daily total, 10 minutes): https://data.geo.admin.ch/ch.meteoschweiz.messwerte-niederschlag-10min/ch.meteoschweiz.messwerte-niederschlag-10min_en.json

torarnv

#!/bin/bash

# Run in share directory, e.g. /volume1/foo

echo "Removing share '$1' without removing files..."
sudo synoshare --del FALSE $1

echo "Changing ownership of files..."
sudo chown -R $USER:users . *

c18s

## --- Docker Compose ---
version: '2'
services:
  acme.sh:
    image: neilpang/acme.sh                                                                                                                                                              container_name: acme.sh
    restart: always
    environment:
      - Namecom_Username=
      - Namecom_Token=
    volumes:

bl4ck5un

/* 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"],

mattsches

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 %}

idleberg

This list has been updated for Big Sur (and later). Since I don't use these versions, this guide might still need further improvements. For older macOS versions, please see this older revision.

Open in Sublime Text

• Open Automator
• Quick Action
• Set “Service receives selected” to files or folders in any application
• Add a Run Shell Script action
• Set the script action to /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl -n "$@"
• Set “Pass input” to as arguments

alekseykulikov

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:

• SUIT CSS naming conventions + SUIT CSS design principles;
• PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
• Flexbox is awesome. No need for grid framework;
• Normalize.css, base styles and variables are solid foundation for all components;

manigandham

Strictly Frameworks

• Mobiledoc - github.com/bustle/mobiledoc-kit - framework to build editors with a standardized JSON structure
• ShareDB - github.com/share/sharedb - framework to sync any JSON document using operational transforms, add real-time collaborative editing to anything else
• Bangle.dev - github.com/bangle-io/bangle.dev - toolkit built for building editors, based on prosemirror

Abstracted Editors

These use separate document structures instead of HTML, some are more modular libraries than full editors

simeonf

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]

julianlam

Exposing a directory on the host machine to an LXC container

1. Log into the container and create an empty directory, this will be the mount point
2. Log out and stop the container.
3. Open to your container's config file
   • For regular LXC containers: /var/lib/lxc/mycontainer/config
   • For unprivileged LXC containers: $HOME/.local/share/lxc/mycontainer/config
4. Add a new line above the 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

• Both of these paths are relative to the host machine.