-
Notifications
You must be signed in to change notification settings - Fork 1
/
firebase-debug.log
61 lines (54 loc) · 3.93 KB
/
firebase-debug.log
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
[debug] [2019-10-01T21:54:25.965Z] ----------------------------------------------------------------------
[debug] [2019-10-01T21:54:25.967Z] Command: C:\Program Files\nodejs\node.exe C:\Users\valeria.castillo\AppData\Roaming\npm\node_modules\firebase-tools\lib\bin\firebase.js init
[debug] [2019-10-01T21:54:25.967Z] CLI Version: 7.4.0
[debug] [2019-10-01T21:54:25.967Z] Platform: win32
[debug] [2019-10-01T21:54:25.967Z] Node Version: v10.15.1
[debug] [2019-10-01T21:54:25.969Z] Time: Tue Oct 01 2019 14:54:25 GMT-0700 (Pacific Daylight Time)
[debug] [2019-10-01T21:54:25.969Z] ----------------------------------------------------------------------
[debug]
[debug] [2019-10-01T21:54:25.977Z] > command requires scopes: ["email","openid","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]
[debug] [2019-10-01T21:54:25.977Z] > authorizing via signed-in user
[info]
######## #### ######## ######## ######## ### ###### ########
## ## ## ## ## ## ## ## ## ## ##
###### ## ######## ###### ######## ######### ###### ######
## ## ## ## ## ## ## ## ## ## ##
## #### ## ## ######## ######## ## ## ###### ########
You're about to initialize a Firebase project in this directory:
C:\Users\valeria.castillo\Desktop\Personal\Personal_Web_Projects\CafeLeChatChateau\CafeLeChatChateau
[info]
=== Project Setup
[info]
[info] First, let's associate this project directory with a Firebase project.
[info] You can create multiple project aliases by running firebase use --add,
[info] but for now we'll just set up a default project.
[info]
[debug] [2019-10-01T21:54:46.492Z] > refreshing access token with scopes: ["email","https://www.googleapis.com/auth/cloud-platform","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","openid"]
[debug] [2019-10-01T21:54:46.493Z] >>> HTTP REQUEST POST https://www.googleapis.com/oauth2/v3/token
<request body omitted>
[debug] [2019-10-01T21:54:46.958Z] <<< HTTP RESPONSE 200
[debug] [2019-10-01T21:54:46.980Z] >>> HTTP REQUEST GET https://firebase.googleapis.com/v1beta1/projects?pageSize=100
[debug] [2019-10-01T21:54:47.536Z] <<< HTTP RESPONSE 200
[info] i Using project cafelechatchateau (CafeLeChatChateau)
[info]
=== Firestore Setup
[debug] [2019-10-01T21:54:49.969Z] > command requires scopes: ["email","openid","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]
[debug] [2019-10-01T21:54:49.972Z] > authorizing via signed-in user
[debug] [2019-10-01T21:54:49.973Z] >>> HTTP REQUEST GET https://firebase.googleapis.com/v1beta1/projects/cafelechatchateau
[debug] [2019-10-01T21:54:50.394Z] <<< HTTP RESPONSE 200
[info]
[info] Firestore Security Rules allow you to define how and when to allow
[info] requests. You can keep these rules in your project directory
[info] and publish them with firebase deploy.
[info]
[debug] [2019-10-01T21:54:59.307Z] >>> HTTP REQUEST GET https://firebaserules.googleapis.com/v1/projects/cafelechatchateau/releases?pageSize=10&pageToken=
[debug] [2019-10-01T21:55:00.104Z] <<< HTTP RESPONSE 200
[debug] [2019-10-01T21:55:00.106Z] Found ruleset: projects/cafelechatchateau/rulesets/f5d534e1-a1f6-4c37-a626-8b202291600a
[debug] [2019-10-01T21:55:00.107Z] >>> HTTP REQUEST GET https://firebaserules.googleapis.com/v1/projects/cafelechatchateau/rulesets/f5d534e1-a1f6-4c37-a626-8b202291600a
[debug] [2019-10-01T21:55:00.347Z] <<< HTTP RESPONSE 200
[info]
[info] Firestore indexes allow you to perform complex queries while
[info] maintaining performance that scales with the size of the result
[info] set. You can keep index definitions in your project directory
[info] and publish them with firebase deploy.
[info]