mysticaltech

- I need your answer to be precise, it’s crucial you get them right, I am counting on you!
- You always think step by step, break down the problem into intermediate steps and communicate to the user which steps you took in order to answer their query
- If you think you need to execute more steps in order to answer the query, ask the user for confirmation and run more steps
- Always provide a detailed explanation for your response, including the underlying reasoning and any relevant sources to support your answer.
Use this format to answer:
```
**Answer**: {answer}
**Internal monologue**: {why you answered this way, how you broke down the problem in steps and your train of thought}
**What other questions you might ask**: {what kind of followup questions you expect from me? What did I miss?}
**Sources**: * {source1} {confidence score about source1, 1 to 10} * {source2} {confidence score about source2, 1 to 10} * {...}

mysticaltech

version: '3.7'
services:
  dockerregistrymirror:
    container_name: docker-registry-mirror
    image: registry:2
    ports:
      - "443:443"
    volumes:
      - ./data/docker/var/lib/registry:/var/lib/registry
      - ./data/certs:/certs

mysticaltech

Longhorn best practices

The following settings are provided as an example how longhorn should be configured in a production cluster, especially if it is deployed on Hetzner Cloud infrastructure.

Hetzner server nodes provide local storage and allow up to five attached volumes (with a size of up to 10TiB each) Local storage is provided by NVMe storage and therefore is much faster than the attached volumes, but limited in size (max 300GiB usable).

Initial configuration

Also you want to control the nodes that are used for storage. So it is suggested to set the option Create default disk only on labeled node to true

mysticaltech

if ( typeof(jQuery) === 'function' ) {
    jQuery(document).ready(function($) {
        jQuery.fn.extend({
            getPath: function() {
                var path, node = this;
                while (node.length) {
                    var realNode = node[0],
                        name = realNode.localName;
                    if (!name) break;
                    name = name.toLowerCase();

mysticaltech

**As a developer you have complete control over the signup and signin functionality...**

```shell
$ surreal sql --conn http://localhost:8000 --user root --pass root --ns test --db test
```

```sql
-- optional : this is the default see --ns test --db test start server flags
-- USE NS test DB test;

mysticaltech

1/ Install nfs-utils

sudo dnf install nfs-utils

2/ Enable the needed services

sudo systemctl enable rpcbind
sudo systemctl enable nfs-server
sudo service rpcbind start
sudo service nfs-server start

mysticaltech

#!/usr/bin/env bash
#
# mirror_mirror
#
# One-way Rsync mirror of data from source to destination.
#
# Author: M. Krinitz <mjk235 [at] nyu [dot] edu>
# Date: 2020.04.20
# License: MIT
#

mysticaltech

from matplotlib import use

from pylab import *
from scipy.stats import beta, norm, uniform
from random import random
from numpy import *
import numpy as np
import os

# Input data

mysticaltech

#!/usr/bin/env python
# Inspired by: https://www.youtube.com/watch?v=izG7qT0EpBw
# The CRC values are verified using: https://crccalc.com/

def reflect_data(x, width):
    # See: https://stackoverflow.com/a/20918545
    if width == 8:
        x = ((x & 0x55) << 1) | ((x & 0xAA) >> 1)
        x = ((x & 0x33) << 2) | ((x & 0xCC) >> 2)
        x = ((x & 0x0F) << 4) | ((x & 0xF0) >> 4)

mysticaltech

Basically, to make it work and have it resolve DNS queries, you need to disable systemd-resolved as it monopolizes the /etc/resolv.conf file, more about this process here https://fedoraproject.org/wiki/Changes/systemd-resolved.

sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved
sudo bash -c 'mkdir -p /etc/systemd/system-preset && echo "disable systemd-resolved.service" >/etc/systemd/system-preset/20-systemd-resolved-disable.preset'

Then reboot, and don't worry it is normal that you do not have internet at that point. We need to delete an old symlink left over from systemd-resolved operations. 

rm /etc/resolv.conf