The following is a good diagram of the various services running. Note, we can use infranodes to pull those cluster services from the compute nodes (things like registry, observability, monitoring, etc). Diagram from the docs.
jkeam
/ mad_roadshow_links.md
Last active
December 13, 2023 14:48
— forked from brandoncox/MAD Roadshow links
jkeam
/ odo-dotnet-demo.txt
Created
August 8, 2022 19:39
— forked from cvicens/odo-dotnet-demo.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Get odo for linux | |
| $ curl -OL https://mirror.openshift.com/pub/openshift-v4/clients/odo/v2.0.0/odo-linux-amd64 && mv odo-linux-amd64 odo && chmod u+x odo | |
| $ export PATH=$PATH:$(pwd) | |
| $ odo version | |
| # Use git to check out the .NET Core application | |
| $ git clone https://github.com/redhat-developer/s2i-dotnetcore-ex | |
| $ cd s2i-dotnetcore-ex/app | |
| $ git checkout dotnetcore-3.1 |
jkeam
/ gist:fdda2557ee2a28881f5a33356391f42c
Created
February 17, 2017 06:10
— forked from sebboh/gist:f1dfe4f096746c45f3e9ea06a09743a0
Installing a Gem on Heroku from a Private GitHub Repo
Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.
Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.
This method does not add your OAuth token to Gemfile.lock. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.
jkeam
/ gist:a8efc00c016b1f31f07aafb18a7fe9b1
Created
February 17, 2017 06:10
— forked from sebboh/gist:f1dfe4f096746c45f3e9ea06a09743a0
Installing a Gem on Heroku from a Private GitHub Repo
Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.
Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.
This method does not add your OAuth token to Gemfile.lock. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.