#debuglogs.app

This is the source for debuglogs.app: an in-browser viewer for Signal's debuglogs.org logs. To use the site, simply replace .org with .app on any debuglog, and you'll jump into an in-browser viewer.

If you'd like to do this automatically, you can use the 'Always debuglogs.app' extension, which you can find here: link.

#Running locally

This is a simple Deno/TypeScript app. The only dependency is Deno.

The quickest way to get started is to simply run:

deno task start

This will build the client and start the server on port 8080. You can view any log by replacing debuglogs.org with localhost:8080.

#Developing

During development, you can run the builder in "watch" mode to re-compile the client code whenever you change something:

deno task watch

Note: This only watches the client code, not the server code.

#Deploying

You can deploy a version of this however you'd like, but debuglogs.app runs on a Dokku instance. That's what the Dockerfile is for. If you'd also like to run it on Dokku, you can deploy it like a normal app, but remember to proxy the host port 80 to container port 8080.

dokku proxy:ports-add debuglogs.app http:80:8080

If you use the Dokku letsencrypt plugin, you can configure that per usual and it'll Just Work.

#How it works

The server itself (index.ts) is little more than a proxy. It just serves static files and exposes a /proxy endpoint to allow the client code to fetch the raw contents of the debuglogs.org log file.

All of the actual work is done on the client. The client takes the file, formats it (which may even involve unzipping using zip.js), and then renders it using Monaco, the editor behind VSCode.