I updated to github stable. I noticed a few data migrations. Now I have an action of Nicole Braun again:
Because you didn’t remove Nicole which is a default user, Zammad will update it based on migration when ever required.
Thx, I deleted the user now. Hopefully, she couldn’t do a login for my zammad server before. And hopefully, future migrations continue to work.
Nicole Braun is a virtual person. The account has no login credentials unless you give her some.
Updated to github:stable and Nicole Braun shows up again:
So: Deleting the user doesn’t help. It shows up again after updating.
It surely is time for you to tell us how exactly your update process logs.
Meaning what are the steps you take in order to update.
Thx for taking the time. I do this:
- Update my github checkout
- Create a tar using
git archive --format=tar ...
- (*) Determine the file differences relative to the previous tar - which files have been in the previous tar but aren’t in the current tar any more?
- Stop zammad and apache httpd (=used as a reverse proxy)
- Unpack the tar to my webroot
- Delete all files from (*) within the webroot
- Start zammad and apache httpd
- When I see updated dependencies, execute these commands as zammad user:
gem install bundler rake rails
bundle install --without test development postgres
- This was not necessary for the last update!
- Execute various commands as “zammad” user:
rake db:migrate rake db:seed rails r "Locale.sync" rails r "Translation.sync" rake assets:precompile rails r Cache.clear
Typically, this works fine. Sometimes I have to update some env variables, for example when
rails got updated.
And exactly this command is your problem.
The update documentation doesn’t mention it. Seeding your database means inserting default values.
This even potentially overwrites existing settings if you’re very unlucky.
Cross that step and you’ll be fine.
Seeding is relevant exactly once (initial installation).
Thx a lot for debugging my upgrade procedure!
Hopefully “Nicole Braun” will now be gone forever. Hopefully, the instance will continue to work. Looking into the source code, I see some special code paths which contain hard-coded references to this user, for example:
def test_customer User.find_by(login: 'email@example.com') end
I hope this is testing code, only.
This part is not relevant in production instances that left testing phase.
This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.