Help the adoption of Going Buildless by frontend developers, regardless of frameworks or libraries they use.
Make the most valuable tools related to Going Buildless easy to discover, use and contribute to.
@open-wc has become an umbrella project which consists of lots of parts mixed in the same repo and docs site:
| @echo off | |
| REM Make sure that the path to the script is correct! | |
| @bash -l -c "~/bin/gitkraken-wsl-bash.sh %*" |
ⓘ This list is not meant to be exhaustive and is not guaranteed to be maintained. See the comments for updates and alternative options.
(Items in bold indicate possible concerns)
| Keycloak | WSO2 Identity Server | Gluu | CAS | OpenAM | Shibboleth IdP | |
|---|---|---|---|---|---|---|
| OpenID Connect/OAuth support | yes | yes | yes | yes | yes | yes |
| Multi-factor authentication | yes | yes | yes | yes | yes | yes |
| Admin UI | yes | yes | yes | yes | yes | no |
| OpenJDK support | yes | yes | partial² | yes |
Europe
Updated: 2022-07
I wrote the first edition of this as a guide for myself at the end of 2017 - it was a mashup of Pi-Hole + PiVPN scripts and an IPsec script installed within a separate Raspian Docker image... and it actually worked!
But things have come a long way, and WireGuard happened - I've since streamlined and simplified my setup into a single Docker Compose script.
The steps below assume the following:
Last updated March 13, 2024
This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.
Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.
For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.
This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.
Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,
| /** @jsx h */ | |
| // You only need custom elements for this!!! | |
| import 'skatejs-web-components/src/native-shim'; | |
| import { Component, define, h, prop } from 'skatejs'; | |
| import ShadowNode, { scopeCss, scopeTree } from './shadow-node'; | |
| // Converts real DOM nodes into Incremental DOM nodes. | |
| // | |
| // This is orthogonal to this gist, but makes it so we can distribute real |
