Sidekiq not running on local Discourse, can't upgrade

(Frank Bailey) #1

I need to upgrade my local discourse to the latest version so I can restore a backup made from a live Discourse instance, import users from Ning, and then backup and restore to the live instance. However, as Sidekiq isn’t running isn’t checking for updates. I tried to go to /admin/upgrade manually but I get a “route doesn’t exist” screen. Is there any other way to force an upgrade without having Sidekiq running? I dont’ want to run Sidekiq as I don\t want my dev instance sending out real emails.

Thanks in advance!

(Jeff Atwood) #2

Simply tick the “Disable all outgoing mail” checkbox in the site settings.

(Frank Bailey) #3

Jeff, are you saying I have no other option but to enable Sidekiq in order to be able to upgrade my Discourse instance? Is there no other way to upgrade to the latest version from within the Admin?

(Jeff Atwood) #4

You can upgrade from the command line, I was just pointing out that you can globally disable email via a site setting, you don’t have to kill off sidekiq.

(Jay Pfaffman) #5

Disabling outgoing mail is the best way to solve your problem of not sending mails. There are lots of ways you could accidentally re-start sidekiq.

You should upgrade from the command line. (./launcher rebuild app).

If you don’t want all of your imported users to get a PM from discobot (which starts a bunch of sidekiq processes) you should find that system setting before you do the import.

(Frank Bailey) #6

Yes, that was a very good suggestion; I’ve turned off emails entirely for the moment. Thanks :slight_smile:

(Frank Bailey) #7

Just to be sure, if I restore my backed-up local installation to the live server, will emails suddely begin going out to newly-added accounts, or will the live instance also have the “no emails at all” setting active if my local one was set to send no emails?

(Jay Pfaffman) #8

If you had the setting turned on when you made the backup, it’ll be restored.