[Feature Request] Persistent Data #9
Comments
|
Hi @I-am-Kamino! Thanks for the feature request. For the following points:
I'd suggest downloading the language pack and creating these preset files on your host, and volume-mounting them into the container. I'll see if there's a better way to do this in the meantime. I'll look into why you keep getting asked to re-install it. |
|
Hi @luketainton. I'd like to second @I-am-Kamino's request, and add some info. Hopefully this wall of text will be of some help to you both. The issueI'm experiencing similar issues to @I-am-Kamino. If, for some reason, I have to recreate the HESK container, it forces me to go through the install process again. Only it can't complete it, since the database already exists. Updating doesn't work either, because the script responsible for updating refers to the default HESK login values for the already-existing database. It then errors out with the following message if you've changed any of those values (which you should): What didn't workThe However, this creates an empty directory without any of the necessary files after spinning up the containers. What workedEventually, I got it to work by going through the following steps:
My
|
|
Right, that would work because it's editing the HESK config file directly on the host. The issue comes when you update HESK to a new version, although I'd like to assume they provide guides on how to do this. The easiest option I can think of right now is to keep the config file and other persistent files on the host (or in a Docker volume) and mount them into the container. It might take some time for me to identify all relevant files (I have a day job too 😄) so bear with, unless you know of them? |
Yeah, it's definitely not working as expected. Normally, manual editing on the host shouldn't be necessary. But as a workaround it works. Updating HESK shouldn't be an issue. You usually only need to replace a few files, and you're done. A diff of two
I'll see if I can dig around my notes. I think I may have already looked into it once. As to the permissions settings I talked about, I've not had time to look into those (which is why I opted for the global 777 approach). Same problems with a day job here too. I'll post an update if I find anything. Might take a while though. |
|
Here's a list of files that are different between HESK v3.2.5 and v3.3.1: Looks like this list could be different between each version, though. The upgrade guide provided by HESK (look under "Upgrade from old HESK version") will tell you all the files need to be replaced when upgrading, but you can probably get away with replacing only the files that are different and removing those that are unique to the old version ( As for the file permissions, looks like you only need to give read/write permissions to three locations (according to HESK UI): Hope this helps. |
@Gitoffomalawn Any ideas? |
Well, yes. The HESK app and the database are two separate containers. This means that inputting However, you don't necessarily need to use the IP address to point to the database. You can input
Yes, I addressed this issue in #11. According to @luketainton, this is an issue with HESK itself which he cannot resolve as he doesn't maintain the application. In any case, this error doesn't appear to affect the installation process or how HESK functions in any way that I've encountered so far. Seems to me you can safely ignore this error. |
|
@Gitoffomalawn thank you. Makes sense. |
|
Hey all, apologies it's taken me so long. I have an idea that could work here:
|
I would think that one would also want to do this with the |
Hi,
I am not sure if posting this here is right, as I am new to github. Please correct mistakes made.
My request
So there are several things:
/srv/language/<locale>/emails/<preset>.txtand/srv/hesk_settings.inc.phpThis all takes some time so I am wondering if you may persist some of these settings. Maybe using environment variables or a conf.yml.
My configuration
I currently use your hesk image using docker-compose and mariadb.
My docker-compose.yml looks like this:
Best regards,
Kamino
The text was updated successfully, but these errors were encountered: