GlitchTip
- 0 ratings
Open source error-tracking app. GlitchTip collects errors reported by your app.
Deploy this app to Linode with a free $100 credit!
This is a meta repo for general issue tracking, wiki, and deployment information.
GlitchTip on DO App Platform consists of a web, worker, migration job, postgres database, and redis. Start by clicking the following button. Note this link acts as a referral and helps fund GlitchTip.
Leave environment variables blank and click next. Pick the basic or pro plan. One 512 MB RAM | 1 vCPU is fine to start with. Click Launch. Now copy app-platform.yaml to your local computer. Edit the following
This can be anything. We default to "glitchtip" and "nyc".
At a minimum, set the SECRET_KEY to a random string of letters.
For more information on configuration settings see our install docs.
GlitchTip requires Redis for sending notification, managing events, and more. Go to https://cloud.digitalocean.com/databases/ and create a new redis database. For almost all size instances, the 1 GB RAM | 1 vCPU instance is sufficient. Enter your redis database's name in the glitchtip-redis section. Let's assume it's named "glitchtip-redis". At the time of this writing, both "name" and "cluster_name" must be the same value.
- name: glitchtip-redis
engine: REDIS
production: true
cluster_name: glitchtip-redisEnsure the environment variable "REDIS_URL" uses the same name. If you didn't name your redis instance "glitchtip-redis" then make sure to update it.
You'll need to install doctl and log in.
Run doctl apps list to get your app's id.
Now apply your app-platform.yaml spec with doctl apps update 11111111-1111-1111-1111-111111111 --spec app-platform.yaml (enter your actual id)
After deployment, you should be able to visit the app URL and start using GlitchTip!
If you intend to use GlitchTip in production, consider upgrading your Postgres database to a production instance. In the web interface, go to Manage Components, glitchtip-db, Upgrade to a managed database.
If you haven't already, you'll need to set up email via environment variables.
By default, the docker image tag is "latest". Click Deploy to upgrade to the latest GlitchTip docker image.
Consider upgrading your Postgres and web dyno plan for production usage.
Most users do not need additional workers. However if you do, create a third dyno typed called extra_worker. Set the run command to ./bin/run-celery.sh. Do not increase the "worker" dyno count because this these run with an embedded Celery beat scheduler.
By default, the docker image tag is "latest". Click Deploy to upgrade to the latest GlitchTip docker image.
Please login to review this project.
No reviews for this project yet.
Comments (0)
Please login to join the discussion on this project.