Hi guys.
I’ve browsed the forum in search for an answer/docs - found something that was supposed to work - but cannot, am unable to find a way to get specific release.
I’m reading that adding, eg.: version: v3.4.6
into your .yml and also puling specific docker image, prior to launcher
run should result in that exactly, in such a given version being built/deployed, but..
./launcher
seem to pull latest image regardless and - in variations I’ve tried - my bootstraps
attempts always fail, only ‘latest-release’ succeeds, but that defeats the purpose of specific release, naturally.
Is there a relatively simple method to build/deploy specific release?
Hello @lejeczek
Is there a reason you want this? Its recommended you are on latest and update your site periodically to enjoy new features and most importantly, ensure you have the latest security fixes. Once you update to a specific version rolling back is not supported.
Using official method I ended up with 3.3.0.beta1-dev some time ago - which works - now trying to update (to the latest) I get broken Discourse with:
Oops
The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.
What are the errors in /logs?
Did you run the update from the command line twice? There’s a postgres upgrade in there.
But no, it will be difficult to run a very old version since, as you point out, new old discourse isn’t compatible with new images. You need to check out an old version of Discourse docker.
Why do you want old software?
If you want old software then the best thing to do is switch to the stable branch. Or just never upgrade anything. That’s another way to play it. The oldest I think I’ve seen was 6 years
Some way I can upload/send somewhere/somebody more complete logs?
Hmm… could you take a screenshot of the errors?
Also, you may want to try what @pfaffman mentioned above: