managedhostingpartners

We’ll test this with a couple of sites for a little while and see.

Ok, I had another look at it and this configuration works. Changes I made:

– simpler prefix
– use : at end of prefix, so that username cannot access data of username1
– remove non key-based commands from access string. Final result:

define('WP_REDIS_SCHEME','tls');
define('WP_REDIS_HOST','master.mhptls.3dltm0.apse2.cache.amazonaws.com');
define('WP_REDIS_PASSWORD',['www-testdemohub','*****']);
define( 'WP_REDIS_CLIENT', 'phpredis' );
define('WP_REDIS_PREFIX', 'www-testdemohub:');
define('WP_REDIS_SELECTIVE_FLUSH',true);

And access string

“on ~www-testdemohub:* +@all -scan -randomkey -keys -flushall -flushdb”

I dug out your offer for < 100 sites enterprise, but its still a little way off commercially.

Thanks again,

Jochen

• This reply was modified 2 years, 4 months ago by managedhostingpartners.

Hi Till,

thanks for the quick response.

Indeed I won’t need such long prefixes. However I’m concerned that site 1 can maliciously switch their redis database to site 2’s database, hence I am looking at using ACLs.

Is this support available on your paid product?

Jochen

Hi there,

have you had any further thoughts on the default setting of this field and why it is not usiung a simpler format?

Jochen

Ok, could you have a look at the response from Amazon Web Services here: https://serverfault.com/a/917563/81774

I wonder why the default is set as

\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@

instead of

\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0

Jochen

Here is also a quick test of default values for binary columns on MySQL 5.7.21. It seems Binary columns are already defaulted to \0

mysql> create table btest (t varchar(10) not null,bcol binary not null);
Query OK, 0 rows affected (0.01 sec)

mysql> show create table btest;
+-------+---------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                                        |
+-------+---------------------------------------------------------------------------------------------------------------------+
| btest | CREATE TABLE <code>btest</code> (
  <code>t</code> varchar(10) NOT NULL,
  <code>bcol</code> binary(1) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
+-------+---------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> insert into btest (t) values ('a');
Query OK, 1 row affected, 1 warning (0.00 sec)

mysql> select * from btest where bcol = "\0";
+---+------+
| t | bcol |
+---+------+
| a |      |
+---+------+
1 row in set (0.00 sec)

Hi there,

it is not created as MyISAM.

The way it is set up now, it won’t support point in time recovery on RDS, is there no other way to default this column?

Jochen

I have found an example on the web for S3 handling, which solves my problem:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1503142286000",
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::site-mysite.com",
                "arn:aws:s3:::site-mysite.com/*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": "s3:ListAllMyBuckets",
            "Resource": "arn:aws:s3:::*"
        }
    ]
}

• This reply was modified 7 years, 3 months ago by managedhostingpartners.