david_bai
246eff196e
- generate-config.sh
- Add flags: --no-clean, --reset-ssl, --ssl-mode (letsencrypt|self-signed|provided)
- Stop deleting docker/ssl by default; only wipe on explicit --reset-ssl
- Inject ACME webroot route into HTTP (80) server; create docker/letsencrypt-www
- Default SSL_MODE: full=letsencrypt, private/public=self-signed
- Add enable_https_if_cert_present: append 443 server only when server-cert.pem/server-key.pem exist
- Keep self-signed path generating HTTPS immediately (non-basic)
- docker-compose.yml
- Mount ./docker/letsencrypt-www:/var/www/certbot:ro for Nginx ACME challenges
- deploy.sh
- Add --le-email for Let’s Encrypt account email
- Auto-install certbot once (apt-get) and enable systemd timer if available
- Install deploy hook at /etc/letsencrypt/renewal-hooks/deploy/privydrop-reload.sh to:
- Copy renewed certs into docker/ssl
- Hot-reload Nginx; HUP or restart coturn
- First-time issuance (webroot) for <domain> and turn.<domain> after Nginx:80 is up; copy certs
- Re-run generate-config with --no-clean --ssl-mode letsencrypt to enable 443, then reload Nginx
- Behavior changes
- Full mode prefers Let’s Encrypt by default; HTTPS gets enabled as soon as certs exist
- docker/ssl is no longer wiped by config generation
- Notes
- SNI-based turns:443 is not implemented yet (planned)
- Backward compatible with private/public (self-signed)
PrivyDrop - A Privacy-Focused, WebRTC-Based File Sharing Tool
PrivyDrop(formerly SecureShare) is an open-source, peer-to-peer (P2P) file and text sharing tool built on WebRTC. It requires no server-side data relay; all data is transmitted directly between browsers, ensuring end-to-end encryption for maximum privacy and security.
We believe everyone should have control over their own data. PrivyDrop was created to fulfill this vision: a simple, fast, and private sharing solution.
Try it Live » | GitHub Repository »
✨ Key Features
- 🔒 End-to-End Encryption: Leverages P2P direct connections via WebRTC. All files and text are transferred directly between browsers without passing through any central server.
- 📂 File & Folder Transfer: Supports transferring multiple files and entire folders.
- ⏸️ Resume Transfer: Resume file transfer from the point of interruption. Simply set the save directory to enable this feature, ensuring your large files are delivered safely even with unstable networks. If interrupted, you currently need to refresh both the sender and receiver web pages to restart the transfer.
- ⚡ Real-time & Efficient: Displays real-time transfer progress and automatically calculates transfer speed.
- 📝 Rich Text Clipboard: Supports editing and sending formatted text, not just files.
- 🔗 Convenient Sharing: Easily share a room and establish a connection via a link or QR code.
- 📱 Multi-Device Support: Responsive design supports both desktop and mobile browsers.
- 🌐 Internationalization: Supports multiple languages, including English and Chinese.
🛠️ Tech Stack
- Frontend: Next.js 14, React 18, TypeScript, Tailwind CSS, shadcn/ui
- Backend: Node.js, Express.js, TypeScript
- Real-time Communication: WebRTC, Socket.IO
- Data Storage: Redis
- Deployment: PM2, Nginx, Docker [WIP]
🚀 Quick Start (Full-Stack Local Development)
Before you begin, ensure your development environment has Node.js (v18+), npm, and a running Redis instance installed.
-
Clone the Project & install redis
git clone https://github.com/david-bai00/PrivyDrop.git cd PrivyDrop sudo apt-get install -y redis-server -
Configure and Start the Backend Service
cd backend npm install # Copy the development environment file, then modify .env.development as needed cp .env_development_example .env.development npm run dev # Starts by default at http://localhost:3001 -
Configure and Start the Frontend App (in a new terminal window)
cd frontend pnpm install # Copy the development environment file, then modify .env.development as needed, Remove optional items cp .env_development_example .env.development pnpm dev # Starts by default at http://localhost:3002 -
Start Sharing Open
http://localhost:3002in your browser to access the application.
🗺️ Roadmap
We have a public roadmap that outlines our vision for the future and our current priorities. It's a great place to see what we're working on or to find areas where you can contribute.
➡️ Check out the Project Roadmap
📚 Documentation
We provide detailed documentation to help you dive deeper into the project's design and deployment details:
- Overall Project Architecture: Understand how all components of the PrivyDrop system work together.
- Frontend Architecture Deep Dive: Explore the frontend's modern, layered architecture, state management with Zustand, and the decoupled service-based approach to WebRTC.
- Backend Architecture Deep Dive: Dive into the backend's code structure, signaling flow, and Redis design.
- Deployment Guide: Learn how to deploy the complete PrivyDrop application in a production environment.
🤝 Contributing
We warmly welcome contributions of all forms! Whether it's reporting a bug, suggesting a feature, submitting code or adding a star, your help is invaluable to PrivyDrop's growth. Please read our Contribution Guidelines to start your journey.
We have a Code of Conduct that all contributors are expected to follow. Please be sure to review it before participating.
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.