I'm running Apache 2.4.6 on openSUSE 13.1 and I want to do a little web development, mostly php scripting. Therefore, I have installed eclipse mars for php developers.

HTML and php files I put in the right directory as poited out by instructions, i.e. /srv/www/htdocs/ are indeed process and correctly, e.g. If I put newfile.php in that folder, I get the correct output on localhost/newfile.php. Now the problem is that the server cannot access files in the workspace. I have tried several approaches so far: • Symlink from /srv/www/htdocs/ to /path/to/workspace/. This changed the output from the server from '404 Object not found' to '403 Access denied', even though I gave complete access starting from /. • Giving access to the directory by editing httpd.conf, like Require all granted • Setting up the server in Eclipse using the pathmapping.

• Putting a new workspace in /srv/www/htdocs/. But already when I want to access a file at localhost/workspace/file.php I get '404 Object not found' Yet nothing showed the desired effect. Since I only need the access for development purpose and the network is protected from outside even workarounds would be fairly acceptable to me, though a more correct way to do it would, of course, be preferable.

I am reading a nice article about upgrading php on mac os x mountain lion. At the Install part of the document the author says that the user must execute a multiple line configure command. How to execute a multiple line configure command using Mac OS X terminal? At the Install part of the document the author says that the user must. Magento 2.0.18 is the final 2.0.x release. After March 2018, Magento 2.0.x will no longer receive security patches, quality fixes, or documentation updates. To maintain your site's performance, security, and PCI compliance, upgrade to the latest version of Magento.

Edit: Solution The issue that caused the problem was as simple as it was fatal. The openSUSE firewall blocked the port 80. Now the solution with transferring the eclipse workspace into /srv/www/htdocs/ is working. The correct way to do what you want is almost always to use some kind of deployment stage. For a purely internal or experimental setup, this can be something as simple as a script that runs rsync -a --delete./* /srv/www/htdocs.

(Specifying the source files using./* reduces the risk of unusual file names causing issues during the copy process.) You can then, if needed, amend the deployment script to make further changes, such as: make any applicable changes to configuration files, set ownership and permissions on files and directories, delete things that aren't supposed to be available to the web server (.gitignore anyone?), etc. This way, the web server can be configured without any specific regard for the development side needs. Let Eclipse have things its way, and let Apache have things its way. It shouldn't be too hard to configure Eclipse to run such a script when 'building' the software, if you want a one-stop solution workflow.