Skip to content

Corporate Free Digital Platforms For Political Action

Why This Training Matters

In a world where political movements are increasingly captured by corporate software, this training builds the infrastructure for resistance. It protects organizing and distributes technical power to communities rather than extracting it for Silicon Valley.

Every person who completes this course can teach others. Every organization that deploys these tools achieves digital sovereignty. Every server we spin up is a small act of technological resistance.

The revolution will be self-hosted.

Let's get to work.

Condensed Training Outline

Duration: 3-4 weeks (6 sessions, 2 hours each)

Format: In-person preferred, hybrid possible

Class Size: 6-12 participants

Schedule: Flexible - can be delivered as 2 sessions/week over 3 weeks, or spread across 4 weeks

Total Hours: 12 hours of instruction + homework practice between sessions

Course Philosophy

This course teaches political actors how to escape the Political Industrial Complex by building their own digital infrastructure. Participants will learn to deploy corporate-free platforms that protect their organizing and distribute power to communities rather than extracting it for Silicon Valley.

We build, teach, and distribute the tools. Workers, with the right tools, will build the future. The medium is the message.

This training emphasizes Free and Open Source Software (FOSS) as the foundation for technological sovereignty. By learning to deploy, configure, and maintain FOSS applications, participants gain skills that transfer across platforms and create infrastructure that serves movements, not corporations.

Course Overview

This condensed format delivers the essential skills for digital sovereignty in 6 focused sessions:

Sessions 1-2: Foundation & Setup - Theory, hardware selection, Linux installation - Terminal basics, SSH, first containerized applications

Sessions 3-4: Building Your Stack - FOSS ecosystem exploration, deploy Nextcloud & Bookstack - Automation with n8n, backups & security

Sessions 5-6: Communication & Completion - Newsletter system with Listmonk, complete signup workflows - Capstone presentations, teaching others, future paths

What's Different from the Full Course: This condensed version focuses on core self-hosting skills and omits advanced topics like local AI deployment, which can be covered in follow-up workshops or advanced sessions.

Prerequisites

Recommended: Digital Security Culture facilitation (1 session, 2 hours) Required: Willingness to learn, basic computer literacy, commitment to weekly practice

Learning Outcomes

By the end of this course, participants will be able to: - Articulate why corporate software is politically compromising - Set up and maintain a basic server running Linux - Deploy containerized FOSS applications from the community - Navigate and utilize FOSS resources (Awesome lists, linuxserver.io, GitHub) - Build automation workflows for organizing tasks - Deploy a self-hosted newsletter system - Train others in their organization on these tools - Make informed decisions about digital infrastructure


Session One: Theory, Hardware & Getting Started

Duration: 2 hours Format: Discussion and hands-on introduction

Part 1: Introduction & Political Context (30 min)

Quick Introductions: - Name, pronouns, organization - One corporate software tool you hate and why

The Political Industrial Complex: - How corporate software extracts wealth from movements - Case studies: deplatforming, surveillance, corporate complicity - FOSS alternative: owning your infrastructure

Key Concepts: - Free Software vs. Open Source - Self-hosting vs. cloud - What we're building: Newsletter, forms, automation, file storage - Live demo of what participants will build by week 4

Part 2: Hardware & Material Reality (30 min)

Digital is Physical: - "The cloud" is just someone else's computer - Your server: what you need and why

Hardware Options: - Old laptop (free, built-in battery backup) - Mini PC (Intel NUC, Beelink - efficient, purpose-built) - Raspberry Pi 5 (low power, great for learning)

Hardware Assessment: - Quick evaluation of devices participants brought - Requirements: 8GB RAM minimum, ethernet connection, 24/7 capability - Shopping list for missing components

Part 3: Linux Installation Demonstration (45 min)

Why Linux?: - Freedom, security, community, cost

Live Demo - Installing Ubuntu Server: - Creating bootable USB - Boot process and BIOS settings - Installation walkthrough (facilitator demonstrates on one machine) - Initial configuration: user, network, security basics - Basic commands: ls, cd, pwd, apt update

Troubleshooting Time: - Help participants who brought devices get started - Common issues addressed

Part 4: Setting Expectations & FOSS Resources (15 min)

What to Expect: - This is challenging but achievable - We learn by doing - By Session 6, you'll have your own infrastructure

FOSS Resources Overview: - Awesome Lists: https://github.com/awesome-selfhosted/awesome-selfhosted - LinuxServer.io: Pre-built containers - GitHub as the commons

Collective Agreements: - Ask questions freely - Help each other - Confidentiality about organizing work - Commit to practice between sessions

Homework:

  • Complete Ubuntu Server installation on your device
  • Get server online and accessible from your network
  • Practice basic terminal commands (ls, cd, pwd, mkdir)
  • Read: "If you do politics who is reading your secrets"
  • Inventory: List all software your organization uses and who owns it
  • Browse https://github.com/awesome-selfhosted/awesome-selfhosted for 20 minutes

Session Two: Terminal, SSH & Containerization

Duration: 2 hours Format: Highly technical, hands-on

Part 1: Terminal Basics & SSH (40 min)

Terminal Essentials: - Why the command line matters - Navigation: cd, ls, pwd - File operations: mkdir, touch, cp, mv, rm - Viewing files: cat, less - System info: df, free, htop

SSH Setup: - What is SSH and why it matters - Install SSH server: sudo apt install openssh-server - Generate SSH keys on client machine - Copy public key to server: ssh-copy-id - Test connection and disable password authentication - Now you can access your server from anywhere on your network

Part 2: Git Basics (15 min)

Version Control Quick Start: - What is Git? Version control for files - Git vs GitHub: protocol vs platform - Install: sudo apt install git - Clone a repository (we'll use this to deploy apps) - Why this matters: most FOSS apps are distributed via Git

Part 3: Docker & Containerization (55 min)

Understanding Containers: - Containers are reproducible, isolated environments - When you subscribe to SaaS, you're renting a container on their server - We're going to run the same containers on our server

Docker Installation: - Install Docker Engine - Add user to docker group - Test: docker run hello-world

Deploy Your First Real Application: - Pull a simple web server: docker run -d -p 8080:80 nginx - Access it in your browser - View logs: docker logs [container-id] - Stop and remove: docker stop, docker rm

Real Organizing Tool - Budibase (Forms/Database): - Introduction to docker-compose.yml - Deploy Budibase: docker-compose up -d - Access the application - Create a simple form - Discussion: We just deployed enterprise software that would cost $25+/month - Our cost: $0 (running on infrastructure we own)

Part 4: Wrap-up (10 min)

What We Just Did: - You now have a server you can access remotely - You deployed your first application in a container - You have the foundation to deploy any FOSS software

Homework:

  • SSH into your server daily and practice commands
  • Deploy one additional container from Docker Hub (suggestions provided)
  • Read: Docker documentation basics
  • Browse: https://hub.docker.com/ and https://fleet.linuxserver.io/
  • Document: Screenshot your running containers

Session Three: The FOSS Ecosystem & Application Discovery

Duration: 2 hours Format: Exploration and hands-on deployment

Part 1: The FOSS Commons (25 min)

FOSS Philosophy & Practice: - The four freedoms: use, study, modify, distribute - How FOSS is built: volunteers, cooperatives, foundations - Why FOSS matters for movements: sovereignty, transparency, community

The FOSS Ecosystem: - Awesome Lists: https://github.com/awesome-selfhosted/awesome-selfhosted - LinuxServer.io: Community-maintained Docker containers - GitHub/GitLab: Where FOSS lives

Quick Scavenger Hunt: - Find FOSS alternatives to Google Docs, Zoom, Slack, Trello - Share discoveries: What could your organization replace today?

Part 2: Deploy Two Key Applications (70 min)

Understanding LinuxServer.io: - Consistent container format, excellent documentation - Browse https://fleet.linuxserver.io/ - Reading docs: environment variables, volumes, ports

Application 1: Nextcloud (File Storage & Collaboration): - Why: Replace Google Drive/Dropbox - Deploy using docker-compose - Set up first user - Upload files, explore Calendar, Contacts, Deck apps - This is your organizing cloud

Application 2: Bookstack (Documentation/Wiki): - Why: Document organizing, create playbooks, share knowledge - Deploy from linuxserver.io container - Initial configuration - Create a sample page about your organization - Group discussion: How would you use this?

Part 3: Documentation & Planning (25 min)

Reading FOSS Documentation: - GitHub README files are your first stop - Understanding environment variables and volumes - Finding help: GitHub issues, forums

Troubleshooting Practice: - Quick demonstration of debugging a broken deployment - Reading logs: docker logs [container-name] - Checking configs

Plan Your Stack: - What does your organization need? - Map corporate tools to FOSS alternatives - Prioritize deployment order - Share ideas with the group

Homework:

  • Deploy one additional application from the Awesome list
  • Document your setup (screenshots, commands, problems solved)
  • Read: "Revolution & Likes"
  • Think about repetitive tasks you want to automate (next session)

Session Four: Automation & Workflows

Duration: 2 hours Format: Practical automation projects

Part 1: Automation as Liberation (20 min)

Discussion: - What is "bullshit work" in your organizing? - Data entry, email follow-ups, social media posting - Automation frees organizers for relationship-building - Corporate alternative: Zapier ($20+/month) - FOSS alternative: n8n (self-hosted, powerful, free)

The Vision: - Organizers spend time door knocking, not email sorting - Systems handle routine tasks - Technology serves people, not capital

Part 2: Deploy & Learn n8n (50 min)

What is n8n?: - Visual workflow automation platform - Self-hosted, integrates with nearly everything

Deployment: - Docker compose for n8n - Initial configuration - Understanding the interface (nodes and connections)

Build Your First Workflow: - Follow along: Form submission → Send email notification - Understanding triggers, actions, data flow - Test it and watch it work

Second Workflow: - Spreadsheet → Schedule social media posts - Introduction to scheduling and conditional logic

Part 3: Build Real Workflows (40 min)

Example Workflows to Build: - New signup → Add to database → Send welcome email - Daily backup trigger → Backup files → Report status

Hands-on Practice: - Each participant builds one workflow for their actual organizing work - Facilitator provides support - Test, debug, iterate

Share & Discuss: - Quick presentations: What did you build? - When to automate vs. when to keep human touch - Automation should make space for connection, not replace it

Part 4: Backups & Security (10 min)

Backups Are Not Optional: - Your server now holds valuable organizing data - 3-2-1 rule: 3 copies, 2 media, 1 offsite - Quick backup script demonstration - Set up automated daily backups with cron

Homework:

  • Build one more automation workflow
  • Set up backups on your server and test restoring
  • Document your workflows with screenshots
  • Start planning your capstone project (final session presentation)

Session Five: Building Your Newsletter System

Duration: 2 hours Format: Deploy a complete organizing tool

Part 1: Why Email & Why Self-Hosted (20 min)

Email is Still King: - Social media deplatforms you - Email is decentralized, you own the list - Newsletter as organizing tool: updates, calls to action, movement building

The Case for Self-Hosting: - You own the data, control the message - No corporate surveillance - No arbitrary deplatforming - Unlimited subscribers, unlimited sends - Corporate alternative: Mailchimp ($20-300+/month)

Quick Case Studies: - How movements use newsletters effectively

Part 2: Deploying Listmonk (60 min)

What is Listmonk?: - Self-hosted newsletter and mailing list manager - Modern interface, powerful features - Free and open source

Deployment: - Docker compose configuration (includes PostgreSQL database) - Initial Listmonk configuration - Email delivery setup (SMTP - facilitator provides guidance)

Hands-on Configuration: - Import test subscribers - Create subscriber lists - Design your first template - Write and send a test campaign - Review analytics

Part 3: Integration & Workflow (30 min)

Connect Everything: - Forms (Budibase) → Newsletter signup → Listmonk - n8n workflow: new subscriber → send welcome email

Build Complete Signup Flow: - Create signup form in Budibase - Connect to Listmonk via n8n - Test end-to-end - Verify emails are deliverable

Best Practices: - Double opt-in (legal and ethical) - Easy unsubscribe (required) - Consistent schedule - Mobile-friendly design

Part 4: Content Strategy & Planning (10 min)

What Makes a Good Political Newsletter?: - Clear calls to action - Mix of education and mobilization - Personal voice, not corporate speak - Regular schedule builds trust

Quick Planning: - Frequency? Content pillars? Goals? - Will you actually commit to this?

Homework:

  • Send your first real newsletter to a test list
  • Set up and test your complete signup workflow
  • Write 2-3 newsletter drafts
  • Finalize your capstone project plan (you'll present next session!)

Session Six: Presentations & Future Paths

Duration: 2 hours Format: Celebration and sharing

Part 1: Capstone Presentations (60 min)

Each Participant Presents (5-7 minutes each): - What did you build? - What problem does it solve for your organizing? - What was hardest to learn? - Demo your system! - Questions from the group

Facilitator Notes: - Celebrate every win - Highlight creative solutions - Document impressive projects

Part 2: Reflection & Teaching (40 min)

Guided Reflection: - What did you believe about technology 4 weeks ago? What now? - How does owning your infrastructure feel different from renting? - How has this changed your organizing approach?

Political Reflection: - How does learning these tools shift power? - What does it mean to own your infrastructure? - How can this escape the Political Industrial Complex?

You Are Now the Teacher: - Who in your organization needs these skills? - How will you teach them? - Each participant commits to teaching 1-2 people from their org

Part 3: Future Paths & Closing (20 min)

Where to Go From Here: - Advanced self-study resources - How to stay connected with this cohort - Bunker Ops office hours and support

Call to Action: - Distribute these tools in your movements - Teach others (free or at cost) - Contribute to open source - Resist corporate capture of organizing

Closing Circle: - Each person shares one word describing how they feel - Group commitment: stay in touch, support each other, build the future

Celebration: - Exchange contact info - Optional: group photo (with consent) - Pat yourselves on the back - you did the damn thing


Course Materials & Resources

Provided by Facilitator:

  • Access to demo server for practice
  • USB drives with Ubuntu Server image
  • Printed command reference sheets
  • Reading materials (digital and printed)
  • Ongoing support via Signal group

Participants Should Acquire:

  • Server hardware: Old laptop, mini PC, Raspberry Pi, or similar (often can repurpose existing hardware)
  • Ethernet cable (for reliable network connection)
  • USB drive for installation (8GB or larger)
  • Optional: Domain name (if planning to host publicly accessible services)
  • Optional: External drive for backups
  • All Bunker Ops philosophy documents (provided)
  • "Surveillance Capitalism" resources
  • Security culture zines
  • Relevant chapters from "Emergent Strategy"

Online Resources:

  • Bunker Ops documentation repository
  • Docker documentation
  • Linux command reference
  • Participant-created wiki (built during course)

Assessment & Certification

Completion Requirements:

  • Attend 5 of 6 sessions (one absence allowed)
  • Complete capstone project
  • Present your work in Session 6
  • Help at least one peer with troubleshooting

Certificate of Completion:

  • Participants receive certificate documenting:
  • Skills learned
  • Applications deployed
  • Hours of training
  • Can be used for professional development or organizational credentialing

Ongoing Community:

  • Alumni invited to monthly co-working sessions
  • Advanced workshops offered periodically
  • Opportunity to TA future cohorts
  • Building a movement of technically skilled organizers

Facilitator Notes

Preparation Checklist:

  • Demo server fully configured and accessible
  • All reading materials gathered and shared
  • Hardware sourced for participants who need it
  • Backup plans for technical failures
  • Strong coffee budget

Pedagogical Approach:

  • Theory and practice woven together always
  • Validate struggle: this is hard because capitalism wants it to be
  • Celebrate small wins: first command, first deployment, first automation
  • Build solidarity: we're learning together, help each other
  • Political grounding: never lose sight of why we're doing this

Common Challenges & Solutions:

  • Participants at different skill levels: Pair stronger with newer learners
  • Hardware failures: Have backup machines available
  • Confidence issues: Normalize struggle, share your own early mistakes
  • Time management: Be ruthless about staying on schedule, offer bonus sessions
  • Retention between sessions: Weekly homework accountability, peer check-ins

Success Metrics:

  • All participants deploy at least 3 applications
  • Infrastructure ownership and control achieved
  • At least 50% teach someone else within 3 months
  • Ongoing community stays active
  • Organizations actually adopt these tools