Skip to content

ezBookkeeping #1856

Closed
Task
Closed
ezBookkeeping#1856
Task
Assignees
tremor021
Labels
Started Migration To ProxmoxVE

Description

@tremor021
tremor021
opened on May 23, 2026

Name of the Script

ezBookkeeping

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 not supported

📋 Script Details

community-scripts/ProxmoxVE#14590

Application
Name: ezBookkeeping
Website: ezbookkeeping.mayswind.net

Description
ezBookkeeping is an open source, lightweight, self-hosted personal finance app based on the premise of double-entry, which is the fundamentals to bookkeeping. It would be useful to have on Proxmox VE Helper-Scripts as it would allow people who are learning accountancy to easily deploy this software, but it can also help expand the range of budgeting software already offered on the Helper-Scripts site.

Activity

  1. tremor021
    self-assigned this
    on May 23, 2026
  2. tremor021
    added
    Ready For Testing
    on May 23, 2026
  3. tremor021
    moved this to In Progress (VED) in 🚀 Script Pipeline Overviewon May 23, 2026
  4. tremor021
    added this to 🚀 Script Pipeline Overviewon May 23, 2026
  5. tremor021
    added the
    Task
    issue type on May 23, 2026

  6. github-actions commented on May 23, 2026

    @github-actions
    github-actionsBot
    on May 23, 2026 – with GitHub Actions
    Contributor

    The ezbookkeeping script is ready for testing:
    bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/ezbookkeeping.sh)"
    Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

  7. CerberusStyle commented on Jun 1, 2026

    @CerberusStyle
    CerberusStyle
    on Jun 1, 2026

    Install, Web UI and account setup work,

    update function also works but settings are not persistent through update.

  8. tremor021 commented on Jun 1, 2026

    @tremor021
    tremor021
    on Jun 1, 2026
    MemberAuthor

    @mayswind can you lend us a hand here? Am i missing something while backing up current state of the app here:

    mkdir -p /opt/ezbookkeeping-backup
cp /opt/ezbookkeeping/conf/ezbookkeeping.ini /opt/ezbookkeeping-backup/
cp -r /opt/ezbookkeeping/data /opt/ezbookkeeping-backup/data/
cp -r /opt/ezbookkeeping/storage /opt/ezbookkeeping-backup/storage/

    This is the code snippet that handles backing up of the data before deploying a fresh tarball. Did i miss something that makes @CerberusStyle settings not restoring properly?

  9. mayswind commented on Jun 2, 2026

    @mayswind
    mayswind
    on Jun 2, 2026

    Install, Web UI and account setup work,

    update function also works but settings are not persistent through update.

    @CerberusStyle Which settings were not retained? The application configuration settings in conf/ezbookkeeping.ini, or the user settings and application settings after signing in?

  10. CerberusStyle commented on Jun 2, 2026

    @CerberusStyle
    CerberusStyle
    on Jun 2, 2026

    Login details are gone completely after update.

    1. Install
    2. Register account on WebUI and test logout/login and other basic settings.
    3. Force Update process as usual.
    4. Retest WebUI - account no longer present.

  11. mayswind commented on Jun 2, 2026

    @mayswind
    mayswind
    on Jun 2, 2026

    Based on the description that @CerberusStyle describes, it seems that all data was lost after the upgrade. I am not familiar with how @tremor021 implemented the deployment script. Looking at the https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/ezbookkeeping.sh file, it relies heavily on external functions. Since I do not have a Proxmox environment, I am unable to verify its behavior.

    However, I can provide some information about how ezBookkeeping handles its configuration and database, which may help with troubleshooting:

    1. ezBookkeeping loads configuration from environment variables with the highest priority (see the documentation: https://ezbookkeeping.mayswind.net/configuration/).
    2. For all other settings, if the conf-path application parameter is not specified, ezBookkeeping loads configuration from conf/ezbookkeeping.ini under the working directory by default.
    3. If no database type is configured, ezBookkeeping uses SQLite3 by default.
    4. The default SQLite database path is data/ezbookkeeping.db under the working directory.
    5. To verify whether the data was backed up correctly during the upgrade, compare the database file that contained data before the upgrade with the database file afterward. ezBookkeeping does not encrypt SQLite databases, so you can inspect them with any SQLite database management tool. In some cases, simply comparing the file sizes may already provide a useful indication.

  12. tremor021 commented on Jun 2, 2026

    @tremor021
    tremor021
    on Jun 2, 2026
    MemberAuthor

    @mayswind if our fetch_and_deploy_gh_release() functions confuses you, its just fetching the latest tagged release from the github repo and extracts it to specified directory:

    CLEAN_INSTALL=1 fetch_and_deploy_gh_release "ezbookkeeping" "mayswind/ezbookkeeping" "prebuild" "latest" "/opt/ezbookkeeping" "ezbookkeeping-*-linux-amd64.tar.gz"

    prebuild means its a custom named archive, not default source tarballs that are made on github, so its a simple function really.
    CLEAN_INSTALL=1 means that the destination directory should be deleted with rm -rf before extracting the archive. So its not possible for application to have some remnants of previous installs to interfere with the newest version.

    cp /opt/ezbookkeeping/conf/ezbookkeeping.ini /opt/ezbookkeeping-backup/
cp -r /opt/ezbookkeeping/data /opt/ezbookkeeping-backup/data/
cp -r /opt/ezbookkeeping/storage /opt/ezbookkeeping-backup/storage/

    Here i already back up the config ini and data + storage directories, which i restore few lines down in the script, after fetch_and_deploy_gh_release function is done extracting the archive:

    mv -f /opt/ezbookkeeping-backup/ezbookkeeping.ini /opt/ezbookkeeping/conf/
mv -f /opt/ezbookkeeping-backup/data /opt/ezbookkeeping/data/
mv -f /opt/ezbookkeeping-backup/storage /opt/ezbookkeeping/storage/
rm -rf /opt/ezbookkeeping-backup

    If what you say is correct, the script should be doing its job. New archive extracted to the directory, then restoring the data/storage directories + ini

    Weird.

  13. mayswind commented on Jun 3, 2026

    @mayswind
    mayswind
    on Jun 3, 2026

    I think this issue is actually quite straightforward. If you follow the approach described in item 5 above, you should be able to quickly determine whether there is a problem and, if so, where it is occurring.

    If @tremor021 can confirm that everything works correctly on your side, then @CerberusStyle should try the same verification method to identify where the issue lies.

  14. tremor021 commented on Jun 3, 2026

    @tremor021
    tremor021
    on Jun 3, 2026
    MemberAuthor

    Ah, i see the issue. @CerberusStyle can you try again in like 5 minutes?

    Somehow i completely disregard that directories are already there after the new release extraction. Should work fine now.

  15. CerberusStyle commented on Jun 3, 2026

    @CerberusStyle
    CerberusStyle
    on Jun 3, 2026

    Ah, i see the issue. @CerberusStyle can you try again in like 5 minutes?

    Somehow i completely disregard that directories are already there after the new release extraction. Should work fine now.

    ah that confused me for a sec as had not seen this message and it had suddenly started working, yes i can confirm all is now working correctly.

  16. tremor021
    added
    Migration To ProxmoxVE
    and removed
    Ready For Testing
    on Jun 3, 2026

  17. github-actions commented on Jun 3, 2026

    @github-actions
    github-actionsBot
    on Jun 3, 2026 – with GitHub Actions
    Contributor

    A PR has been created for ezbookkeeping: community-scripts/ProxmoxVE#14901

  18. github-actions
    added
    Started Migration To ProxmoxVE
    and removed
    Migration To ProxmoxVE
    on Jun 3, 2026

  19. michelroegl-brunner commented on Jun 3, 2026

    @michelroegl-brunner
    michelroegl-brunner
    on Jun 3, 2026
    Member

    Merged with #14901 in ProxmoxVE

  20. michelroegl-brunner
    closed this as completedon Jun 3, 2026
  21. github-project-automation
    moved this from In Progress (VED) to Done in 🚀 Script Pipeline Overviewon Jun 3, 2026

  22. github-actions commented on Jun 3, 2026

    @github-actions
    github-actionsBot
    on Jun 3, 2026 – with GitHub Actions
    Contributor

    Files deleted with PR #1890

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Started Migration To ProxmoxVE

Type

Task

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions