Ask HN: What server setups should I test my new self-hosted app on?
I'm currently running a small ISV, developing a self-hosted (on a LAMP stack web server) analytics package.
We've just hit the alpha testing stage, and I'm wanting to make sure that our app runs on as wide a range of web server environments as possible.
It's designed to be installed on a LAMP stack, so I'm trying to think of all the ways that stack could be configured which could cause us problems.
Currently, on the list I have:
* Test as many distros as reasonably possible, including Ubuntu, Fedora, CentOS, Debian.
* Test versions of PHP back to 5.2
* Test older versions of MySQL
* Test drop-in replacements for MySQL like MariaDB.
What else should I be testing? What other configurations, settings, modules etc have you seen cause problems for a simple PHP/Mysql app?
All suggestions gratefully received!
2 comments
[ 1.9 ms ] story [ 11.8 ms ] thread- Other OS: Windows, OSX at least.
- Prepackaged environments: WAMP, XAMPP, MAMP.
- PHP Modules that are not normally installed and that your app is using.
- How PHP works with Apache: mod_php, filters, CGI/FastCGI.
- NGINX.
- PHP interface with MySQL (mysql, mysqli). We only support mysqli but it's not always installed. Other times no support for MySQL is installed.
- Other databases if you allow them.
- You're probably not developing with the latest versions of PHP/MySQL, so check also incompatibilities with newer versions.
- Sessions / Cookies.
- Time settings can give problems also: different timezone between the server and PHP.
These are the ones I could think of right now. Installation is, by far, what's going to cause you the majority of support issues.
You app seems interesting, do you have anything to show?
We don't have anything much to show right now, but we hopefully will do soon.