Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade loses admin key from config.js #184

Open
webmink opened this issue Mar 13, 2023 · 4 comments
Open

Upgrade loses admin key from config.js #184

webmink opened this issue Mar 13, 2023 · 4 comments

Comments

@webmink
Copy link

webmink commented Mar 13, 2023

Describe the bug

When running any upgrade to CryptPad on Yunohost, the admin key is lost from config.js

Context

  • Hardware: Raspberry Pi 4
  • YunoHost version: 11.1.15
  • I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • If upgrading, current package version: 5.2.1~ynh6

Steps to reproduce

  • Click "System Update" in Yunohost admin screen
  • Request pending upgrade to CryptPad
  • On completion config.js has been replaced with a vanilla version with no admin key so no administration is possible without manual edits of config.js

Expected behavior

Install should preserve admin key and perhaps some other changes to config.js that are necessary for normal operation

Logs

https://paste.yunohost.org/raw/atukamafes

@webmink
Copy link
Author

webmink commented Mar 21, 2023

Potential fix: #185

@Ddataa
Copy link
Member

Ddataa commented Mar 25, 2023

yes it is under construction...

@webmink
Copy link
Author

webmink commented Jul 28, 2023

Did this get integrated in the recent release? I still had to update my admin key when I upgraded...

@tituspijean
Copy link
Member

It has been implemented in #185, but somehow disappeared from the code later. In any case, the ynh_read_var_in_file helper does not seem to be able to read that variable. Maybe we need to have a configuration panel for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants