The NixOS flake and Home Manager were setup following this tutorial
# From root dir of the configuration
$ ls
catsnvim configuration.nix flake.lock flake.nix hardware-configuration.nix home.nix
To add nixCats to Home Manager...
The NixOS flake and Home Manager were setup following this tutorial
# From root dir of the configuration
$ ls
catsnvim configuration.nix flake.lock flake.nix hardware-configuration.nix home.nix
To add nixCats to Home Manager...
| version: "3" | |
| services: | |
| restate-1: | |
| <<: *defaults | |
| ports: | |
| - target: 8080 | |
| published: 80 | |
| protocol: tcp | |
| mode: host |
| (* A straightforward adaptation of the Java code for the Scanner in the book Crafting Interpreters, by Robert Nystrom | |
| Original Java code can be found here : https://github.com/munificent/craftinginterpreters/blob/master/java/com/craftinginterpreters/lox/Scanner.java *) | |
| type token = | |
| | LeftParen | |
| | RightParen | |
| | LeftBrace | |
| | RightBrace | |
| | Comma | |
| | Dot |
from PyPDF2 import PdfWriter, PdfReader
reader = PdfReader('Elixir in Action.pdf')
writer = PdfWriter()
A4_WIDTH = 7.36
A4_HEIGHT = 9.23
page = reader.pages[0]| (ns com.yakread.report.dashboards | |
| (:require [com.biffweb :as biff] | |
| [clojure.string :as str] | |
| [cheshire.core :as cheshire])) | |
| (defn debug [x] | |
| [:pre (with-out-str (biff/pprint x))]) | |
| ;; slight modification of clojure.core/distinct | |
| (defn distinct-by |
https://julialang.org/downloads/
or via package manager :
sudo apt install julia
Download the XKB configuration for bqn here, and place it whith the other layouts:
curl https://raw.githubusercontent.com/mlochbaum/BQN/master/editors/bqn
cp bqn /usr/share/X11/xkb/symbols/Add an entry for BQN in evdev.xml
Postgres 15 is just out, and while there is a lot to love about this new release, you're in for a surprise if you try to set it up with Django following tutorials like this one.
The reason is stated in the release announcement:
Remove PUBLIC creation permission on the public schema (Noah Misch) The new default is one of the secure schema usage patterns that Section 5.9.6 has recommended...
Provided your web app doesn't access your database as a superuser (it shouldn't) and uses a dedicated user, it is not allowed to use the public schema anymore. You have to create one for this specific user, and the next section will