That are great news. Let me tell you my suggestions:
Beltran wrote:How to configure and enable FTP to access from other machines. How to configure it to give access for other developers.
Beltran wrote:How to configure Apache with VirtualHosts
How to create wildcard VirtualHosts
One of my Top "How to" Guides still Work in Progress.
Creating (namebased) Vhosts is a very common question/answer here
Well, these issues there are starting issues, so they have to be accessible even then Apache could not get started.
Beltran wrote:How to deploy a PHP application from GitHub
Great! I look forward to read this guide.
Beltran wrote:How to create/restore MySQL backups from command line and using phpMyAdmin
Again one very common issue, still on my todo for a guide.
Beltran wrote:How to configure sendmail or phpMailer for sending emails
I would like to read that.
How to install Bitnami add-ons on top of XAMPP
We will also add all the content of these guides in the ApacheFriends translation application http://translate.apachefriends.org/
so they will be also available for different languages soon
Beltran wrote:We need your help to know which other topics should we include in the new Welcome page for XAMPP. Any suggestion will be welcome!
I would like to see a structure change.
The central index.php should persist but should only contain the following information:
- Information that is displayed if the page is not requested correct (opened in the browser directly) and how to solve this, or a simple link to the correct requestable URL
- Maybe information about Apache starting issues (see above).
This page should NOT
contain a intransparent redirect because beginner commonly get confused.
The project folder of the welcome page should be renamed to something different. "xampp" as project folder can be confusing for beginners. Maybe "dashboard" is a good name for it, because it is something like a dashboard or could be.
Get rid of the /security section and the status page. They can be very confusing for beginners, because of false negatives. Issues after using the MySQL root password change or creating a folder protection are common.
A better way would be a guide how to change the password the proper way.
Beltran wrote:We also want to remove sample applications in the current XAMPP welcome page (like the CD collection example). They are a source of security issues and some users inadvertently leave them available from the outside.
I don't wish to remove all of them completely, because i think they can be a great inspiration for beginners.
But they should be simple enough and secure. They need a complete rewrite to get protected against SQL-Injections, Crosssite-Scripting (XSS) and Cross-Site Request Forgery (CSRF). This rewrite is still on my Todo-List.
I would get rid of biorhythm and instant art. I would leave one database driven application (cdcol) and maybe two or three new applications covering up to date techniques and topics (like Websockets, PHPUnit or emailing). They should all get independend database users (if needed) with only this permissions the application really needs (best practice).
I would like to see the XAMPP Welcome page to be a greater help for developing. We need ressources and tools that provide a more helpful platform.
I would like to see a project management / issue tracker in XAMPP welcome page, like traQ
Tutorials on the following topics would be great;
- Integrating different PHP versions in XAMPP (with FCGI and changing the current PHP version for a folder by .htaccess)
- activating/configurating XDebug
- activating/configurating PHPUnit
Ideas ideas ideas, but i don't have enough time by myself