tmckayus

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

cfergeau

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

markbates

name: Release
on:
  release:
    types:
      - published

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

siddhesh

// 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();

anjannath

package main

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

sarahbx

Bootstrap Prompt: SDLC Agent Framework

Use this file as a prompt to Claude to scaffold the full SDLC agent framework in a new project. Copy the section below "--- BEGIN PROMPT ---" as your first message to Claude in the new project.

Customization points (before you run the prompt):

1. REQUIREMENTS.md — Replace the four requirements with your project's non-negotiable rules. The structure (ID, rationale, enforcement matrix) should be kept; the content is yours.
2. settings.json — Adjust the ask/deny permission lists to match your tech stack and tooling (e.g., swap uv for npm, add your cloud CLI).
3. LESSONS.md — Starts empty for a new project. The format is established; sessions fill it.
4. PERSONALITY.md / CYNEFIN.md / role files — These are framework-level and rarely need changes. Only modify if you have a principled reason.