Hello,
Is there a way to download an older version of Passbolt CE?
I’m currently running version 4.8.0 on Rocky Linux 8 on a VM. I need to test the new v4.9.0 version on a new test server. I’d like to install v4.8.0 first on the test server, then perform the upgrade to v4.9.0 and then test everything works as expected.
Is it possible to download the rpm for Passbolt CE version 4.8.0? If yes, can you please tell me how?
Thank you very much!!
Hi @skystar 
You can follow the passbolt setup instructions then instead of install the latest version, you can install the 4.8.0 like this:
dnf install passbolt-ce-server-4.8.0-2.noarch
If you wanna see all available versions:
dnf search --showduplicates passbolt-ce-server
Cheers,
1 Like
Thanks @AnatomicJC I really appreciate the help and the quick response!
1 Like
You’re welcome! 
Hi Guys, noob here on the community just trying to get a version of passbolt to run on a Rocky Linux 8 setup for a customer. They are keen to run with this product but need the Linux guy (that would be me) to do the underpinning works.
I cannot get to the repo for Rocky Linux 8 setup and of course the install script being Rocky Linux 9 won’t work.
Is there a repo file/location or a download location for the version that works on Rocky Linux 8?
dnf of course has no idea about passbolt as there is no repo and is not found on the epel setup either.
Any pointers much appreciated.
The customer is willing to go to Rocky Linux 9 but there is a lot of ‘stuff’ already on Rocky Linux 8 VM to migrate so a direct install on the existing LAMP is more time friendly.
Also on a new install, is Rocky Linux 10 on the cards or did I miss this somewhere?
Many thanks for your patience with my questions if posted elsewhere and I will go digging for any more posts on the Rocky Linux 8 questions I have replied with here.
G’day David.
The short story is that the dep-scripts setup an OS with the repositories, GPG keys, and currently they do some opinionated requirements to make for a clean install on fresh installs.
We have a task internally for separating out some of those functions and letting the package set its own dependencies but that’s for another story…
I would strongly recommend to anyone that they have a dedicated host OS (bare metal/vm/container) that does not share services with anything but the web server with PHP 8.2 modules, a database, and some firewall/hardening required for hosting a passbolt instance.
One could comment out the compliance_check(), is_supported(), and os_detect(), and install_dependencies () functions of the dep script as it is indeed “just a LAMP stack”.
We have 15+ install methods (including from source) and I certainly wouldn’t recommend them all.
Does your client have a set of requirements other than running Rocky 8?
We are currently testing Rocky 10 and Debian 13.
Happy to answer any questions.
cheers
gareth
https://endoflife.date/rocky-linux
https://github.com/passbolt/passbolt-dep-scripts/blob/main/passbolt-repo-setup.ce.sh
1 Like
Thank you Gareth, the customer finished up creating a Rocky Linux 9 VM but they did ask me about Rocky Linux 10 - would you recommend I get a 10 in place instead rather than proceeding with 9?
Good morning David.
I would stick with Rocky 9 and Debian 12 for now.
IMHO I think people want to “set and forget” Linux servers as they’re like an old diesel truck, they can go on forever.
But even a diesel engine should have the injectors replaced every 150-200 thousand kilometres.
What I mean by that is that hosting stacks get fragile over time unless you’re constantly managing them.
Databases need love, PHP and Nginx need love, even passbolt upgrades hit weird issues with instances that have been running on the same stack for 5+ years.
My point is that you should think about the Operating System as being relatively ‘ephemeral’. You need to wipe it out and install the latest version every few years so work on your backup and restoration plan.
It’s a cliché but true that servers experience issues because many of the changes that have been made over a long period are not persistent upon a reboot or not documented and if you inherit management of one of these servers it’s a kind of archeology to figure out what’s been done to it. (sometimes that person is future you, cursing your own name)
Setting and forgetting a hosting server is from a time when ‘uptime’ was a badge of honour.
Rocky 9 has active support for 1 year and 9 months. It’s stable and if there are bugs then they’re probably very well documented.
When running production systems: be boring, and be reproducible.
Perhaps you are familiar with Ansible and want to try deploying passbolt that way?
Always happy to help if you have more question.
Gareth
Yes I have been working with UNIX since 1987 so very much come from ye olde school of locking things down and then not allowing anyone to change anything at the OS level or the running software was a rule set in stone.
Will go with the Rocky 9 they installed as I have had a hard enough little trip trying to get the application onto Rocky 8
Thank you so much for your guidance and having worked with LAMP for a while now I am all too aware of the little dependencies that ‘change’ over time.