If you need to build, make images, code, etc. try using https://arena.ai/ its totally free and you can build some valuable assets or apps and just transfer to whatever you are coding with. It can save you a lot of money.

Been playing with Odysseus, a project by PewDiePie, and I finally got it running on my own VM under my own subdomain. Really fun seeing a self-hosted AI workspace come alive on infrastructure I control myself. Chat, tools, research, memory, documents, the whole thing feels like having a personal AI environment instead of relying entirely on someone else’s platform. I setup this up using VScode with Copilot to ssh into the vm and build the project for me and setup my subdomain. The manual steps only involve changing some dns records in my domain registrar for the subdomain.

Hey fam!! First off, I want to say this community means a lot to me and I've been thinking about it a LOT lately. I just reactivated this group and I'm coming back in HOT with a ton of energy and stuff to share. Let me catch you up on what I've been deep in... I literally spend HOURS every single day, and I mean every day, living and breathing AI, automation, affiliate marketing, content creation, and online business. This isn't a hobby for me, this is life. I work from my RV, my wife and I travel the Southwest, and my "office" is wherever we park. That freedom? That's exactly what this group is about. Profitz 2 Freedom. Here's some of what I've been building and experimenting with lately: AI AGENTS - I've been going deep on building and deploying AI agent systems. We're talking full automation pipelines, agents that can research, write, post, and manage workflows without me babysitting them. The tools available right now are absolutely insane if you know how to use them AI VIDEO - Using tools like Google Veo and other AI video generators to create content at scale. I run 100+ YouTube channels as an affiliate marketer and AI video has completely changed the game for content production speed. WEB APPS AND AUTOMATION - Building on Google Cloud, Vercel, using OpenRouter API to plug in the best AI models, GitHub for version control. I'm in the terminal daily building real stuff. Python, JavaScript, bash scripts, all of it. ECOMMERCE AND RESELLING - Still doing eBay flips, trading cards, and keeping my eye on marketplace opportunities. Old school hustle meets new school tools. AFFILIATE MARKETING - Always testing new funnels, new traffic strategies, new offers across platforms like ClickBank and others. The landscape keeps changing and I keep adapting. I stay up to date on EVERYTHING. Claude updates, OpenAI drops, Google AI news, new models coming out. I'm tracking it all daily so I can bring you what matters. But here's the thing. I don't want this to just be ME posting. I want to hear from YOU.

This lesson shows you how to build a simple but reliable 24/7 YouTube livestream stack without turning your laptop into the permanent broadcast machine. The core idea is straightforward: 1. Use your main computer as the operator workstation. 2. Use a small Linux VM as the always-on runtime. 3. Prebuild the heavy media assets before you stream. 4. Let FFmpeg handle the broadcast. 5. Let PM2 keep the long-running processes alive. If you copy this architecture, you will get a setup that is easier to restart, easier to debug, and much harder to break accidentally. ## What You Are Building By the end of this guide, you will have: - A local operator machine for setup, media prep, and manual control. - A lightweight Linux VM for the live runtime. - A Node.js app that prepares the loop, manages the stream state, and runs helper services. - An FFmpeg broadcast pipeline that can update overlays without a full restart. - A PM2 process model that keeps the stream services alive across crashes and reboots. ## Recommended Architecture Use this split: - Operator workstation: Build media assets, run manual maintenance actions, inspect logs, and deploy updates. - Linux VM: Run the always-on stream, chat responder, and health reporting. Why this matters: - Heavy browser automation and media generation are bursty workloads. - 24/7 broadcasting needs stable, boring, repeatable workloads. - Those are not the same job, so do not force them onto the same box. ## Minimum Stack Install or prepare these pieces: - Node.js 20+ - FFmpeg - PM2 - Git - OpenSSH - A Linux VM with Ubuntu 22.04 or similar - A YouTube channel enabled for live streaming - A Telegram bot or another alerting destination if you want health summaries Recommended VM size: - 2 vCPU - 1 to 4 GB RAM - Enough disk for logs plus generated loop assets ## Folder Layout Use a layout like this: ```text your-project/ src/ live/ stream.js chatResponder.js healthReporter.js overlayControl.js scripts/ start-live.sh deploy-live.ps1