env GOOS=target-OS GOARCH=target-architecture go build package-import-path
# Example
env GOOS=darwin GOARCH=amd64 go build
env GOOS=darwin GOARCH=amd64 go build main.go
env GOOS=darwin GOARCH=amd64 go build github.com/zoo/york/foo/bar
<?xml version='1.0' ?> | |
<!-- | |
Why is this one giant script instead of a bunch of smaller scripts? | |
Mostly this comes down to BuildGraph and personal preference. As the language BuildGraph isn't | |
really much of a programming language there is no easy way to use an IDE and jump between | |
includes, find usages of variables, and just generally quickly search things. It was found to | |
be easier to have a single large file that a developer can quickly jump up and down in when | |
trying to understand what the BuildGraph script is doing. |
Descrizione verticale delle fasi con traduzione in inglese:
I'm trying to follow this guide to install NixOS
using Btrfs
, LUKS
and LVM
. The main usage of this page for me will be remembering what I did! My laptop is ASUS ROG GL553VD
.
Just downloaded Plasma Desktop, 64bit and create a bootable Flash Drive. Then boot up to NixOS Live CD. Using gparted to create two partitions, One 200MB vfat EFI partittion and the rest of SSD drive will be an encrypted partition.
DISK=/dev/nvme0n1
First attempt at NixOS installation and configuration.
Ssetup is similar to the gist where Void Linux was installed.
With NixOS the following features are listed:
import warnings | |
from urllib3.exceptions import NotOpenSSLWarning | |
warnings.filterwarnings("ignore", category=NotOpenSSLWarning) | |
import subprocess | |
import requests | |
import urllib.parse | |
import json | |
import os | |
from datetime import datetime |
HCT is a color model developed by [Google][material-hct]. It aims to solve a problem related to generating color palettes with good contrast. While HCT may seem like a revolutionary color model, the idea behind it is quite simple, take the perceptually uniform color model CAM16 and combine it with the CIE Lab's lightness.
_ _ _ ____ _ _ | |
| | | | __ _ ___| | __ | __ ) __ _ ___| | _| | | |
| |_| |/ _` |/ __| |/ / | _ \ / _` |/ __| |/ / | | |
| _ | (_| | (__| < | |_) | (_| | (__| <|_| | |
|_| |_|\__,_|\___|_|\_\ |____/ \__,_|\___|_|\_(_) | |
A DIY Guide | |
version: '2' | |
services: | |
redis: | |
image: redis:alpine | |
container_name: redis_db | |
command: redis-server --appendonly yes | |
ports: | |
- 6379:6379 | |
volumes: |
This guide will walk you through creating a custom MCP (Model Context Protocol) server that integrates with Claude Code, allowing you to extend Claude's capabilities with external tools, APIs, or even other AI models.
MCP (Model Context Protocol) is a protocol that allows Claude to communicate with external servers to access tools and capabilities beyond its built-in features. Think of it as a plugin system for Claude.