# Sidekiq fails to start after Zeitwerk on docker dev

**URL:** https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031
**Category:** Development
**Created:** [2 oktober 2019 om 10:44 UTC](https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031 "2019-10-02T10:44:03Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![azawawi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/azawawi/32/135777_2.png) [@azawawi](https://meta.discourse.org/u/azawawi)
#### Post date: [4 oktober 2019 om 05:13 UTC](https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031/17 "2019-10-04T05:13:30Z")

</div>

@kris.kotlarek Thanks a lot 🥳 👍 . I took a look at your post for the zeitwork auto-loader. Is there a plan to enable a development plugin auto-reloading feature to speed up plugin development.

> [@Upgrading Discourse to Zeitwerk](https://meta.discourse.org/t/upgrading-discourse-to-zeitwerk/128337):
>
> Rails 6 ships with two autoloading modes: zeitwerk and classic. In that pull request [DEV: Upgrading Discourse to Rails 6 by KrisKotlarek · Pull Request #8083 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/8083) I upgraded Rails to version 6.0.0 with classic autoloader as a transitional phase. It would be interesting to try to switch to Zeitwerk. Zeitwerk is an efficient and thread-safe code loader for Ruby. As long as the project is following naming conventions, Zeitwerk can find correct files and load them on deman…

[https://github.com/fxn/zeitwerk](https://github.com/fxn/zeitwerk)

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031)._