In Raku, Lists can be constructed several ways.
# A list of strings: "one", "two", "three"
my @x = <one two three>;
# Using << >> allows interpolating variables
my $num = "six";
my @y = << four five $six >>;
package xmpp | |
import ( | |
"context" | |
"encoding/xml" | |
"fmt" | |
"io" | |
"log" | |
"os" | |
"os/exec" |
packer { | |
required_plugins { | |
lxd = { | |
version = ">=1.0.0" | |
source = "github.com/hashicorp/lxd" | |
} | |
} | |
} | |
variable "buildkite_token" {} |
#!/usr/bin/env raku | |
use v6.d; | |
# mention: | |
# priorities | |
# resource-based lb | |
my @gat-ids = [ | |
(Q |Overprovisioning factor|, "https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/overprovisioning"), | |
]; |
The CI runs in an LXD container. That container technology is more VM-like than Docker/OCI containers. For instance, you can easily run Docker containers inside LXD. That's why I like using it for CI.
The LXD container is built from a Packer file and scripts. That Packer file is here on my git server:
# Kakoune | |
set verbose mode (good for learning) | |
`:set -add global autoinfo normal` | |
## Movement | |
### Goto | |
`10g` - go to line 10 |
I was searching for an alternative and landed on this Stack Exchange question. There are a few good suggestions there.
But I don't have enough reputation on that site to answer. 🤷
TL;DR, a possible alternative is "shibboleth".
I like Go a lot, but I'm looking for a more powerful tool for organizing my projects. Here's some of the things I could hopefully do in Meson if we added support
Download the cue cli tool and follow along
When CUE is exported to JSON, every value in every (processed) file is unified into one giant object.
% echo 'name: "Vlad"' > /tmp/name.cue
% echo 'disposition: "cheerful"' > /tmp/disposition.cue
| Name | Type | Default | Example | Description | | |
| :--- | :--- | :--- | :--- | :--- | | |
| rules | array | n/a | | A list of rules to compare to the incoming request. Rules are checked in order of appearance in the list. | | |
| rules.key | string | n/a | "Authorization" | The key to check in the incoming request | | |
| rules.location | enum\[header, cookie, queryString, metadata\] | header | cookie | The location to check for the specified key/value pair | | |
| rules.location | enum\[header, cookie, queryString, metadata\] | header | cookie | The locati | |
on to check for the specified key/value pair | | |
| rules.metadataFilter | string | "" | "gm.oidc-authentication" | The name of the filter to read dynamic metadata from. Required if rules.location=metadata | | |
| rules.enforce | bool | false | true | Whether to completely reject the request if a rule doesn't match | | |
| rules.enforceResponseCode | string | 403 | 500 | The status code to send back if a rule does not match and `enforce` is true. | |