Now, the paths are embedded in the system, so you need to make sure that you use the correct binary. We need to transfer our PHP and HTML files: htdocs]# cp /home/usr-1/htdocs/*.php htdocs]# cp /home/usr-1/htdocs/*.html htdocs]# lampp]# cp /home/usr-1/config.php lampp]# lampp]# XAMPP: Do you want to change the password? XAMPP: The FTP password is still set to 'lampp'. XAMPP: Change phpMyAdmin's authentication method. XAMPP: Write the password somewhere down to make sure you won't forget it!!! XAMPP: Setting phpMyAdmin's pma password to the new one. XAMPP: The MySQL/phpMyAdmin user pma has no password set!!! XAMPP: Your XAMPP pages are NOT secured by a password. Don’t even dink around on the web page: usr-1]# /opt/lampp/lampp security Really, before you do anything else, secure it. XAMPP: Starting Apache with SSL (and PHP5). To get the app up and running on GNU/Linux, we first need to install XAMPP: usr-1]# ls usr-1]# ls usr-1]# tar -xzf xampp-linux-1.4.16.tar.gz -C usr-1]# /opt/lampp/lampp start We initially developed the application on OS X. Our GNU/Linux box, for instance, already has Apache and MySQL on it however, it is very easy to isolate the database and configuration of PHP, as well as maintain consistent operation between platforms using XAMPP. It will run on a specific user’s machine. Further, the target audience for this may very well use XAMPP to run the application, since it is not a public application. Most of the work is done on OS X, but we also do some work on GNU/Linux. This project is perfect for maintaining a cross platform dev environment for an application we are currently working on.
We wrote about the XAMPP project in this article.
0 kommentar(er)
