-
-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathdefault.yaml
89 lines (78 loc) · 3.12 KB
/
default.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
# The location information is passed on the the server
location:
# The name of this location
name: "default"
# The type of tests that you can run
setup:
- name: "Desktop Browsers"
type: "desktop"
# If you do not use Docker, you need to make sure you
# install the browsers yourself
browsers: ["chrome", "firefox", "edge"]
connectivity: ["native", "3g", "4g", "cable"]
# If you choose to run sitespeed.io docker containers make sure
# to run: sudo modprobe ifb numifbs=1
# on the host so that setting connectivity will work
# Also remember that localhost inside the container isn't automatically
# the same as localhost on the server:
# https://www.sitespeed.io/documentation/sitespeed.io/docker/#access-localhost
# That means if you run everything locally and want to use sitespeed.io docker
# containers, you need to set --s3.endpoint to something else than 127.0.0.1.
# On Mac you can use --s3.endpoint http://host.docker.internal:9000 and on Linux
# you can use your actual IP.
useDocker: false
- name: "Emulated Mobile"
type: "emulatedMobile"
browsers: ["chrome"]
connectivity: ["native", "3g", "4g", "cable"]
useDocker: false
# Here's an example of setting up a Android phone
#- name: "Android"
# type: "android"
# browsers: ["chrome", "firefox"]
# model: "Moto G5"
# deviceId: "ZY322MMFZ2"
# useDocker: false
# connectivity: ["native"]
# Where to connect to the message broker that is a Redis like thing
redis:
port: null
host: null
password: jgsay7f2fgfgda6acCa7g()jaba51!
tls: null
# Verbose log level or not
log:
verbose: false
# The default sitespeed.io configuration file used by the sitespeed.io instance
# It will be merged by the server sitespeed.io config and what you add in the
# cli or gui. If you use a Docker container, make sure to map a volume and use
# the full path to the configuration file
# sitespeedioConfigFile:
# The working directory for the testrunner, where it temporary will put it files
# By default it used the os.tmpdir
# workingDirectory: "."
# The sitespeed.io executable. The default is a globally installed sitespeed.io
executable: "sitespeed.io"
# If you run sitespeed.io using Docker this is the container that is used.
# If you use the majir, make sure to docker pull the container once a day
# to get the latest major version update.
# extraparameters will be passed on to Docker, between docker run and the container name
# baselinedir is the directory that is mapped where baseline data is stored
docker:
container: "sitespeedio/sitespeed.io:35"
extraparameters: "--cap-add=NET_ADMIN"
#baselinedir: "$(pwd)"
# The number of jobs to keep in the queue
# Depending on how many jobs you run and how much memory
# you have on your Redis/KeyDb instance you can tune this
queue:
removeOnComplete: 50
removeOnFail: 50
sitespeed.io:
s3:
endpoint: "http://127.0.0.1:9000"
bucketname: "sitespeedio"
key: "sitespeedio"
secret: "tracksofmytears"
region: "motown"
resultBaseURL: "http://127.0.0.1:9000/sitespeedio"