Bubba|two

[Tim]

On the flipside, MySQL has marketshare.

If you like something that is widely used try SQLite http://www.sqlite.org/mostdeployed.html instead of MySQL

SQLite is not a universal solution (don't use it for gigabytes+ of data), but if you need to quickly deploy a medium size data-driven website or use a local SQL file store, its performance and ease of use are difficult to beat - It also has native support by PHP 5 and Python. Downsides of SQLite are no GRANT/REVOKE (but would you use it on a simple web site?), VIEWS are not directly updateable (but can be done with triggers), triggers must be FOR EACH ROW, No FOREIGN KEYS (use triggers). You can probably tell that I am a fan Probably because I use C and Python.

You are right about Informix, I was involved in a large deployment on the MIPS platform in the 1980s - It was one of the most horrid jobs I have ever been given.

[carl]

A reason we have for using MySQL is the use-case of a non-über-techie developing an own web-page on the bubba. Probably the most known SQL-server for that person is MySQL.

[Tim]

A reason we have for using MySQL is the use-case of a non-über-techie developing an own web-page on the bubba. Probably the most known SQL-server for that person is MySQL.

Interesting commercial choice (not a criticism). I note that you are going to use Lighthttpd in BUBBA|TWO. So do we infer that you have sacrificed the most well known web-server (Apache), so that you then have the resources left to Run MySQL? - Please note that I actually prefer Lighthttpd to Apache. It, like SQLite, is designed for ease of use on small devices where resource allocation may be a problem.

A cynical person might infer that the main reason that you are using MySQL is because it is Swedish? (Joke!). I know we 'all' like MySQL, but for a newbie SQLite is easier (trust me) - It is a single file installation that is normally included in the standard PHP5 install so you don't even have to configure it.

I do have a legitimate reason for my caution concerning MySQL, whilst it is made available under a GPL licence, commercial distributions can require that a commercial licence is purchased from MySQL (and now, presumably, Sun). I used to write (and sometimes distribute) commercial software, so the licence was not suitable for me. The normal SQLite licence is 'Public Domain'.

So can you confirm that we, as users, are covered by a commercial licence if we use MySQL for any (potentially commercial) purpose?

[Binkem]

For me as a server noob its helpful that the bubba|two will run mySQL. I want to run my current (WordPress-based) site on the bubba. I know that there is a WordPress for SQlite, but keeping WordPress up to date and using add-ons is easier using mySQL.

[carl]

A reason we have for using MySQL is the use-case of a non-über-techie developing an own web-page on the bubba. Probably the most known SQL-server for that person is MySQL.

Interesting commercial choice (not a criticism). I note that you are going to use Lighthttpd in BUBBA|TWO. So do we infer that you have sacrificed the most well known web-server (Apache), so that you then have the resources left to Run MySQL? - Please note that I actually prefer Lighthttpd to Apache. It, like SQLite, is designed for ease of use on small devices where resource allocation may be a problem.

A cynical person might infer that the main reason that you are using MySQL is because it is Swedish? (Joke!). I know we 'all' like MySQL, but for a newbie SQLite is easier (trust me) - It is a single file installation that is normally included in the standard PHP5 install so you don't even have to configure it.

I do have a legitimate reason for my caution concerning MySQL, whilst it is made available under a GPL licence, commercial distributions can require that a commercial licence is purchased from MySQL (and now, presumably, Sun). I used to write (and sometimes distribute) commercial software, so the licence was not suitable for me. The normal SQLite licence is 'Public Domain'.

So can you confirm that we, as users, are covered by a commercial licence if we use MySQL for any (potentially commercial) purpose?

The MySQL commercial license is only required if you want to use MySQL is a product and you cant/wont follow the GPL or any appropriate FOSS licenses. As this is not the case for us (We are trying to follow the GPL to both the letter and the spirit), a commercial license isn't required, nor is it wanted (It would add a neat sum of 500$ to the cost per unit).

[Tim]

The MySQL commercial license is only required if you want to use MySQL is a product and you cant/wont follow the GPL or any appropriate FOSS licenses. As this is not the case for us (We are trying to follow the GPL to both the letter and the spirit), a commercial license isn't required, nor is it wanted (It would add a neat sum of 500$ to the cost per unit).

Thanks Carl. That is good...
/Tim

[carl]

The MySQL commercial license is only required if you want to use MySQL is a product and you cant/wont follow the GPL or any appropriate FOSS licenses. As this is not the case for us (We are trying to follow the GPL to both the letter and the spirit), a commercial license isn't required, nor is it wanted (It would add a neat sum of 500$ to the cost per unit).

Thanks Carl. That is good...
/Tim

There have been a change in the software setup; At least initially, we will ship with apache instead of lighttpd, due to a problem with lighty and uploading of files.

/Carl

[Hammer]

Nooo! Apache hasn't worked out for me on the Bubba 1, haven't been able to do any web site design at all.

This means I will have to reconsider my pre-order and perhaps go for a QNAP TS-509.

*sigh*

[carl]

Nooo! Apache hasn't worked out for me on the Bubba 1, haven't been able to do any web site design at all.

This means I will have to reconsider my pre-order and perhaps go for a QNAP TS-509.

*sigh*

We are going to do everything to make lighttpd work, though in the short term, to allow file upload via the web interface, lighty made it not possible.

/Carl

[solsson]

Is it easy to switch between lighthttpd and apache on port 80, and still run bubba's web-based tools?

I need to host a Subversion repository, which requires Apache2. As with the choice of database, I hope there is an easy way for users to switch, so we can stop fighting about which one is the best :) Switching is easy in Debian, so it all depends on the compatibility of the bubba packages.

/Staffan