There are several ways to clone a repository from github. Similar from other providers, such as bitbucket, gitlab, etc.
https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
Mostly, we use
- http
- ssh
| # ================================================================================================== | |
| # | |
| # NOTICE | |
| # | |
| # This gist is no longer maintained. It was moved to repo: | |
| # | |
| # https://github.com/maratori/golangci-lint-config | |
| # | |
| # Full history and all v2 releases are preserved in the repo. | |
| # |
There are several ways to clone a repository from github. Similar from other providers, such as bitbucket, gitlab, etc.
https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
Mostly, we use
| /** | |
| * Lib: JSON.ahk | |
| * JSON lib for AutoHotkey. | |
| * Version: | |
| * v2.1.3 [updated 04/18/2016 (MM/DD/YYYY)] | |
| * License: | |
| * WTFPL [http://wtfpl.net/] | |
| * Requirements: | |
| * Latest version of AutoHotkey (v1.1+ or v2.0-a+) | |
| * Installation: |
| ; How much height of screen size the terminal window takes. | |
| VRatio := 0.8 | |
| ; The path to the Windows Terminal exe file. | |
| WtPath = "%LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe" | |
| #SC29::ToggleTerminal() | |
| ShowAndPositionTerminal() | |
| { | |
| ScreenX := GetScreenLeft() |
This was created years ago; at the time I'd been a Shibboleth admin for nearly a decade but we needed something that could handle OIDC/OAuth and that explicitly supported OpenJDK. After a lot of investigation, I really liked Keycloak/Red Hat Single Sign-On. More details here: Gluu vs keycloack vs wso2 identity management
(Items in bold indicate possible concerns)
This has been updated to install Dashboard v2.0.0, see below for pre v2.0.0 instructions
Generate the kubeconfig file for your cluster using the Kubeconfig File button in the Cluster view of your cluster.
Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.
The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.
It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential
| package demo.plain; | |
| import org.keycloak.OAuth2Constants; | |
| import org.keycloak.admin.client.CreatedResponseUtil; | |
| import org.keycloak.admin.client.Keycloak; | |
| import org.keycloak.admin.client.KeycloakBuilder; | |
| import org.keycloak.admin.client.resource.RealmResource; | |
| import org.keycloak.admin.client.resource.UserResource; | |
| import org.keycloak.admin.client.resource.UsersResource; | |
| import org.keycloak.representations.idm.ClientRepresentation; |