Development environment : running sidekiq and discourse at startup

[jack2]

@drew0101

I just cant for the life of me figure out why the admin dashboard says that sidekiq is not running,

I always have this warning message and Sidekiq works like a charm. So I came to the conclusion it’s the standard behavior for a dev instance.

@drew0101

why jobs stay in the enqueued section

This workaround worked for me: change config.eager_load to true in development.rb. See this thread:

Webhooks/Sidekiq issue on dev instance

I run 2 Discourse instances: a standard one (Docker) a dev one, behind a nginx proxy I’ve set up the same webhook on both instances. It works well from the standard instance, but not from the dev instance: the Ping button never gets a response and stays gray, although the corresponding POST event seems to appear in the nginx log (EDIT: this log entry is about the click event localhost->Discourse, not the outgoing webhook ping message). I see no error in the Discourse server console or n…