Guides & Examples
Self-Hosting Guide
Deploy and manage your own superglue instance
This guide walks you through deploying and managing your own instance of Superglue for complete control over your data processing pipeline.
Prerequisites
Before you begin, ensure you have:
- Docker (version 20.10.0 or higher)
- Redis (version 6.0 or higher) for persistent storage
- OpenAI API key with access to the recommended model
- At least 2GB of RAM and 1 CPU core
- Git (optional, for building from source)
Deployment Options
Option 1: Docker Compose (Recommended)
- Create a Docker Compose File
Create a docker-compose.yml
file:
- Configure Environment Variables
Create a .env
file:
- Start the Services
Option 2: Manual Docker Setup
If you prefer more control over the container setup:
- Pull the Docker Image
- Create a Docker Network
- Start Redis
- Start Superglue
Health Checks and Monitoring
Basic Health Check
Expected response: OK
Monitoring Endpoints
- Dashboard:
http://localhost:3001/
- GraphQL Playground:
http://localhost:3000/graphql
Other Considerations
-
Network Security
- Use reverse proxy (nginx/traefik) for TLS termination
- Implement IP whitelisting if needed
- Keep access to the dashboard private since it is not protected by auth, or implement nginx basic auth to protect it
-
Authentication
- Change default AUTH_TOKEN
- Use strong Redis passwords
- Rotate credentials regularly
-
Telemetry
- Superglue uses telemetry to understand how many users are using the platform.
- You can opt out by setting the DISABLE_TELEMETRY environment variable to true.
Performance Tuning
Redis Configuration
Optimize Redis for your workload:
Resource Allocation
Recommended minimum resources:
- 2 CPU cores
- 4GB RAM
- 20GB storage
Troubleshooting
Common Issues
-
Connection Refused
- Check if containers are running:
docker ps
- Verify network connectivity:
docker network inspect superglue-network
- Check if containers are running:
-
Authentication Failed
- Verify if the query params token or the Authorization Bearer is present and set to AUTH_TOKEN in the .env file
- Check Redis credentials
-
High Memory Usage
- Monitor Redis memory:
docker stats
- Adjust cache settings
- Consider upgrading resources
- Monitor Redis memory:
Logs
Access container logs:
Upgrading
- Pull Latest Image
- Update Services
Support and Resources
- Documentation: Superglue Docs
- GitHub Issues: Report bugs
- Discord Community: Join our Discord
- Email Support: stefan@superglue.cloud
Was this page helpful?