ProxmoxVE: Actual Budget install/update breaks app β missing index.html in desktop-client
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
actual bedget
π What was the exact command used to execute the script?
bash -c β$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh)β
π Provide a clear and concise description of the issue.
After running the helper script to install or update Actual Budget on a Proxmox container, the application fails to start. When accessing it via browser, the following error is shown:
Error: ENOENT: no such file or directory, stat '/opt/actualbudget/packages/desktop-client/build/index.html'
βοΈ What settings are you using?
- Default Settings
- Advanced Settings
π₯οΈ Which Linux distribution are you using?
Debian 12
π Steps to reproduce the issue.
Step 1: Install or update actual budget Step 2: go to the URL of actual budget
β Paste the full error output (if available).
Error: ENOENT: no such file or directory, stat β/opt/actualbudget/packages/desktop-client/build/index.htmlβ
πΌοΈ Additional context (optional).
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 40 (12 by maintainers)
That is one of the reasons. Which is why we have repeatedly considered removing actualbudget completely. Their releases simply suck. Every time something is defective or something else.
Use at your own risk, I made this script to fix the issue on my system. Always back up first.
OK time to remove the Script. It makes no sense. It is 1:1 their documentation + the user message
apt Install yarn? Lol, yarn will be installed by NodeJS, not the old Debian repo thing. Dont do this
@c3kuperus sure, in a very insecure not maintainable way, not in a way that can be turned into a reusable, shareable script sadly.
@timtjtim I think that is a good idea to create a seperate install script for docker LXC then people can make there own chose.
okay. cool. but for now it is working.
@MickLesk how would you feel about a script that just used the docker LXC? I know thatβs not ideal as people want a βbare metalβ install rather than two layers of virtualisation, but it might be a suitable middle ground vs removing the script completely?
Then feel free to Push an issue there and they should check whats Missing. Its the 10 time in a half year, where this Script is broken. Maybe its better to use dockge or docker LXC
A git pull on a main branch is very very likely to give you broken code unless the team are exceptionally careful about what is merged in.
The only thing you should be running is a git tagged version, or youβre opening yourself up to a world of security vulnerabilities.
We dont use git. Then there Release package is broken (once again)
I cant do anything on the Script