A containerized AI Toolkit setup with MCP (Model Context Protocol) integration for training LoRA models and fine-tuning diffusion models. This provides a complete solution for training custom LoRA models with full MCP integration, allowing AI assistants to manage the entire training workflow.
See the template repository for a complete example. Also includes the ComfyUI MCP Server used for creating images/videos from the trained models.
A containerized ComfyUI setup with MCP (Model Context Protocol) integration for AI-driven image generation workflows. Includes both standard MCP (stdio) access and HTTP API access.
See the template repository for a complete example. Also includes the model training mcp used for creating checkpoints / loras.
A complete implementation guide for integrating LaTeX document compilation with MCP (Model Context Protocol) servers, enabling AI assistants to create professional documents, academic papers, and typeset materials programmatically.
| package main | |
| import ( | |
| "flag" | |
| "log" | |
| "github.com/nats-io/nats-server/v2/server" | |
| nats "github.com/nats-io/nats.go" | |
| ) |
| # Install these packages (use your favorite AUR tool here) | |
| yay -S minikube-bin kubectl-bin docker-machine-driver-kvm2 libvirt qemu-headless docker-machine ebtables | |
| # Get libvirt going | |
| sudo systemctl enable libvirtd.service | |
| sudo usermod -a -G libvirt $(whoami) | |
| # This fix thanks to http://blog.programmableproduction.com/2018/03/08/Archlinux-Setup-Minikube-using-KVM/ | |
| sudo virsh net-autostart default |
| const axios = require('axios').default; | |
| function getAPIClient() { | |
| const axiosConfig = { | |
| baseURL: 'https://csrng.net/csrng/csrng.php', | |
| timeout: 5000, | |
| }; | |
| return axios.create(axiosConfig); | |
| } |
| @EnableConfigServer | |
| @SpringBootApplication | |
| @Import(SshLocationOverrideConfiguration.class) | |
| public class ConfigServerApplication { | |
| public static void main(String[] args) { | |
| SpringApplication.run(ConfigServiceApplication.class, args) | |
| .start(); //<-- THIS IS IMPORTANT! | |
| } | |
| } |
Some applications requires contacting HTTPS endpoints. In those cases you need to supply the CA certificates.
Most Nix applications won't package in the CA certificates, this is because they can make use of the OS provided CA certificate store.
The NixOS location for this is at: /etc/ssl/certs.
The OpenSSL library in Nixpkgs is compiled to use that path if there is no environment variables such as SSL_CERT_FILE.
