project’s policy regarding database dependencies?

[SunFlowerOwl]

Hi,
I’m currently working on installation scripts for Redmine and MantisBT. Both applications require a database to function.

My question is about the project’s policy regarding database dependencies:
Should the script only install the application (leaving it non-functional until the user sets up and configures their own database URL), or should it also include the database installation in which case I’d have to choose the database type for the user (MySQL, PostgreSQL, etc.)?

I noticed that the Gitea installation script doesn’t embed a database. Instead, the application itself prompts the user to provide the database URL. The user can still access the app, so technically it works but in a specific way.

[tremor021]

msg_info "Installing Dependencies"
$STD apt-get install -y git
$STD apt-get install -y sqlite3
msg_ok "Installed Dependencies"

Gitea uses sqlite3

[SunFlowerOwl]

I should have made it clearer sorry: do you prefer separating the database into its own container, or should we choose and fully set up a database for the user so that they can access the application UI immediately after installation?

[michelroegl-brunner]

Ususlly we do the second one, add the db and make it so the app runs. Otherwise it would be a bit silly. Lool at snipe-it for example

[tremor021]

@SunFlowerOwl I mean, if app has a .env variable that enables specifying of database host, nothing really stops you from making your own db LXC then point all the apps you want to it.

We make our LXCs a self containing units, meaning app and db and w/e other service is needed we keep inside one container. This makes it not reliable on you having external databases or services, everything is in one LXC to manage.

[SunFlowerOwl]

Ok, thank you for your answers, @tremor021 1 and @michelroegl-brunner. That makes sense to me that the application should work right after the installation, and if a user is knowledgeable enough to want a different database, they should be able to change it themselves via the config file and then remove package from the container.

[tremor021]

That is correct. A lot of people really just want their apps to work out of the box, we are trying to deliver that.
If you have knowledge to adapt it to your own needs, we encourage you to do it.