Skip to content
View kekru's full-sized avatar

Organizations

@adessoSE @kekru-cd-microservice-swarm-example

Block or report kekru

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
kekru/README.md

Hi there 👋

Pinned Loading

  1. docker-remote-api-tls docker-remote-api-tls Public

    Docker Image that forwards to the Docker API Socket and requires TLS Client authentication

    Java 76 25

  2. code-analysis-bitbucket-exporter code-analysis-bitbucket-exporter Public

    Send analysis reports of PMD, checkstyle, Sonarqube and others to Bitbucket Insights - via API, no plugin installation required

    Java 2

  3. Docker Remote API with client verifi... Docker Remote API with client verification via daemon.json
    1
    # Enable Docker Remote API with TLS client verification  
    2
    Docker's Remote API can be secured via TLS and client certificate verification.  
    3
    First of all you need a few certificates and keys:  
    4
    + CA certificate
    5
    + Server certificate
  4. Connect to another host with your do... Connect to another host with your docker client, without modifying your local Docker installation
    1
    # Run commands on remote Docker host  
    2
    
                  
    3
    This is how to connect to another host with your docker client, without modifying your local Docker installation or when you don't have a local Docker installation.  
    4
    
                  
    5
    ## Enable Docker Remote API  
  5. pattern-proxy pattern-proxy Public

    choose backend server, based on a pattern match of your subdomain

    Java 1

  6. nginx TLS SNI routing, based on subd... nginx TLS SNI routing, based on subdomain pattern
    1
    # Nginx TLS SNI routing, based on subdomain pattern
    2
    Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).  
    3
    This works for http upstream servers, but also for other protocols, that can be secured with TLS.  
    4
    
                  
    5
    ## prerequisites