Skip to content

Instantly share code, notes, and snippets.

@lloydchang
lloydchang / searxng.ts
Created December 13, 2024 06:50 — forked from ewired/searxng.ts
SearXNG MCP server
#!/usr/bin/env -S deno run --allow-net
/*
{
"mcpServers": {
"searxng": {
"command": "/path/to/deno",
"args": [
"run",
"--allow-net",
"/home/<YOUR USERNAME>/Documents/Cline/MCP/searxng.ts",
@lloydchang
lloydchang / openrouter.ts
Created December 13, 2024 07:49 — forked from ewired/openrouter.ts
OpenRouter MCP Server
#!/usr/bin/env -S deno run --allow-net --allow-env
/*
{
"mcpServers": {
"openrouter": {
"command": "/path/to/deno",
"args": [
"run",
"--allow-net",
"--allow-env",
@lloydchang
lloydchang / amazon.md
Created January 6, 2025 22:46 — forked from terabyte/amazon.md
Amazon's Build System

Prologue

I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/

It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.

The Question

Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?