Skip to content

Dev environment can sometimes show old errors on startup, which is very misleading #825

@jarofgreen

Description

@jarofgreen

Sometimes when you start the dev environment you'll see a bunch of Python crashes that make no sense.

It's because they are from a previous run, and they are being show to you a second time.

From Dockerfile this does it:

CMD ["tail", "-n", "+0", "-f", "/var/log/gunicorn/gunicorn.log"]

If you run:

docker compose -f docker-compose.dev.yml exec web rm /var/log/gunicorn/gunicorn.log

Then restart, the old errors should be gone and you'll only see errors from this run.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions