pkg_add php-fpm

[psypro]

Trying to follow guide at : http://www.h-i-r.net/p/setting-up-op...sed-httpd.html
(OpenBSD, httpd, mariadb, php)

Has php-fpm been removed, what replacement should i use?

Update:
The guide seems to work. php-fpm is now inclueded in php package.
Only issue remanining is permissions, and the guide does not deal with that.

[jggimi]

You are obviously using -current; but following a 3rd party "How To" guide.

Generally, when you have questions about a 3rd party "How To" you should really ask the author directly, rather than asking us about their guide.

Luckily, though, I happen to know the answer. For the upcoming 5.9 release, php-fpm was merged into the base php packages. If you have php installed, php-fpm is installed with it.

[psypro]

Thank you for clearing that up for me.

[psypro]

pkg_add php

Selected option : 5 (non ap2 version). rscripts were installed : /etc/rc.d/php56_fpm

/etc/rc.d/httpd stop

etc/httpd.conf

ext_if="egress"
 types { include "/usr/share/misc/mime.types" }
server "default" {
    listen on $ext_if port 80
    directory {index "index.php" }
    location "/*.php*" {
        root { "/htdocs" }
        fastcgi socket "/run/php-fpm.sock"
    }
    location "/*" {
        root { "/htdocs" }
    }
}

etc/rc.d/php56_fpm start

etc/rc.d/httpd start

Yes, now my server is serving php, now onto understanding more about sqlite3, and WordPress plugin for it.

[psypro]

On the positive side: WordPress have been installed and configured. Gave up sqlite3 and used mariadb.

The problem:
wp-content folder, where uploads go needs

/etc/httpd

ext_if="egress"
 types { include "/usr/share/misc/mime.types" }
server "default" {
    listen on $ext_if port 80
    directory {index "index.php" }
    location "/*.php*" {
        root { "/htdocs" }
        fastcgi socket "/run/php-fpm.sock"
    }
    location "/*" {
        root { "/htdocs" }
    }
}

Anybody have a solution idea?

[jggimi]

Can you help me to understand your problem? As I have never used WordPress before, I have replicated your environment in a virtual machine here.

WordPress is working, I was able to publish a blog post. This appears, for me, with a URL of http://<VM IP>/wordpress/

When I first attempted the top level http://<VM IP>/ I got an "Acccess Denied" because there was no index.php in /var/www/htdocs. When I added an index.php file, the error was eliminated.

I set the ownership of all files in /var/www/htdocs/wordpress to be world readable, but owned by root. PHP should not be able to write into those directories; that would be a significant security concern. These directories should be read-only to PHP and to the web server. (During WordPress install, the installer could not create the wp-config.php file, and gave me text to copy/paste into the file between steps.)

My WordPress userid and blog post are stored within the SQL database, not within /var/www/htdocs/wordpress.

[psypro]

Thank you again jggimi!
It motivated my efforts to know it was possible.
But regarding the permissions, try login in to your WordPress site, and upload a picture trough the web interface.
The site now, works : )

[jggimi]

Ah, ok. There are directories that must be writeable. But using 777 is not best practice. Even the folks at wordpress.org recommend against it. Writeable by your webserver application may be necessary. But 777 leaves it open to other applications.

You could set the ownership of the wp-content branch to www, for example. Or, use the www group to govern access.

To reset to a default filemode of 755 for directories and 644 for files in that branch, and ownership to www, something like this could be used:

# cd /var/www/htdocs/wordpress
# find -X wp-content -type d | xargs chmod 755
# find -X wp-content -type f | xargs chmod 644
# chown -R www wp-content