I’ve been running into some problems while attempting to update from Zammad 6.3.x to Zammad 6.5, and I’ve realised the documentation for updating source installations is missing some important information I think, such as how to copy over the configuration from the existing installation as copying the whole config directory I found doesn’t work. I’ve also had all sorts of fun with installing Vite and trying to successfully complete a rake assets:precompile. I can’t see any documentation on Vite in the Zammad doco’s, but I found I had to manually installing it. The steps documented in this post so far seem to be the best: [Zammad 6.5 per Source - Update] No Users in View - Technical assistance - Zammad - Community
This brings to where I’m up to, which is stuck on rake assets:precompile. When running, it seems to get stuck in a loop repeating the “Building with Vite” step until everything locks up because I’ve run out of memory or the CPU is completely pegged while flogging the swap file. See screenshot below.
If someone can give me some guidance here, that’d be appreciated. I’ll keep at it in the meantime and will be sure to post back with how I’ve fixed it if I manage to get that far.
So, turns out the zip files under https://ftp.zammad.com/ don’t contain any dot-prefixed hidden files or directories. The red-highlighted error regarding missing “.eslist-plugin-zammad” in the above screenshot was somewhat of a clue. That needs to be looked into and remedied as that’s bound to trip up others.
I think my other Vite-related issues were because I didn’t have pnpm installed before running bundle install. So I think I’m all good, but the documentation for updating/upgrading source installations does need to be improved.
I’ll now take the opportunity to migrate to Postgres.
I think for me it’s maybe an issue of control and/or understanding when it comes to troubleshooting.
Using the system package manager is not an attractive option unless I had Zammad running on its own VM. Right now, it’s on a server with other Ruby web apps sometimes on its own Nginx instance, sometimes sharing depending on the Ruby version dependency.
I should look more into docker, but Zammad is the only application that we’d see any benefit from running that way, so we’d have to make that investment solely for the purpose of running Zammad. Maybe the day we move Zammad from on-prem to cloud-hosted that’d make more sense where the Docker infrastructure already exists.
Source installation has generally worked very well for us given we already run other ruby web apps as mentioned. This latest update going from Zammad 6.0 to 6.5 has given me the most grief but only because of the somewhat lacking source install/update documentation and the issue with the zip files, otherwise it would have been relatively straight forward.
