Skip to content

Commit f9dc92a

Browse files
committed
Modify db host
1 parent 4d59e47 commit f9dc92a

File tree

4 files changed

+23
-20
lines changed

4 files changed

+23
-20
lines changed

.travis.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ before_script:
1717
echo "xdebug.ini does not exist"
1818
fi
1919
- ./ci/prepare.sh
20+
- ls -al /ets/mysql
21+
- ls -al /ets/mysql/conf.d
2022

2123
script:
2224
- cd "$TRAVIS_BUILD_DIR/../easyengine"

features/bootstrap/FeatureContext.php

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -409,6 +409,7 @@ public static function cleanup(AfterFeatureScope $scope)
409409
'wp-local-redis.test',
410410
'wp-local-db-redis.test',
411411
'wp-remote-db-local-redis.test',
412+
'wp-remote-db-global-redis.test',
412413

413414
];
414415

features/labels.feature

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,3 +7,23 @@ Feature: Container Labels
77
"""
88
io.easyengine.site=labels.test
99
"""
10+
11+
Scenario: Create WordPress site with remote DB and local redis
12+
When I run 'bin/ee site create wp-remote-db-local-redis.test --cache --type=wp --dbuser="root" --dbpass="" --dbhost="localhost" --with-local-redis'
13+
Then After delay of 2 seconds
14+
And The site 'wp-remote-db-local-redis.test' should have webroot
15+
And The site 'wp-remote-db-local-redis.test' should have WordPress
16+
And Request on 'wp-remote-db-local-redis.test' should contain following headers:
17+
| header |
18+
| HTTP/1.1 200 OK |
19+
And Check local redis cache for 'wp-remote-db-local-redis.test'
20+
21+
Scenario: Create WordPress site with remote DB and global redis
22+
When I run 'bin/ee site create wp-remote-db-global-redis.test --cache --type=wp --dbuser="travis" --dbpass="" --dbhost="127.0.0.1"'
23+
Then After delay of 2 seconds
24+
And The site 'wp-remote-db-global-redis.test' should have webroot
25+
And The site 'wp-remote-db-global-redis.test' should have WordPress
26+
And Request on 'wp-remote-db-global-redis.test' should contain following headers:
27+
| header |
28+
| HTTP/1.1 200 OK |
29+
And Check local redis cache for 'wp-remote-db-global-redis.test'

features/site.feature

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -218,23 +218,3 @@ Feature: Site Command
218218
| header |
219219
| HTTP/1.1 200 OK |
220220
And Check local redis cache for 'wp-local-db-redis.test'
221-
222-
Scenario: Create WordPress site with remote DB and local redis
223-
When I run 'bin/ee site create wp-remote-db-local-redis.test --cache --type=wp --dbuser="root" --dbpass="" --dbhost="localhost" --with-local-redis'
224-
Then After delay of 2 seconds
225-
And The site 'wp-remote-db-local-redis.test' should have webroot
226-
And The site 'wp-remote-db-local-redis.test' should have WordPress
227-
And Request on 'wp-remote-db-local-redis.test' should contain following headers:
228-
| header |
229-
| HTTP/1.1 200 OK |
230-
And Check local redis cache for 'wp-remote-db-local-redis.test'
231-
232-
Scenario: Create WordPress site with remote DB and global redis
233-
When I run 'bin/ee site create wp-remote-db-global-redis.test --cache --type=wp --dbuser="travis" --dbpass="" --dbhost="127.0.01"'
234-
Then After delay of 2 seconds
235-
And The site 'wp-remote-db-global-redis.test' should have webroot
236-
And The site 'wp-remote-db-global-redis.test' should have WordPress
237-
And Request on 'wp-remote-db-global-redis.test' should contain following headers:
238-
| header |
239-
| HTTP/1.1 200 OK |
240-
And Check local redis cache for 'wp-remote-db-global-redis.test'

0 commit comments

Comments
 (0)