everytime I go to update my friend @techwithanirudh forum I can update everything but discourse or discourse related features idk why this is it leads to things such as super outdated forum and annoyance
Can I get an explaintion
Is this something he sets in his SSH or code base that other administrators can not update discourse based items also can not impersontate other admins either that is also I fell wrong.
Docker_manager is the tool that handles upgrades to Discourse. It must be updated first so it knows how to properly upgrade the newer Discourse version.
Click Update on Docker_manager.
Once that’s complete, it should allow you to click Update on Discourse
5 לייקים
I’m not certain what you’re asking for here but my preferred method to update is to use launcher in /var/discourse
If you are on tests-passed then often there will be commits available after a short amount of time as they like to iterate fast. This isn’t necessarily ‘out of date’.
2 לייקים
Adubs I don’t have access to the code of the forum and Keegan I’ll try the manager and let you know
לייק 1
Ok @keegan that seems to have worked it now works but why cant I just update it all at once?
לייק 1
You can if you use launcher. I would request access to SSH.
Because docker manager is the one that updates discourse
לייק 1
IIRC it’s because the newer version of Discourse needs Docker Manager to first be upgraded. Think of it like a dependency thing.
that makes more sense nate adubs could you clarify?
I believe a rebuild via the CLI with ./launcher rebuild app would pull the latest versions of everything from Github automatically, whereas you have to do so manually via the UI.
i think @ice.d has a good point though that it is cumbersome to have to update twice when docker_manager needs an update. You have to first to update docker_manager and then wait for that to complete and then update Discourse (or Update all) to update Discourse and any plugins.
Updating docker_manager takes long enough that I often will start that update and then go away to do something else, and then I only remember later to return to update Discourse.
It would be a nice touch if the UI still allowed the Update all button in this case, and just update docker_manager first and then automatically proceed to update Discourse. If the docker_manager update fails, the process could be interrupted.
3 לייקים
I used to do that, but then I realized that if you update using the website, there is much less downtime.
That’s true, if the update succeeds. But if it fails, and it sometimes will, then you have a non-working forum until you can get to the commandline to fix things. So, if uptime matters to you, you will always be ready to do that at the point of trying an update.
And in every case, you should take a full backup and download it before trying an update. If things go very wrong, you’ll need it.
לייק 1
Hmm… then would a two-container setup help here?
yeh, but would you do about sidekiq?
As I understand it, with a two-container setup you can do a command line rebuild with minimal downtime. So yes, it makes a command line rebuild more attractive.
2 לייקים
Docker Manager does not support two container setup FYI
3 לייקים
Thank you all for your assistance as I’m concerned I just need to make sure the docker is updated inorder to do the rest?
That’s correct. Just run the Docker_manager first. It takes about 5 minutes on my server. After than, you can update Discourse, update plugins, or choose “Update All”.
לייק 1