Skip to content

Start customoffice

Start CustomOffice Locally

To start local development, simply run: 

./start-dev.sh

You will be prompted for a database name.

If you are following the Getting Started guide, then type econ, otherwise choose the name of any loaded databases you wish to start development against.

Now you should be able to access http://localhost:8080

Login using username lokal and password lokal

Logging / Output

When running CustomOffice locally, you can find log output in the following locations:

  • Front-end: Log output is available in the browser's developer console.
  • TypeScript backends and dotnet-server: Logs are available in Seq at http://127.0.0.1:5342/. This local Seq instance acts as the log sink for the following services:
  • api-server (via pino-seq)
  • task-runner (via pino-seq)
  • fields-server (via pino-seq)
  • scripts (via pino-seq)
  • nest-api-server (via nestjs-pino)
  • dotnet-server (via Serilog)
  • Python: Log output is written to stdout and stderr.

The Django backend container depends on the Seq container, ensuring that the Seq service is started automatically when running start-dev.sh to start CustomOffice locally.

Note: In production, we use Sentry to collect logs. At the moment, logs from dotnet-server and pdf-content are not sent to Sentry.