Installing Wordpress on CentOS 7 Minimal

scottalanmiller

@travisdh1 said in Installing Wordpress on CentOS 7 Minimal:

@Tim_G said in Installing Wordpress on CentOS 7 Minimal:

Would it be hard to add the installation of phpMyAdmin into your guide?
yum install phpMyAdmin
Wouldn't normally do that, so much of a security risk if it's not properly managed/maintained.

Same here. Not recommended for normal use.

scottalanmiller

@Tim_G said in Installing Wordpress on CentOS 7 Minimal:

@travisdh1 said in Installing Wordpress on CentOS 7 Minimal:
@Tim_G said in Installing Wordpress on CentOS 7 Minimal:

Would it be hard to add the installation of phpMyAdmin into your guide?
yum install phpMyAdmin
Wouldn't normally do that, so much of a security risk if it's not properly managed/maintained.
For intranet-only it's fine. Different for external facing installs, but it is securable. Especially when using the whitelist approach.

It is, but for something like WordPress, no really use for it.

JaredBusch

@Tim_G said in Installing Wordpress on CentOS 7 Minimal:

Would it be hard to add the installation of phpMyAdmin into your guide?

I never use It, and as the others have said I would never want to have it installed.

scottalanmiller

And graphical tools like phpMyAdmin make instructions much harder. Telling someone to just "copy this command" is so easy. Telling someone to follow screen shot after screen shot of things to click on is not.

Obsolesce

@scottalanmiller said in Installing Wordpress on CentOS 7 Minimal:

@Tim_G said in Installing Wordpress on CentOS 7 Minimal:
@travisdh1 said in Installing Wordpress on CentOS 7 Minimal:
@Tim_G said in Installing Wordpress on CentOS 7 Minimal:

Would it be hard to add the installation of phpMyAdmin into your guide?
yum install phpMyAdmin
Wouldn't normally do that, so much of a security risk if it's not properly managed/maintained.
For intranet-only it's fine. Different for external facing installs, but it is securable. Especially when using the whitelist approach.
It is, but for something like WordPress, no really use for it.

I put it on internal servers because it's easier to set up databases and users for those databases at the same time for web servers that will be hosting multiple sites that need databases. Go to the web address, enter info in for new user and database, set permissions, done. Easy.

I personally do not know the command line way to do that, it's always been super easy and fast doing it through phpMyAdmin. When other people take over, it's very easy for them to do it.

I'm not going to choose not to install it just because there may be a possibility that I have to give someone step by step instructions on creating a database and user for MySQL on ML or SW... if it were in person, I'd just take the 25-30 seconds to bookmark the page and show them.

I'm not disagreeing with all of you, I'm just laying out my case usage. I have never installed phpMyAdmin on external facing servers. In cases where it was, it was due to the Webhost having it incorporated in cPanel for example, with no way to add databases via CLI or other real means.

Now that you have posted the CLI to do it, I already copied that down into my personal notes to do it that way in the future... so thanks for that. Very helpful.

scottalanmiller

@Tim_G said in Installing Wordpress on CentOS 7 Minimal:

I personally do not know the command line way to do that, it's always been super easy and fast doing it through phpMyAdmin. When other people take over, it's very easy for them to do it.

Every install guide has the command, making it super fast. And once you use it once, it is in your command history so you just "up arrow" and there it is.

mysql> CREATE DATABASE databasename;
mysql> GRANT ALL PRIVILEGES ON databasename.* TO "wordpressusername"@"hostname" IDENTIFIED BY "password";
mysql> FLUSH PRIVILEGES;

scottalanmiller

Obviously, you only create the database the first time. But that's how fast it is, just "create database name".

scottalanmiller

I like doing it from the CLI, even though phpMyAdmin is slick, because I only need one interface. Having to switch back and forth between SSH and web or something else is cumbersome and more things that I have to maintain. I've had databases where I need to do regular maintenance and then, definitely, that's the tool that I use. But for just initial setup tasks, I stick to the command line.

Obsolesce

@scottalanmiller said in Installing Wordpress on CentOS 7 Minimal:

I like doing it from the CLI, even though phpMyAdmin is slick, because I only need one interface. Having to switch back and forth between SSH and web or something else is cumbersome and more things that I have to maintain. I've had databases where I need to do regular maintenance and then, definitely, that's the tool that I use. But for just initial setup tasks, I stick to the command line.

Yeah, that's another point I didn't think about: it's never just initial setups that occur on a webserver. At least ones I deal with. Sure it can be fast to type in the commands fast to create a new database and user for it... but then when you have to export and import tables and such from other servers, among other things, I'd need to take a class on how to do it. And I can't stand around and school everyone or expect everyone I make contact with to pick up my documentation and do it all via CLI.

Most people just want an easy web browser bookmark, where they can visually go in an get things done without worrying about typing it all out on CLI and everything that involves.

I'm all about automation, scripting, etc... but only when it involves doing things more than once on the same or like systems.

There's a saying I like that goes something like... "If you have to do it twice, it should have been automated." lol

But anyways, I agree with you... initial set up, easy CLI... more involved work/maintenance = GUI (unless you're a trained SQL CLI admin or whatever) But even still, it's not always you who are going to be maintaining it after initial setup... it may not even be a technical fellow.

scottalanmiller

@Tim_G yeah, that's very different. For WordPress, normally you never touch the DB again, ever.

JaredBusch

Updated the instrucitons a bit to make the MySQL setup non interactive and fixed a missing bit of info for the httpd.conf.

JaredBusch

Thanks to @BRRABill it looks like I missed some SELinux issues.

Instructions updated, but this is what I needed to resolve his issues so far. He just installed, so maybe more updates to come

yum install -y policycoreutils-python
semanage fcontext -a -t httpd_sys_content_t '/opt/yourdomain(/.*)?'
restorecon -R /opt/yourdomain
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/yourdomain/wp-content(/.*)?'
restorecon -R /opt/yourdomain/wp-content

BRRABill

One other thing @JaredBusch and I discussed was the location in /opt and opposed to /var

In theory, it should not matter.

BRRABill

@JaredBusch

BTW, thanks for the writeup. Very good job.

JaredBusch

@BRRABill said in Installing Wordpress on CentOS 7 Minimal:

One other thing @JaredBusch and I discussed was the location in /opt and opposed to /var

In theory, it should not matter.

@scottalanmiller there was a discussion in a thread here a couple years ago around using /opt/ for wordpress installs. but I cannot find it. I think there was a reasoning from someone in there for that location.

scottalanmiller

@JaredBusch said in Installing Wordpress on CentOS 7 Minimal:

@BRRABill said in Installing Wordpress on CentOS 7 Minimal:

One other thing @JaredBusch and I discussed was the location in /opt and opposed to /var

In theory, it should not matter.

@scottalanmiller there was a discussion in a thread here a couple years ago around using /opt/ for wordpress installs. but I cannot find it. I think there was a reasoning from someone in there for that location.

Only thing I know of is that YUM using that location. But have no idea why.

JaredBusch

Looking into things I found this link. Granted this is about packaging for RPM but still.
https://fedoraproject.org/wiki/Packaging:Guidelines#Web_Applications

Web Applications

Web applications packaged in Fedora should put their content into /usr/share/%{name} and NOT into /var/www/. This is done because:

/var is supposed to contain variable data files and logs. /usr/share is much more appropriate for this.
Many users already have content in /var/www, and we do not want any Fedora package to step on top of that.
/var/www is no longer specified by the Filesystem Hierarchy Standard

scottalanmiller

@JaredBusch said in Installing Wordpress on CentOS 7 Minimal:

Looking into things I found this link. Granted this is about packaging for RPM but still.
https://fedoraproject.org/wiki/Packaging:Guidelines#Web_Applications

Web Applications

Web applications packaged in Fedora should put their content into /usr/share/%{name} and NOT into /var/www/. This is done because:

/var is supposed to contain variable data files and logs. /usr/share is much more appropriate for this.

Many users already have content in /var/www, and we do not want any Fedora package to step on top of that.

/var/www is no longer specified by the Filesystem Hierarchy Standard

Hmmm... point two I understand. It's already in use. But it was always in /var specifically because it is variable data, that's where upload caches and stuff go.

No idea about the hierarchy.

JaredBusch

@scottalanmiller said in Installing Wordpress on CentOS 7 Minimal:

@JaredBusch said in Installing Wordpress on CentOS 7 Minimal:

Looking into things I found this link. Granted this is about packaging for RPM but still.
https://fedoraproject.org/wiki/Packaging:Guidelines#Web_Applications

Web Applications

Web applications packaged in Fedora should put their content into /usr/share/%{name} and NOT into /var/www/. This is done because:

/var is supposed to contain variable data files and logs. /usr/share is much more appropriate for this.

Many users already have content in /var/www, and we do not want any Fedora package to step on top of that.

/var/www is no longer specified by the Filesystem Hierarchy Standard

Hmmm... point two I understand. It's already in use. But it was always in /var specifically because it is variable data, that's where upload caches and stuff go.

No idea about the hierarchy.

Looks like I got the /opt thing from you. Your LEMP challenge used /opt/wordpress.
https://mangolassi.it/topic/1082/the-wordpress-on-centos-lemp-challenge

Now I know there was a subsequent discussion somewhere on ML about /opt, I just cannot find it.

scottalanmiller

@JaredBusch said in Installing Wordpress on CentOS 7 Minimal:

@scottalanmiller said in Installing Wordpress on CentOS 7 Minimal:

@JaredBusch said in Installing Wordpress on CentOS 7 Minimal:

Looking into things I found this link. Granted this is about packaging for RPM but still.
https://fedoraproject.org/wiki/Packaging:Guidelines#Web_Applications

Web Applications

Web applications packaged in Fedora should put their content into /usr/share/%{name} and NOT into /var/www/. This is done because:

/var is supposed to contain variable data files and logs. /usr/share is much more appropriate for this.

Many users already have content in /var/www, and we do not want any Fedora package to step on top of that.

/var/www is no longer specified by the Filesystem Hierarchy Standard

Hmmm... point two I understand. It's already in use. But it was always in /var specifically because it is variable data, that's where upload caches and stuff go.

No idea about the hierarchy.

Looks like I got the /opt thing from you. Your LEMP challenge used /opt/wordpress.
https://mangolassi.it/topic/1082/the-wordpress-on-centos-lemp-challenge

Now I know there was a subsequent discussion somewhere on ML about /opt, I just cannot find it.

I have a feeling that it was or is the nginx default directory.