Had a look at nodeweaver's website - https://www.nodeweaver.eu

It looks interesting. They have a clear edge computing, IoT, Industry 4.0 focus on their product and their customers. So it's not a generic IT HCI product but rather geared towards those types of applications.

So what's the difference really? Well, the difference is that it's probably going to be managed by technicians and not IT. So it's design is likely geared towards easy of use and stability rather than towards bleeding edge features and lots of settings.

And also possibly tuned to run on very modest hardware as that is common feature of edge devices. It's also very likely that it is tuned for deterministic real time applications, which is common on edge devices and IIoT. KVM has PREEMPT-RT which are patches to give better performance for real time applications. Basically you want to know that an application will respond within a certain time, every time, regardless of what it is doing.

So this could be a good thing or a bad thing. Most things like real time patches improves things where it is needed but doesn't cause much performance loss where it is not needed. Anyway, as a product I think if you want a turn-key system it will probably be a good fit. If you want to be able to tinker with everything it will probably not be the right choice.

@JaredBusch said in WP-CLI and database users:

@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 [email protected] IDENTIFIED by '$DB_PASS';"
sudo mysql -e "GRANT ALL ON $DB_NAME.* TO [email protected];"
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 to this.

It's kind of f*cked up to have spaces in user names and passwords. Personally I don't use something unless it's specifically needed but either way works.

@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 [email protected] IDENTIFIED by '$DB_PASS';"
sudo mysql -e "GRANT ALL ON $DB_NAME.* TO [email protected];"
sudo mysql -e "FLUSH PRIVILEGES;"

Alright, after some troubleshooting. The line on your script should be:

sudo mysql -e "GRANT ALL ON $DB_NAME.* TO '$DB_USER'@'localhost';"

No ' around $DB_NAME. That gives you a syntax error.

Also since DB_USER doesn't contain spaces and neither does localhost, you don't need any ' around those either (but it doesn't cause any syntax errors).

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.

sudo mysql -uroot -p$DB_ROOT_PASS -e "CREATE USER [email protected] IDENTIFIED by '$DB_PASS';"
sudo mysql -uroot -p$DB_ROOT_PASS -e "GRANT ALL ON $DB_NAME.* TO [email protected];"
sudo mysql -uroot -p$DB_ROOT_PASS -e "FLUSH PRIVILEGES;"

I'm sure you know but you can also put more than one command in the execute string. ; is what separates the commands.
Or put the SQL in a file.
For instance:

sudo mysql -uroot -p$DB_ROOT_PASS -e "GRANT ALL ON $DB_NAME.* TO [email protected]; FLUSH PRIVILEGES;"

@JaredBusch said in WP-CLI and database users:

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

The DB_NAME is correct.....

I don't understand why. What happens if you just login and do it manually? Do you get the same result?

"Unknown database". To me that is related to the default database set in mysql sessions. Do you have a USE command somewhere?

Best action might be to test all the SQL commands manually instead of from the script.

@JaredBusch said in WP-CLI and database users:

@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:

@JaredBusch said in WP-CLI and database users:

ok a better example of my issue with WP-CLI and the database....

in my new guide to standing up WP I have this step.

I think this is a horrible solution. In order to let wp-cli create the dataabse, the WP DB user have to have the ability to actually CREATE a database.

So unlike more normal guides where I tell you to create a DB user with GRANT ALL only on the database it needs (dbname.*), I had to create it with GRANT ALL on everything (*.*).

I guess, I could refrain from setting the root password stuff until the very end and first revoke these permission and then re-add with only GRANT ALL on the specific database.

But that just seems stupidly clunky.

I think you are mistaken. Just grant the privileges to the database you are about to create

 sudo mysql -e "GRANT ALL ON '$DB_NAME'.* TO '$DB_USER'@'localhost';"

then you can do the wp-cli stuff like wp config create, wp db create etc.

My results on a google search were unclear. So I went assuming no as that is illogical to me.

But wouldn't be the first time something illogical to me was fact.

Well, it's very logical to me. And I just confirmed on MariaDB 10.1.44 that it works the way I thought it did.

Privileges are dependent on object names and not a particular object. Therefor the rights to something on a database, table or whatever can be created before that something exists.

Well that works for me. I'll update the guide in a bit and then run through a new deployment as a test.

Great. I like the guides you post, they are very well thought out.

@JaredBusch said in WP-CLI and database users:

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

@JaredBusch said in WP-CLI and database users:

ok a better example of my issue with WP-CLI and the database....

in my new guide to standing up WP I have this step.

I think this is a horrible solution. In order to let wp-cli create the dataabse, the WP DB user have to have the ability to actually CREATE a database.

So unlike more normal guides where I tell you to create a DB user with GRANT ALL only on the database it needs (dbname.*), I had to create it with GRANT ALL on everything (*.*).

I guess, I could refrain from setting the root password stuff until the very end and first revoke these permission and then re-add with only GRANT ALL on the specific database.

But that just seems stupidly clunky.

I think you are mistaken. Just grant the privileges to the database you are about to create

 sudo mysql -e "GRANT ALL ON '$DB_NAME'.* TO '$DB_USER'@'localhost';"

then you can do the wp-cli stuff like wp config create, wp db create etc.

My results on a google search were unclear. So I went assuming no as that is illogical to me.

But wouldn't be the first time something illogical to me was fact.

Well, it's very logical to me. And I just confirmed on MariaDB 10.1.44 that it works the way I thought it did.

Privileges are dependent on object names and not a particular object. Therefor the rights to something on a database, table or whatever can be created before that something exists.

Or in this case, give the right to a user to create a database before that database exists.

@hobbit666 said in What Are You Doing Right Now:

Home lab cleanup. Going to see if I can get the front off to clean the vents, but looks like I need to pull everything out.

Also going to consider installing a new hypervisor, KVM, XCP-NG, etc etc

What did you do to that poor machine???

Don't know if you have access to it but the best way to get remove dust is to blow it out with compressed air, preferably from an air compressor. Otherwise it's very difficult to get the dust that is inside things like power supplies.

@JaredBusch said in WP-CLI and database users:

ok a better example of my issue with WP-CLI and the database....

in my new guide to standing up WP I have this step.

I think this is a horrible solution. In order to let wp-cli create the dataabse, the WP DB user have to have the ability to actually CREATE a database.

So unlike more normal guides where I tell you to create a DB user with GRANT ALL only on the database it needs (dbname.*), I had to create it with GRANT ALL on everything (*.*).

I guess, I could refrain from setting the root password stuff until the very end and first revoke these permission and then re-add with only GRANT ALL on the specific database.

But that just seems stupidly clunky.

I think you are mistaken. Just grant the privileges to the database you are about to create

 sudo mysql -e "GRANT ALL ON '$DB_NAME'.* TO '$DB_USER'@'localhost';"

then you can do the wp-cli stuff like wp config create, wp db create etc.

@scottalanmiller said in What Are You Watching Now:

@Pete-S said in What Are You Watching Now:

Just watched Bad Boys for Life. Good fun!

On Netflix yet?

Don't think so, not yet at least. Netflix is mostly older movie releases or their own limited production.
New stuff you have to buy from Amazon Prime, iTunes and such. Or find it in some dark corner of the web.

Usually it first the cinema release, then after close to six months the VOD & Bluray release and then when most of those sales are done it will be available on things like netflix and cable. Coronavirus have made the movie execs move up the VOD release dates though and postpone cinema release dates.