stenuto

#!/bin/bash

# Function to display usage information
usage() {
    echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]"
    exit 1
}

# Check if at least one argument (input file) is provided
if [ $# -lt 1 ]; then

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} * {...}

virattt

mangiucugna

- 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} * {...}

ifeulner

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).

It is assumed that the cluster creation is already done, e.g. via terraform scripts provided by the great kube-hetzner project.

Initial configuration

koakh

**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;

giggio

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

marshki

#!/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
#

silversillu

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();

karamanbk