thoroc

Awesome list of awesome project for local agentic workflow

List of projects that are somewhat related to opencode.

Model list

• https://models.dev

Running local models

fungiboletus

- name: Overprovision like the pros'
  hosts: all
  tasks:
    - name: Install early OOM killer and zram
      ansible.builtin.apt:
        pkg:
          - earlyoom
          - zram-tools
    - name: Configure early OOM killer
      ansible.builtin.lineinfile:

kukicado

const { spawn } = require('child_process');

const videoUrls = ["YOUR-TIKTOK-VIDEO-THAT-YOU-WANT-TO-DOWNLOAD"];

async function downloadVideo(videoUrl) {
  return new Promise((resolve, reject) => {
    const ytDlpProcess = spawn('yt-dlp', [videoUrl]);

    ytDlpProcess.stdout.on('data', (data) => {
      console.log(`yt-dlp stdout: ${data}`);

cpursley

PostgreSQL is Enough

• Simplify: move code into database functions
• Just Use Postgres for Everything
• Just use Postgres
• PostgreSQL is the worlds’ best database
• Postgres is eating the database world
• Hacker News discussion

Background and Cron Jobs

ih2502mk

Lecture 1: Introduction to Research — [📝Lecture Notebooks] [▶️Video]
Lecture 2: Introduction to Python — [📝Lecture Notebooks] [▶️Video]
Lecture 3: Introduction to NumPy — [📝Lecture Notebooks] [▶️Video]
Lecture 4: Introduction to pandas — [📝Lecture Notebooks] [▶️Video]
Lecture 5: Plotting Data — [📝Lecture Notebooks] [[▶️Vide

btahir

PARC6502

Backend as a Service

Note on sizes: a lot of those might be inaccurate as there might be many microservices required aside from the core release/docker image. I haven't tested these recently so I'm not sure

Supabase - ~94.9K stars

• Designed explicitly as an open source Firebase alternative
• Typescript based
• Docker support
• Full Postgres database with Realtime subscriptions

PocketBase - ~54.5K stars

indiesquidge

There are a myriad of benefits of smaller PRs with smaller line change deltas:

• easier for reviewers, not only in sheer amount of code to review, but also in the ability to provide useful feedback or start a discussion around different architecture patterns
• lower chances of bugs creeping in
• simpler to refactor and iterate upon
• encourages the code author to think more iteratively (e.g. what is the API I am trying to add right now? What will it look like when I'm done? Is what I'm doing extensible? Will it be suitable for future extensions, etc.)
• more synonymous with a CI flow; it is better to ship multiple small things that can easily be cherry-picked or reverted than it is to ship big PRs that are harder to debug and roll back

One pitfall to small PRs is people feeling like they can't move ahead or build on top of code that is up for review.

iMilnb

Rationale

This snippet is a sample showing how to implement CloudWatch Logs streaming to ElasticSearch using terraform. I wrote this gist because I didn't found a clear, end-to-end example on how to achieve this task. In particular, I understood the resource "aws_lambda_permission" "cloudwatch_allow" part by reading a couple of bug reports plus this stackoverflow post.

The js file is actually the Lambda function automatically created by AWS when creating this pipeline through the web console. I only added a endpoint variable handling so it is configurable from terraform.

bvis

pipeline {
    agent { node { label 'swarm-ci' } }

    environment {
        TEST_PREFIX = "test-IMAGE"
        TEST_IMAGE = "${env.TEST_PREFIX}:${env.BUILD_NUMBER}"
        TEST_CONTAINER = "${env.TEST_PREFIX}-${env.BUILD_NUMBER}"
        REGISTRY_ADDRESS = "my.registry.address.com"

        SLACK_CHANNEL = "#deployment-notifications"