Maintanance

[JoschaMiddendorf]

Is this container still maintained or did the project moved to another repo? I'd love to install akaunting in one container.

[carlos-jenkins]

Hi @JoschaMiddendorf

The repository is not currently being maintained. We hit an issue with the way Akaunting expects files to be and how it handles updates that is incompatible with the way we would persist volumes in a docker container.

Basically, there isn't an easy and safe way to upgrade when using a container because Akaunting wasn't designed with that in mind. It could be adapted, but that would imply that the core team at Akaunting is aware of the need and be willing to change the way updates are handled.

In other words, when you are running Akaunting in a container you would expect that only configuration and database is persisted in volumes. Currently that's not possible, you either do not persist the .env file or you persist the whole codebase. You may read more about this here: #1

On another side, we would also like for akaunting to stop upgrading itself from the webui, in particular if we are not persisting the codebase, as any update will be reverted when the containers is discarded or restarted. It creates an expectation on the user that the application is being updated when in reality it will not, plus that the data migrations may break the app when returning to an older version. Updates should come from a Docker new image. Which takes me to the next point.

Akaunting should release a container each time they do a release, so that their Docker users can always have an up-to-date, out-of-the-CI, new image with the release. That is, they would need to incorporate this or something similar in their workflows.

We stopped using Akaunting because of this issue.

Finally, while an all-in-one container sounded attractive some time ago, now I would be more inclined to do a Docker stack instead, which would be easier to maintain.

Sorry.

Regards.