Allow connections via databases.conf

[wolfgangreder]

Currently it is required to build the connection url with the full file path.
It would be nice to register databases in databases.conf

[fdcastel]

Could you elaborate a bit more?

What is your use case?

What problem would this intend to solve?

[wolfgangreder]

1. I am forced to use a (container internal) path in the jdbc url: eg. jdbc:firebirdsql://localhost:3050//var/lib/firebird/data/test.fbd instead of jdbc:firebirdsql://localhost:3040/test.
2. Per database configuration requires manipulation of database.conf.
3. I think it would be generally wise to allow externalization of configuration (not only database.conf), log files and security database. This would allow easy backup and restore.

[bothermenot]

you can mount databases.conf (firebird.conf, udf libraries directories) as volumes
eg. -v /path/to/databases.conf:/opt/firebird/databases.conf

[wolfgangreder]

you can mount databases.conf (firebird.conf, udf libraries directories) as volumes eg. -v /path/to/databases.conf:/opt/firebird/databases.conf

Well, that should be possible. See https://github.com/jacobalberty/firebird-docker

[bothermenot]

So when you mount databases.conf as suggested you should be able to connect to databases as defined in the file instead of using full container path

[fdcastel]

I am still uncertain about the potential benefits this offers, aside from adding boilerplate code to do something already solved by Docker.

To use database aliases, you may create your own databases.conf file and configure a Docker bind mount for it.

Why the image entrypoint.sh code should do this?