Praveen Kumar praveenkumar

## crcd-client.go
package main

import (
	"context"
	"fmt"
	"io/ioutil"
	"net"
	"net/http"
	"os"
	"time"

## GetMF.gs
// This code is in Public domain.

MF_SCHEME_NAME = 3;
MF_NAV = 4;
MF_DATE = 5;
CACHE_NAME = '_mfcache';

function initNAV() {
  var response = UrlFetchApp.fetch("http://portal.amfiindia.com/spages/NAVAll.txt");
  var txt = response.getContentText();

## github-workflows-goreleaser.yml
name: Release
on:
  release:
    types:
      - published

jobs:
  release:
    name: Release
    runs-on: ubuntu-latest

## README.md

      
              3 files
            
          
              0 forks
            
          
              0 comments
            
          
              2 stars
            
          
                cfergeau
                / README.md
            
            
              Last active
              January 13, 2020 08:05
            
          
    Dealing with expired certificates


Start the crc instance with the expired certificates (even if it's non-functional)
Download both scripts to the machine running the crc instance
Run fix-certs.sh
Once it successfully runs, the crc instance should become operational after a few minutes

Note: This script has been tested on linux and macos

  
## remote_crc.md

      
              1 file
            
          
              20 forks
            
          
              36 comments
            
          
              38 stars
            
          
                tmckayus
                / remote_crc.md
            
            
              Last active
              May 17, 2024 21:58
            
              
                Running 'crc' on a remote server
              
          
    Overview: running crc on a remote server

This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.
While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)
The instructions here were tested with F

  
## crc_remote_laptop.md

      
              1 file
            
          
              7 forks
            
          
              6 comments
            
          
              19 stars
            
          
                sub-mod
                / crc_remote_laptop.md
            
            
              Last active
              July 9, 2022 12:03
            
              
                Setup CodeReady Containers on Remote Server and connect from Laptop 4.2
              
          
    Following steps work for F29 for F31 look here
On the remote host

cat /etc/redhat-release
Fedora release 29 (Twenty Nine)

Install packages


## running_coredns_as_a_dns_server_in_a_container.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                robbmanes
                / running_coredns_as_a_dns_server_in_a_container.md
            
            
              Last active
              March 13, 2019 09:20
            
              
                Running CoreDNS as a DNS Server in a Container
              
          
  title
  published
  description
  tags
  
  
  Running CoreDNS as a DNS Server in a Container
  true
  How to manually configure CoreDNS to serve your own DNS zones and
  dns, coredns, container, docker
  
  
This article is published at:

dev.to

If you've ever needed to or wanted to set up your own DNS server, then this is for you. I recently found myself in possession of a Raspberry Pi, and instead of relying on my home router for DHCP and DNS, I decided to serve both from containers on the Pi, so I could resolve all of my hosts with their respective names when I VPN back to my network. I intended to have all other requests forwarded to another server that weren't in my local network, but still service local systems with my customized hostnames.

  
## operatorTalks.md

      
              1 file
            
          
              2 forks
            
          
              3 comments
            
          
              9 stars
            
          
                surajnarwade
                / operatorTalks.md
            
            
              Created
              January 25, 2019 06:03
            
              
                Talks related to Controllers & Operators
              
          
Writing a Custom Controller: Extending the Functionality of Your Cluster [I] - Aaron Levy(CoreOS): https://youtu.be/_BuqPMlXfpE
Writing Kube Controllers for Everyone - Maciej Szulik, Red Hat (Beginner Skill Level): https://youtu.be/AUNPLQVxvmw
Programming Kubernetes with the Go SDK [I] - Aaron Schlesinger, Deis: https://youtu.be/qiB4RxCDC8o
TGI Kubernetes 007: Building a Controller - Heptio: https://youtu.be/8Xo_ghCIOSY
TGI Kubernetes 008: Continuing the Controller - Heptio: https://youtu.be/fWkK-zsFtlU
TGI Kubernetes 009: Finishing the Controller - heptio: https://youtu.be/wqhKCiGsf1Y
Kubernetes Operators: Managing Complex Software with Software [I] - Josh Wood & Jesus Carrillo: https://youtu.be/cj5uk1uje_Y
Deep Dive: Operator Framework BoF - Diane Mueller & Sebastian Pahl, Red Hat: https://youtu.be/fu7ecA2rXmc


## startup-time-of-zsh.md

      
              1 file
            
          
              3 forks
            
          
              11 comments
            
          
              192 stars
            
          
                laggardkernel
                / startup-time-of-zsh.md
            
            
              Last active
              June 21, 2024 15:27
            
              
                Comparison of ZSH frameworks and plugin managers
              
          
    Comparison of ZSH frameworks and plugin managers

Changelog


update 1: add a FAQ section
update 2: benchmark chart and feature comparison table
update 3:

improve the table with missing features for antigen
new zplg times result


TLDR


## run.sh
# These have to be extracted from the qcow2 image
# TODO: Provide these via docker image?
KERNEL="vmlinuz-3.10.0-862.14.4.el7.x86_64"
INITRD="initramfs-3.10.0-862.14.4.el7.x86_64.img"

# This is where the magic happens
#
# To change the ignition (node type), you can use 'bootstrap', 'master' or 'worker'
# coreos.config.url=http://192.168.0.168:8080/bootstrap.ign
#
	package main

	import (
	"context"
	"fmt"
	"io/ioutil"
	"net"
	"net/http"
	"os"
	"time"
	// This code is in Public domain.

	MF_SCHEME_NAME = 3;
	MF_NAV = 4;
	MF_DATE = 5;
	CACHE_NAME = '_mfcache';

	function initNAV() {
	var response = UrlFetchApp.fetch("http://portal.amfiindia.com/spages/NAVAll.txt");
	var txt = response.getContentText();
	name: Release
	on:
	release:
	types:
	- published

	jobs:
	release:
	name: Release
	runs-on: ubuntu-latest
	# These have to be extracted from the qcow2 image
	# TODO: Provide these via docker image?
	KERNEL="vmlinuz-3.10.0-862.14.4.el7.x86_64"
	INITRD="initramfs-3.10.0-862.14.4.el7.x86_64.img"

	# This is where the magic happens
	#
	# To change the ignition (node type), you can use 'bootstrap', 'master' or 'worker'
	# coreos.config.url=http://192.168.0.168:8080/bootstrap.ign
	#