@black3dynamite Can't argue a screenshot, but I swear i've installed Fedora 31 from scratch and not saw that. Maybe I haven't.

I was installing a new instance to test something in my colo and figured I would use Fedora 32.

Saw this right away

Guide updated. I left the ' everywhere else.

Of note, I had to drop the DB_NAME to 16 characters because it broke it longer. Even though current mariadb should accept much longer database names according to my quick google on the subject.

@Pete-S said in WP-CLI and database users:

@JaredBusch said in WP-CLI and database users:

@Pete-S said in WP-CLI and database users:

And when you use -e you should have it after user and password so the SQL commands you want to execute comes after the -e.

That was a once off artifact of me doing it on this system after the root password has been set.

OK, so maybe this then:

sudo mysql -e "CREATE USER $DB_USER@localhost IDENTIFIED by '$DB_PASS';"
sudo mysql -e "GRANT ALL ON $DB_NAME.* TO $DB_USER@localhost;"
sudo mysql -e "FLUSH PRIVILEGES;"

right. Updating the guide. but half tempted to leave the single quotes everywhere it that causes no error in order to protect against spaces by others. Though I am using pwgen to do this.

@Pete-S said in WP-CLI and database users:

I'm sure you know but you can also put more than one command in the execute string. ; is what separates the commands.

My guides are specifically wrote lik this to clearly separate the commands that are used for the people following my guides to see every thing they are doing.

@Pete-S said in WP-CLI and database users:

And when you use -e you should have it after user and password so the SQL commands you want to execute comes after the -e.

That was a once off artifact of me doing it on this system after the root password has been set.

That was also the reason it did not work for me as I tried without the '

@Pete-S said in WP-CLI and database users:

Do you have a USE command somewhere?

No, because when the script runs originally, there is no exisiting database to use.

@Pete-S well WTF... Even after the DB exists..

The DB_NAME is correct.....

[jbusch@jb-wp html]$ sudo mysql -e -uroot -p$DB_ROOT_PASS "GRANT ALL ON '$DB_NAME'.* TO '$DB_USER'@'localhost';"
ERROR 1049 (42000): Unknown database 'GRANT ALL ON 'ziiCh6geiqu6'.* TO 'eitaethie9cahX7u'@'localhost';'
[jbusch@jb-wp html]$ sudo mysql -e -uroot -p$DB_ROOT_PASS "GRANT ALL ON $DB_NAME.* TO '$DB_USER'@'localhost';"
ERROR 1049 (42000): Unknown database 'GRANT ALL ON ziiCh6geiqu6.* TO 'eitaethie9cahX7u'@'localhost';'
[jbusch@jb-wp html]$ cat wp-config.php | grep DB_NAME
define( 'DB_NAME', 'ziiCh6geiqu6' );
[jbusch@jb-wp html]$ 

looks pretty easy actually.

@stacksofplates said in Setup a Cloudflare Origin Certificate for use on a backend server:

@JaredBusch said in Setup a Cloudflare Origin Certificate for use on a backend server:

@stacksofplates said in Setup a Cloudflare Origin Certificate for use on a backend server:

@JaredBusch said in Setup a Cloudflare Origin Certificate for use on a backend server:

@stacksofplates said in Setup a Cloudflare Origin Certificate for use on a backend server:

This is what I did for my personal site. GitLab pages did support Let'sEncrypt but not automated renewals so it was kind of pointless to use that. So I set one of these up. I need to go back and change it now that fully automated renewals are available.

My question would be why use LE for that if you are using Cloudflare in front anyway? There is zero wrong with this type of origin certificate. If you are using Cloudflare, then it is a simple solution.

Oh it's just so I don't ever have to worry about renewing it. With GitLab Pages, I just check the box and it gives me a cert and auto renews for me. That's all.

Obviously nothing wrong with what you are doing. But since you had something in place, I was wondering why change.

Origin certs from Cloudflare have a default (and max) lifespan of 15 years. Since it should only be trusted by Cloudflare, there should be no need to use a shorter span cert.

Yeah I changed it to 5 when I did mine. I've always "preached" short cert life span since that's been a thing so it's dogfooding also.

I don't argue short lifespan is a good thing for frontend. but a backend origin cert? Especially is you validate the origin pull (not in my guide).