Overview MoneyPrinter V2 includes a built-in CRON scheduler (src/cron.py) that enables fully automated content generation and posting. Schedule your YouTube Shorts and Twitter posts to run at specific intervals without manual intervention.
How Scheduling Works The CRON script accepts three key parameters:
Purpose : Which platform to post to (twitter or youtube)Account UUID : Which account to use for postingOllama Model : Which LLM model to use for content generation
The script then:
Retrieves account configuration from cache
Generates content using the specified LLM model
Posts/uploads to the target platform
Logs the operation for monitoring
Setting Up CRON Jobs Prerequisites Before scheduling automated tasks:
Configure at least one account (see Account Setup )
Note the account UUID (visible when selecting accounts)
Install and configure Ollama with at least one model
Test manual posting to ensure everything works
CRON Job Syntax Basic CRON syntax:
┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday) │ │ │ │ │ * * * * * command to execute
Common Schedule Examples
0 * * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter YOUR_UUID llama3.2:3b
Runs at the start of every hour (e.g., 1:00, 2:00, 3:00)
0 * /6 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py youtube YOUR_UUID llama3.2:3b
Runs every 6 hours (e.g., 00:00, 06:00, 12:00, 18:00)
Twice daily (morning and evening)
0 9,21 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter YOUR_UUID mistral
Runs at 9:00 AM and 9:00 PM every day
Once daily at specific time
30 14 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py youtube YOUR_UUID llama3.2:3b
Runs every day at 2:30 PM
Business hours only (Mon-Fri, 9am-5pm)
0 9-17 * * 1-5 cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter YOUR_UUID phi3
Runs every hour from 9 AM to 5 PM, Monday through Friday
0 10 * * 6,7 cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py youtube YOUR_UUID llama3.2:3b
Runs at 10:00 AM on Saturdays and Sundays The Twitter automation flow:
Loads account configuration from cache
Initializes Twitter automation with Firefox profile
Generates tweet content using Ollama
Posts tweet to Twitter/X
Command structure: python src/cron.py twitter < ACCOUNT_UUI D > < OLLAMA_MODE L >
Example: # Post a tweet every 2 hours 0 * /2 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter 660e9500-f39c-52e5-b827-557766551111 llama3.2:3b
YouTube Scheduling The YouTube automation flow:
Loads account configuration from cache
Initializes YouTube automation with Firefox profile
Generates video script using Ollama
Creates video with TTS and visuals
Uploads video to YouTube Shorts
Command structure: python src/cron.py youtube < ACCOUNT_UUI D > < OLLAMA_MODE L >
Example: # Upload a YouTube Short twice daily 0 10,18 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py youtube 550e8400-e29b-41d4-a716-446655440000 llama3.2:3b
YouTube Shorts generation can take several minutes. Avoid scheduling too frequently to prevent overlapping jobs.
Implementation Guide Linux/macOS Setup
Find your account UUID: python src/main.py # Select Twitter Bot or YouTube Shorts Automater # Note the UUID from the accounts table
Open crontab editor:
Add your scheduled jobs: # Twitter bot - posts every 3 hours 0 * /3 * * * cd /home/user/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter YOUR_TWITTER_UUID llama3.2:3b >> /tmp/mpv2_twitter.log 2>&1 # YouTube - uploads daily at 2 PM 0 14 * * * cd /home/user/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py youtube YOUR_YOUTUBE_UUID llama3.2:3b >> /tmp/mpv2_youtube.log 2>&1
Save and exit (in vim: :wq, in nano: Ctrl+X then Y)
Verify scheduled jobs:
Windows Setup Task Scheduler (GUI)
Command Line (schtasks)
Open Task Scheduler (search in Start Menu)
Click “Create Basic Task”
Name: “MPV2 Twitter Bot” (or similar)
Trigger: Choose frequency (Daily, Weekly, etc.)
Action: “Start a program”
Program: Path to Python in your venv
C:\Users\YourName\MoneyPrinterV2\venv\Scripts\python.exe
Arguments:
src/cron.py twitter YOUR_UUID llama3.2:3b
Start in: Path to MoneyPrinterV2 directory
C:\Users\YourName\MoneyPrinterV2
Finish and enable the task
# Twitter bot every 3 hours schtasks / create / tn "MPV2_Twitter" / tr "C:\Users\YourName\MoneyPrinterV2\venv\Scripts\python.exe src/cron.py twitter YOUR_UUID llama3.2:3b" / sc hourly / mo 3 / st 00 : 00 / sd 01 / 01 / 2026 # YouTube daily at 2 PM schtasks / create / tn "MPV2_YouTube" / tr "C:\Users\YourName\MoneyPrinterV2\venv\Scripts\python.exe src/cron.py youtube YOUR_UUID llama3.2:3b" / sc daily / st 14 : 00 / sd 01 / 01 / 2026
Best Practices Frequency Recommendations
Twitter Recommended: 3-8 times per dayAvoid posting more than once per hour to prevent spam flags.
YouTube Shorts Recommended: 1-3 times per dayVideo generation takes time. Space uploads at least 6 hours apart.
Logging and Monitoring Add logging to your CRON jobs for debugging:
# Append stdout and stderr to log files 0 * /3 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter UUID MODEL >> /var/log/mpv2_twitter.log 2>&1
Monitor logs regularly:
# View recent Twitter bot logs tail -f /var/log/mpv2_twitter.log # View recent YouTube automation logs tail -f /var/log/mpv2_youtube.log
Error Handling The CRON script includes basic error handling:
Missing UUID : Exits with error messageAccount not found : Exits gracefullyOllama model not specified : Exits with error
Consider adding email notifications for failures:
# Send email on failure (requires mailutils) 0 * /3 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter UUID MODEL || echo "MPV2 Twitter job failed" | mail -s "CRON Failure" [email protected]
Environment Considerations When running scheduled jobs, ensure:
Virtual environment is activated
Working directory is set to project root
Environment variables (like GEMINI_API_KEY) are available
Firefox profiles are accessible
No conflicting manual operations are running
Multiple Account Scheduling You can schedule different accounts at different times:
# Account 1: Tech content, posts every 4 hours 0 * /4 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter UUID_1 llama3.2:3b # Account 2: Finance content, posts every 6 hours with 2-hour offset 0 2,8,14,20 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py twitter UUID_2 mistral # Account 3: Gaming YouTube, uploads daily at 3 PM 0 15 * * * cd /path/to/MoneyPrinterV2 && source venv/bin/activate && python src/cron.py youtube UUID_3 llama3.2:3b
Troubleshooting
Check:
Verify CRON service is running: systemctl status cron (Linux)
Check crontab syntax: crontab -l
Review system logs: grep CRON /var/log/syslog
Ensure absolute paths are used
Job runs but fails silently
Solution:
Add output redirection: >> /tmp/mpv2.log 2>&1
Check log file for error messages
Test command manually from terminal
Verify virtual environment activation
Firefox profile conflicts
Solution:
Ensure Firefox is not running when CRON job executes
Use separate Firefox profiles for different accounts
Check file permissions on profile directories
Solution:
Verify model is installed: ollama list
Check model name spelling in CRON command
Ensure Ollama service is running: systemctl status ollama
Solution:
Verify UUID in cache files: .mp/twitter.json or .mp/youtube.json
UUIDs are case-sensitive - copy exactly as shown
Ensure cache files have correct permissions
Testing Your Schedule Before setting up production schedules, test manually:
# Navigate to project directory cd /path/to/MoneyPrinterV2 # Activate virtual environment source venv/bin/activate # Linux/macOS # or venv\Scripts\activate # Windows # Test Twitter posting python src/cron.py twitter YOUR_TWITTER_UUID llama3.2:3b # Test YouTube upload python src/cron.py youtube YOUR_YOUTUBE_UUID llama3.2:3b
If manual execution works, the scheduled version should work too.
Advanced Scheduling Dynamic Model Selection Rotate between different models for variety:
# Morning posts use llama3.2:3b 0 9 * * * python src/cron.py twitter UUID llama3.2:3b # Evening posts use mistral 0 21 * * * python src/cron.py twitter UUID mistral
Rate Limiting Preventing platform rate limits:
# Stagger posts across the day 0 9,12,15,18,21 * * * python src/cron.py twitter UUID llama3.2:3b
Conditional Execution Run only during specific conditions:
# Only run if internet connection is available * /30 * * * * ping -c1 google.com > /dev/null && cd /path/to/MPV2 && python src/cron.py twitter UUID MODEL
Next Steps
Configuration Settings Optimize settings for scheduled operations
Account Management Manage multiple accounts for scheduling
