Suggestion: centralized configuration file for easier customization

[GSEPE]

This is not exactly a bug but rather a difficulty I'm experiencing.

The Docker setup works perfectly, but I'm struggling with customization.
The only parameter I can successfully configure is baseURLFlag in main.go, where I set my self-hosted URL. However, any other modification in this file or in other repository files seems not to have taken effect.

It would be great to have a configuration file (e.g., config.*) where all modifiable parameters are centralized. This could include base_url, admin/user credentials, various true/false flags, ports, and possibly options for enabling reCAPTCHA. Passwords could also be hashed on the first script execution.

I understand many of these parameters might already be configurable within the binary for quick setup. However, even if I prefer docker, I cannot start it. Even after launching the binary as indicated in the Makefile, I received the following error:

Unable to connect to the database: Unable to ping the database: db:5432

The docker compose -f ci.yml up --abort-on-container-exit exits with the error code 0, so the test is successful (genius move having this script).
(yes, I run docker compose without the -)

`docker version`

Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-130-generic x86_64)

Client: Docker Engine - Community
 Version:           27.5.1
 API version:       1.47
 Go version:        go1.22.11
 Git commit:        9f9e405
 Built:             Wed Jan 22 13:41:31 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          27.5.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.11
  Git commit:       4c9b3b0
  Built:            Wed Jan 22 13:41:31 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.25
  GitCommit:        bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc:
  Version:          1.2.4
  GitCommit:        v1.2.4-0-g6c52b3f
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

I'm not expecting an immediate fix or reply; I sincerely appreciate this open-source project and the website you provide.
Neither of these should be taken for granted, let alone supporting users like me struggling to figure things out.

So, thank you!

[espebra]

Thank you for the report. I suspect that both #36 and #61 are related to this, and that it would be nice to improve in this area.

I'm thinking initially that an entrypoint.sh script that reads configuration from environment variables would be an improvement. What do you think? It would be nice to avoid a new configuration file when parameters can already be set on the command line or via environment variables.

[GSEPE]

Hello there,

Regarding the issue

#36

I can confirm that I have no problem with port 9000 since I used a clean server with nothing else installed. In fact, only when the filebin docker is running,
sudo netstat -pnlt | grep ':9000'
returns
tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 44276/docker-proxy
otherwise, nothing.

As for the error

#61

it seems that I have the same problem, but it only occurs when trying to download a single file.

Indeed, when I click the "Download File" button near the single file line (see image attached), the URL provided points to an internal hostname (storage:9000) instead of the public hostname (e.g. mydomain.com:9000). As a result, the download isn't working correctly, and I see errors like NS_ERROR_UNKNOWN_HOST in the dev tools.

The link to which this Download file button points is:
http://storage:9000/filebin/.../...

On the other hand, when downloading the entire bin in tar or zip format, this problem does not occur since the URL
https://mydomain.com/archive/bvj.../zip
is called.

I believe that all this indeed depends on the system initialization parameters (at least regarding docker). On the other hand, the fact that I continue to receive the error
Unable to connect to the database: Unable to ping the database: db:5432
when running the binary ./artifacts/filebin2-linux-amd64 --... remains a mystery.

So, for me, the creation of a script entrypoint.sh that allows us to input all the parameters in order to customize the environment is a gigantic YES ^_^

Additionally, I would also include the possibility of customizing the length parameter of the GenerateId function in the file dbl/bin.go to allow for shorter URLs, so there is no need to use a URL shortener in minimal environments such as private implementations.

edit:
I want to add that I initially mentioned a configuration file containing all the customizable system parameters. It seemed to me like the most resilient way to avoid reconfiguring everything from scratch whenever the service is restarted or an update is performed. However, I'm sure that the solutions you come up with will be the best.

Thank you again for your time and effort.