Myroslav diwms

🗺🐘 1000+ PostgreSQL EXTENSIONs

This is a list of URLs to PostgreSQL EXTENSION repos, listed in alphabetical order of parent repo, with active forks listed under each parent.

⭐️ >= 10 stars
⭐️⭐️ >= 100 stars
⭐️⭐️⭐️ >= 1000 stars
Numbers of stars might not be up-to-date.

Programming as Theory Building

Peter Naur

Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct

Tailwind CSS best practices

Utility classes

When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!
Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.
Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

Here's a step by step guide to convert a Virtualbox .ova to a Vagrant box.

List your VMs to find the VM id you want to convert:

$ VBoxManage list vms
"testing" {a3f59eed-b9c5-4a5f-9977-187f8eb8c4d4}

You can now package the .ova VM as Vagrant box:

	# yaml-language-server: $schema=https://raw.githubusercontent.com/kjellberg/mrsk/validate-with-json-schema/lib/mrsk/configuration/schema.yaml
	service: testexample
	image: githubuser/test/main
	servers:
	web:
	hosts:
	- 1.1.1.1
	labels:
	traefik.http.routers.web.rule: Host(`test.example.com`)
	traefik.http.routers.web_secure.entrypoints: websecure

	<?php
	declare(strict_types=1);

	use Doctrine\ORM\EntityManagerInterface;
	use ProxyManager\Factory\LazyLoadingValueHolderFactory;
	use ProxyManager\Proxy\VirtualProxyInterface;
	use Psr\Container\ContainerInterface;
	use Swoole\ArrayObject;
	use Swoole\Coroutine;

	module.exports = {
	theme: {
	extend: {
	screens: {
	light: { raw: "(prefers-color-scheme: light)" },
	dark: { raw: "(prefers-color-scheme: dark)" }
	}
	}
	},
	plugins: [

	<template>
	<div>
	<label v-if="label" class="form-label" :for="`date-input-${_uid}`">{{ label }}:</label>
	<input v-bind="$attrs" class="form-input" :id="`date-input-${_uid}`" :class="{ error: error }" type="text" ref="input" :value="value" @change="change" @keyup="change">
	<div v-if="error" class="form-error">{{ error }}</div>
	</div>
	</template>

	<script>
	import pikaday from 'pikaday'

	@setup
	require __DIR__.'/vendor/autoload.php';
	(new \Dotenv\Dotenv(__DIR__, '.env'))->load();

	$server = "spatie.be";
	$userAndServer = 'forge@'. $server;
	$repository = "spatie/spatie.be";
	$baseDir = "/home/forge/spatie.be";
	$releasesDir = "{$baseDir}/releases";
	$currentDir = "{$baseDir}/current";

	<?php
	/*
	\|--------------------------------------------------------------------------
	\| Remove Laravel Comments
	\|--------------------------------------------------------------------------
	\|
	\| Just made a new Laravel project, but don't want all those big
	\| comment blocks? Put this in the root of your project and run
	\| "php remove_laravel_comments.php"
	\|