A design language for premium, dark-themed knowledge interfaces.
"Numbers are heroes, labels are whispers."
| "custom/window-state": { | |
| "exec": "~/.config/waybar/scripts/window-state.sh", | |
| "interval": 1, | |
| "format": "{text}", | |
| "return-type": "json", | |
| }, |
| import numpy as np | |
| import cv2 | |
| def color(img): | |
| imageFrame = cv2.resize(img, (0, 0), None, 0.2, 0.2) | |
| # Convert the imageFrame in | |
| # BGR(RGB color space) to | |
| # HSV(hue-saturation-value) | |
| # color space |
| #!/bin/bash | |
| # Generate self-cert certificates for Docker socket. I have tried many tutorials including http://tech.paulcz.net/2016/01/secure-docker-with-tls/ | |
| # None worked... So I took the official steps from Docker docs - https://docs.docker.com/engine/security/https/ and placed them | |
| # in a script. Please ensure that you replace the IP addresses/DNS names denoted in X with IP's and hostnames you wish to allow | |
| # to connect with your daemon, normally 127.0.0.1 is always required and the hostname of your server. If you have a coreos cluster | |
| # placing IP's and hostnames of each node maybe preferable over creating unique certs for each node. | |
| # This script does not cover the steps for copying your certs to the relevant locations, as per the following document - https://docs.docker.com/engine/security/https/ | |
| # 1. In our production setup we copy server.key, server-cert.pem and ca-cert.pem to /etc/docker/ssl | |
| # 2. Client certs(ca.pem,cert.pem,key.pem) are copied to user dir in our case user core - /home/core/.docker/ |
| env: | |
| TERM: xterm-256color | |
| window: | |
| dimensions: | |
| columns: 80 | |
| lines: 24 | |
| padding: | |
| x: 2 |
| const puppeteer = require('puppeteer'); | |
| (async () => { | |
| const browser = await puppeteer.launch(); | |
| const page = await browser.newPage(); | |
| await page.goto('https://news.ycombinator.com', {waitUntil: 'networkidle2'}); | |
| await page.pdf({path: 'hn.pdf', format: 'A4'}); | |
| await browser.close(); | |
| })(); |
| Parse.Cloud.beforeSave(Parse.Installation, function(request, response) { | |
| var androidId = request.object.get("androidId"); | |
| if (!androidId) { | |
| console.warn("No androidId found, save and exit"); | |
| return response.success(); | |
| } | |
| var query = new Parse.Query(Parse.Installation); | |
| query.equalTo("androidId", androidId); | |
| query.ascending("createdAt"); |
| //First: get the ANDROID_ID | |
| String android_id = Settings.Secure.getString(this.getContentResolver(), Settings.Secure.ANDROID_ID); | |
| Parse.initialize(this, "APP_ID", "CLIENT_KEY"); | |
| //Now: add ANDROID_ID value to your Installation before saving. | |
| ParseInstallation.getCurrentInstallation().put("androidId", android_id); | |
| ParseInstallation.getCurrentInstallation().saveInBackground(); |
| Telerik Platform | SashiDo and Parse Server |
|---|---|
| Cloud Code for Data | Triggers |
| Cloud Functions | Cloud Functions |
| Scheduled Jobs | Cloud Jobs |
| Stored Procedures | N/A |
| N/A | Webhooks |
| Telerik Platform | SashiDo and Parse Server |
|---|---|
| Type-Level permissions | Class-level permissions |
| Item-Level permissions | Object-Level access control |
| Roles content type | Role collection |
| Users content type | User collection |
| Devices content type | Installation collection |
| Relations | Relations and Pointers |
| Images | Images |