I'm creating a lightweight bug tracker, and I'm really having difficulties with people that don't know how to deploy and connect to a MySQL database on their own.
What they should do is to create their database, and run my SQL source to create the tables required. They need to know the port, username, password and name of their database.
During this process, they also have to provide their own MySQL server... and compatible MySQL Connector... which also have to be compatible with my Mono .Net 2.0 environment (this is a bug tracker for Unity).
In the beginning, while my users are trying the application, I just want all this to go away. I don't want any ports, usernames, passwords to begin with.
Later, when they've opted to use my bugtracker, I'll accept that they need to know the port of the server, and maybe click their way through a "server creation process", to create a server that is separate from the demo application.
I'm playing with the thought of switching to SQLite, but according to peoples recommendations, this is best suited for single-user applications. That doesn't sound like a proper bug-tracker situation to me. With SQLite nobody will be able to scale their volume up.
Is there a way to include a whole MySQL/MariaDB server with my application and deploy it by the click of a button?