SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-30 01:32:43 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Bitmagnet: Config file location #1920

New Issue
Closed
opened 2025-11-20 05:19:56 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:19:56 -05:00
Owner
Copy Link

Originally created by @luismco on GitHub (Sep 20, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Bitmagnet

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/bitmagnet.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.13

📝 Provide a clear and concise description of the issue.

The configuration files listed on the script (/opt/bitmagnet/config.yml or /opt/bitmagnet/.env) do not exist or have other filenames.

🔄 Steps to reproduce the issue.

  • Run the script on the PVE console
  • Enter the LXC pct enter "Container ID"
  • List files on the described location ls -la /opt/bitmagnet
  • No config.yml or .env files found

❌ Paste the full error output (if available).

root@bitmagnet:~# ls -la /opt/bitmagnet/
total 46228
drwxr-xr-x 10 root root     4096 Sep 20 17:48 .
drwxr-xr-x  3 root root     4096 Sep 20 17:46 ..
-rwxr-xr-x  1 root root 47116580 Sep 20 17:48 bitmagnet
drwxr-xr-x  9 root root     4096 Sep 20 17:46 bitmagnet.io
-rw-r--r--  1 root root     1203 Sep 20 17:46 ci.Dockerfile
-rw-r--r--  1 root root     5486 Sep 20 17:46 CODE_OF_CONDUCT.md
-rw-r--r--  1 root root     5908 Sep 20 17:46 docker-compose.yml
-rw-r--r--  1 root root      460 Sep 20 17:46 Dockerfile
-rw-r--r--  1 root root      227 Sep 20 17:46 Dockerfile_dev
-rw-r--r--  1 root root       24 Sep 20 17:46 .dockerignore
-rw-r--r--  1 root root      147 Sep 20 17:46 .editorconfig
-rw-r--r--  1 root root       10 Sep 20 17:46 .envrc
-rw-r--r--  1 root root     1494 Sep 20 17:46 flake.lock
-rw-r--r--  1 root root      788 Sep 20 17:46 flake.nix
drwxr-xr-x  4 root root     4096 Sep 20 17:46 .github
-rw-r--r--  1 root root      490 Sep 20 17:46 .gitignore
-rw-r--r--  1 root root      200 Sep 20 17:46 .golangci.yml
-rw-r--r--  1 root root     8137 Sep 20 17:46 go.mod
-rw-r--r--  1 root root      258 Sep 20 17:46 goreleaser.Dockerfile
-rw-r--r--  1 root root     1964 Sep 20 17:46 .goreleaser.yml
-rw-r--r--  1 root root    73444 Sep 20 17:46 go.sum
drwxr-xr-x  6 root root     4096 Sep 20 17:46 graphql
drwxr-xr-x 30 root root     4096 Sep 20 17:46 internal
-rw-r--r--  1 root root     1079 Sep 20 17:46 LICENSE
drwxr-xr-x  2 root root     4096 Sep 20 17:46 licenses
-rw-r--r--  1 root root      148 Sep 20 17:46 main.go
drwxr-xr-x  2 root root     4096 Sep 20 17:46 migrations
-rw-r--r--  1 root root      535 Sep 20 17:46 .mockery.yml
drwxr-xr-x  3 root root     4096 Sep 20 17:46 observability
-rw-r--r--  1 root root      139 Sep 20 17:46 .prettierignore
-rw-r--r--  1 root root      221 Sep 20 17:46 README.md
-rw-r--r--  1 root root     3235 Sep 20 17:46 Taskfile.yml
-rw-r--r--  1 root root      191 Sep 20 17:46 tools.go
drwxr-xr-x  6 root root     4096 Sep 20 17:46 webui

🖼️ Additional context (optional).

The service runs fine, but the config files listed on the script do not exist or have other filenames.

Originally created by @luismco on GitHub (Sep 20, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Bitmagnet ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/bitmagnet.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.13 ### 📝 Provide a clear and concise description of the issue. The configuration files listed on the script (`/opt/bitmagnet/config.yml` or `/opt/bitmagnet/.env`) do not exist or have other filenames. ### 🔄 Steps to reproduce the issue. - Run the script on the PVE console - Enter the LXC `pct enter "Container ID"` - List files on the described location `ls -la /opt/bitmagnet` - No config.yml or .env files found ### ❌ Paste the full error output (if available). ``` root@bitmagnet:~# ls -la /opt/bitmagnet/ total 46228 drwxr-xr-x 10 root root 4096 Sep 20 17:48 . drwxr-xr-x 3 root root 4096 Sep 20 17:46 .. -rwxr-xr-x 1 root root 47116580 Sep 20 17:48 bitmagnet drwxr-xr-x 9 root root 4096 Sep 20 17:46 bitmagnet.io -rw-r--r-- 1 root root 1203 Sep 20 17:46 ci.Dockerfile -rw-r--r-- 1 root root 5486 Sep 20 17:46 CODE_OF_CONDUCT.md -rw-r--r-- 1 root root 5908 Sep 20 17:46 docker-compose.yml -rw-r--r-- 1 root root 460 Sep 20 17:46 Dockerfile -rw-r--r-- 1 root root 227 Sep 20 17:46 Dockerfile_dev -rw-r--r-- 1 root root 24 Sep 20 17:46 .dockerignore -rw-r--r-- 1 root root 147 Sep 20 17:46 .editorconfig -rw-r--r-- 1 root root 10 Sep 20 17:46 .envrc -rw-r--r-- 1 root root 1494 Sep 20 17:46 flake.lock -rw-r--r-- 1 root root 788 Sep 20 17:46 flake.nix drwxr-xr-x 4 root root 4096 Sep 20 17:46 .github -rw-r--r-- 1 root root 490 Sep 20 17:46 .gitignore -rw-r--r-- 1 root root 200 Sep 20 17:46 .golangci.yml -rw-r--r-- 1 root root 8137 Sep 20 17:46 go.mod -rw-r--r-- 1 root root 258 Sep 20 17:46 goreleaser.Dockerfile -rw-r--r-- 1 root root 1964 Sep 20 17:46 .goreleaser.yml -rw-r--r-- 1 root root 73444 Sep 20 17:46 go.sum drwxr-xr-x 6 root root 4096 Sep 20 17:46 graphql drwxr-xr-x 30 root root 4096 Sep 20 17:46 internal -rw-r--r-- 1 root root 1079 Sep 20 17:46 LICENSE drwxr-xr-x 2 root root 4096 Sep 20 17:46 licenses -rw-r--r-- 1 root root 148 Sep 20 17:46 main.go drwxr-xr-x 2 root root 4096 Sep 20 17:46 migrations -rw-r--r-- 1 root root 535 Sep 20 17:46 .mockery.yml drwxr-xr-x 3 root root 4096 Sep 20 17:46 observability -rw-r--r-- 1 root root 139 Sep 20 17:46 .prettierignore -rw-r--r-- 1 root root 221 Sep 20 17:46 README.md -rw-r--r-- 1 root root 3235 Sep 20 17:46 Taskfile.yml -rw-r--r-- 1 root root 191 Sep 20 17:46 tools.go drwxr-xr-x 6 root root 4096 Sep 20 17:46 webui ``` ### 🖼️ Additional context (optional). The service runs fine, but the config files listed on the script do not exist or have other filenames.
saavagebueno added the not a script issue label 2025-11-20 05:19:56 -05:00
saavagebueno commented 2025-11-20 05:19:57 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 20, 2025):

Have you read any documentation of this application?

https://bitmagnet.io/setup/configuration.html

Image

Choose how you want to configure the app and create either .env file or yaml.

@tremor021 commented on GitHub (Sep 20, 2025): Have you read any documentation of this application? https://bitmagnet.io/setup/configuration.html <img width="757" height="311" alt="Image" src="https://github.com/user-attachments/assets/d35a1a9c-b0e2-44db-9ae3-581485e96c99" /> Choose how you want to configure the app and create either .env file or yaml.
saavagebueno commented 2025-11-20 05:19:57 -05:00
Author
Owner
Copy Link

@luismco commented on GitHub (Sep 21, 2025):

Have you read any documentation of this application?

https://bitmagnet.io/setup/configuration.html
Image

Choose how you want to configure the app and create either .env file or yaml.

I did read the documentation. I do understand that it's not a script issue but it also doesn't seem obvious from the documentation that you have to create a config.yml yourself and that it's not something that is provided by the application or the way the scripts installs the application.

I appreciate the explanation, thanks.

@luismco commented on GitHub (Sep 21, 2025): > Have you read any documentation of this application? > > https://bitmagnet.io/setup/configuration.html > <img alt="Image" width="757" height="311" src="https://private-user-images.githubusercontent.com/58952836/491975558-d35a1a9c-b0e2-44db-9ae3-581485e96c99.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTg0NDcxNTMsIm5iZiI6MTc1ODQ0Njg1MywicGF0aCI6Ii81ODk1MjgzNi80OTE5NzU1NTgtZDM1YTFhOWMtYjBlMi00NGRiLTlhZTMtNTgxNDg1ZTk2Yzk5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA5MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwOTIxVDA5MjczM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTMyMDFiNTE5YjFiYTk4NWMxMTZkMzQ1NzJhYTliYWFkYjg4YjJlNjk4MjY0M2Y3NjQ3Mzk0YmZhNWZiZDE5NTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.w4inhaChX2ktSN42GNLJvMV7ZSWPOxTBB9e5COuFGmw"> > > Choose how you want to configure the app and create either .env file or yaml. I did read the documentation. I do understand that it's not a script issue but it also doesn't seem obvious from the documentation that you have to create a config.yml yourself and that it's not something that is provided by the application or the way the scripts installs the application. I appreciate the explanation, thanks.
saavagebueno commented 2025-11-20 05:19:57 -05:00
Author
Owner
Copy Link

@jvandervyver commented on GitHub (Sep 27, 2025):

The guidance here does not actually work, both of these files are ignored for me.

/opt/bitmagnet/config.yml
/opt/bitmagnet/.env

I ended up creating a symlink ln -s /opt/bitmagnet/config.yml /root/config.yml in order for the configuration file to work. I can only assume the working directory is /root

@jvandervyver commented on GitHub (Sep 27, 2025): The guidance here does not actually work, both of these files are ignored for me. ``` /opt/bitmagnet/config.yml /opt/bitmagnet/.env ``` I ended up creating a symlink `ln -s /opt/bitmagnet/config.yml /root/config.yml` in order for the configuration file to work. I can only assume the working directory is `/root`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1920
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?