Bugsink Error tracking consists of two main components: the Bugsink server and the Bugsink client. The server is responsible for receiving error reports and showing them to you, while the client is used to send error reports to the server. Client-side setup instructions are available once you create a project in Bugsink, but in general, you can use the Sentry SDK to send errors to Bugsink.
These guides cover the different ways you can deploy the Bugsink Server, depending on your environment and requirements:
Local Install: Great for testing and development purposes. This method allows you to run Bugsink on your local machine with minimal setup. It’s a quick way to evaluate Bugsink’s features without committing to a full production setup. Pythonistas will love this.
Docker Installation: Ideal for those who prefer containerized deployments. You can run Bugsink using Docker, with the option to choose between MySQL for persistent storage or SQLite for simplicity. This approach is flexible and can be easily integrated into different orchestration tools like Docker Compose or Kubernetes.
Production Setup: Best suited for high-traffic and long-term deployments. You’ll use Nginx as a reverse proxy and Gunicorn to handle application processes, ensuring stability and performance. This setup is designed for environments where reliability is critical.
Choose the method that aligns with your workflow and get Bugsink up and running in no time. Each approach is designed to streamline the installation process and get you started with minimal hassle.
