This repository provides an open-source version of the Campsite app, aimed at developers interested in self-hosting or understanding its internal workings. It offers a reference implementation for a collaborative workspace application, allowing for forks for non-commercial use.

How It Works

The application is a monorepo built with a Rails API backend and a web frontend. It relies heavily on external services for core functionalities: AWS S3 for media storage, Pusher for real-time updates, Imgix for CDN image processing, and 100ms for video conferencing. OpenAI is integrated for call summarization. Development is managed using Overmind for orchestrating multiple services.

Quick Start & Requirements

• Setup: Run script/setup from the workspace root.
• Prerequisites: AWS S3 (with IAM user and policies), Pusher account, Imgix account (with user, policies, and API key), 100ms account, OpenAI API key and organization ID. Additional services like Cal.com, Figma, Linear, Postmark, Sentry, Slack, and Vercel may be required for full functionality.
• Development: Uses Overmind for service management. Web app development requires pnpm install, vercel login, and vercel link.
• Docs: Local dev setup: https://github.com/campsite/campsite#local-dev-setup

Highlighted Details

• Extensive integration with third-party services for media, real-time, CDN, video, and AI features.
• Monorepo structure managed with pnpm for dependency handling across packages.
• Rails API with credential management for sensitive information.
• Vercel is used for deploying and managing the web application.

Maintenance & Community

This codebase is provided "as-is" and is not actively maintained by the Campsite team. Pull requests and issues are only considered for self-hosting or critical fixes. Forks are welcomed for non-commercial projects.

Licensing & Compatibility

The README does not explicitly state a license. It mentions that the codebase is available "as-is" and welcomes forks for non-commercial projects, suggesting potential restrictions on commercial use.

Limitations & Caveats

The project is not actively maintained, with limited support for pull requests and issues. Critical functionality relies on multiple external paid services, which must be configured and maintained separately. Video call features requiring webhooks necessitate a secure tunnel like ngrok for local development.