-
A database for 2022 (hn) (Tailscale uses SQLite)
-
I'm all-in on server-side SQLite (hn) (Fly.io acquires Litstream)
apiVersion: v1 | |
kind: Namespace | |
metadata: | |
labels: | |
app.kubernetes.io/instance: ingress-nginx | |
app.kubernetes.io/name: ingress-nginx | |
name: ingress-nginx | |
--- | |
apiVersion: v1 | |
automountServiceAccountToken: true |
<?php | |
namespace App\Http\Controllers\Slack; | |
use App\Slack\Webhook; | |
use App\Http\Controllers\Controller; | |
use Illuminate\Http\Request; | |
use Illuminate\Support\Facades\Log; |
# Used on Ubuntu 18.04 and 20.04 | |
# Find instructions for other OSes here: https://certbot.eff.org/instructions | |
# Install Certbot via Snaps | |
sudo snap install core; sudo snap refresh core | |
sudo snap install --classic certbot | |
sudo ln -s /snap/bin/certbot /usr/bin/certbot | |
# Install DNS CloudFlare plugin | |
sudo snap set certbot trust-plugin-with-root=ok |
If you've ever wanted to create an oAuth style application with Microsoft, you might have felt this pain before.
In true Enterprise Microsoft Fashion™, there's a lot going on.
This will be a bit long because of that. I hope I haven't missed anything (but I'm sure I have)!
We'll be using PHP (Laravel in my case).
<? | |
// | |
// AUTO KEYWORD-BASED FOLLOWER CURATION BOT (by @levelsio) | |
// | |
// File: twitterFollowerCuratorBot.php | |
// | |
// Created: May 2021 | |
// License: MIT | |
// |
#!/usr/bin/env bash | |
### | |
## This mounts a (single) ephemral NVMe drive in an EC2 server. | |
## It's meant to be run once, within user-data | |
## For EBS drives (non-ephemeral storage), see: https://gist.github.com/jalaziz/c22c8464cb602bc2b8d0a339b013a9c4 | |
# | |
Each query in MySQL is running as its own transaction, assuming you didn't change this default configuration, and unless you're starting a transaction manually and running multiple deletes in that one transaction.
Because every query is a transaction, MySQL has to save the data being deleted in case of a rollback. Large deletes means saving a TON of data for that potential case.
Additionally, deletes cause a LOT of writes to the binary log. When the delete completes, the query/results of the delete are committed to the binary log,
# Nomad 0.12.0+ requires volumes to be enabled | |
# within the client configuration | |
plugin "docker" { | |
config { | |
volumes { | |
enabled = true | |
} | |
} | |
} |
The pipeline could use a selection of pre-set features.
- Give the pipeline more polish by allowing users to "build" their pipeline (preset items they can run)
- Make Chipper feel more integrated with services such as AWS, Forge, Envoyer, Vapor
- Make it easier to script more complex items such as conditional actions, or creating build artifacts
It might be nice to have a way to have icons for each as well - PHP, NodeJS, Composer, Dusk, Vapor, etc etc etc.