Icanhazip

GET https://major.io/index.json

[
  {
    "content": "We use Vertex AI at work for accessing Anthropic’s models and the opencode setup is quite smooth! Although getting your authentication credentials from Google can be a little tricky, using them with opencode involves setting a few environment variables.\nSetting up Vertex AI Before you point opencode at Vertex AI, you need a few things on the GCP side.\nPrerequisites A GCP project with the Vertex AI API enabled IAM permissions for the Claude models (your account needs the aiplatform.endpoints.predict permission, or a broader role like Vertex AI User) Either a service account key or Application Default Credentials (ADC) Authentication You have two main options here. The easiest for local development is ADC:\ngcloud auth application-default login This stores credentials locally and opencode picks them up automatically.\nIf you’re using a service account (common in enterprise setups where your org provisions access), point to the key file:\nexport GOOGLE_APPLICATION_CREDENTIALS=/path/to/your-service-account.json Environment variables Set these in your shell profile or session:\nexport ANTHROPIC_VERTEX_PROJECT_ID=your-gcp-project-id export GOOGLE_CLOUD_PROJECT=your-gcp-project-id export GOOGLE_APPLICATION_CREDENTIALS=/path/to/your-service-account.json # if not using ADC You can also set VERTEX_LOCATION if you need a specific region, but the global endpoint is the default. It routes to the nearest available region.\nUsing opencode You don’t need to configure opencode at all! It finds the environment variables and takes care of the rest for you.\nYou can type /models, press enter, and you should see the list of available models from Vertex AI. From there, use CTRL-F to select any favorites that you use often.\nTroubleshooting If you don’t see any models, double check the environment variables to ensure they are set in your terminal session. You may need to open a new terminal or source your shell profile to pick up the new variables.\nYou can also run opencode models --refresh to force a refresh of the model list from Vertex AI.\n",
    "permalink": "https://major.io/p/vertex-ai-anthropic-opencode/",
    "summary": "Opencode makes it easy to use Anthropic’s Claude models through  Google’s Vertex AI platform.",
    "title": "Using Anthropic's models via Vertex AI in opencode"
  },
  {
    "content": "Porkbun does exactly what I need and nothing more. I came to them a few years ago with domains scattered across a few different registrars that were quickly becoming too difficult to manage. Their site has minimal upselling, quick renewals, and self-servicing your domains is easy. 🐷\nI’m always on the hunt for ways to automate all of my infrastructure, so I set out to build some Porkbun automation. However, many of the python modules for Porkbun only did certain things, such as just DNS or just buying domains. I wanted the whole thing: domain pricing, DNS, DNSSec management. Everything.\nLet’s dig into the code. 👨‍💻\nImportant note: None of these projects are affiliated with Porkbun in any way. They’re just passion projects from someone who really enjoys using their service! oinker 🐖 My initial project is oinker. It’s a simple Python client (async-first, but sync is there, too) that helps you manage all aspects of your Porkbun account in a type-safe and Pythonic way.\nHere’s a quick example:\nfrom oinker import AsyncPiglet, ARecord async with AsyncPiglet() as piglet: # List DNS records records = await piglet.dns.list("example.com") for record in records: print(f"{record.record_type} {record.name} -> {record.content}") # Create an A record await piglet.dns.create( "example.com", ARecord(content="1.2.3.4", name="www") ) There’s a lot more you can do with it! The documentation covers lots of examples and has an extensive set of API reference material, too.\nporkbun-mcp 🤖 LLMs are all around us these days, right? Sometimes I like to talk to Claude via opencode about my DNS records. This gets handy when I’m struggling to find out why one of my kubernetes services isn’t responding and it’s due to a missing DNS record.\nThere’s porkbun-mcp for that! You can chat with LLMs about your DNS records to get advice, troubleshoot problems, or just create records on the go.\nCheck the getting started docs to configure porkbun-mcp in your favorite MCP client or LLM tool.\noctodns-porkbun 🐙 Finally, there’s octodns-porkbun for those who manage DNS as code with octoDNS. This provider plugin uses oinker under the hood and supports all the record types you’d expect.\nIf you’re already using octoDNS to manage DNS across multiple providers, this makes it easy to add Porkbun to the mix.\nPull requests welcome! If you find a way to improve upon any of these projects, please let me know! You can always stop by one of the repos to open an issue, fix a bug, or add a feature!\n",
    "permalink": "https://major.io/p/love-for-porkbun/",
    "summary": "Porkbun has been a great DNS registrar for me and what better way to show my appreciation than to write some software! ❤️",
    "title": "Coding love for Porkbun"
  }
]