You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -171,8 +171,8 @@ After running these steps, the Pulsar Manager is running locally at http://127.0
171
171
172
172
If you are deploying Pulsar Manager 0.1.0 using the released container, you can log in the Pulsar Manager UI using the following credentials.
173
173
174
-
* Account: `pulsar`
175
-
* Password: `pulsar`
174
+
* Account: `pulsar`
175
+
* Password: `pulsar`
176
176
177
177
If you are deploying Pulsar Manager using the latest code, you can create a super-user using the following command. Then you can use the super user credentials to log in the Pulsar Manager UI.
178
178
@@ -189,7 +189,7 @@ After running these steps, the Pulsar Manager is running locally at http://127.0
189
189
* `backend-service`: The IP address or domain name of the backend service.
190
190
* `password`: The password should be more than or equal to 6 digits.
191
191
192
-
2. Create an environment.
192
+
2. Create an environment.
193
193
194
194
An environment represents a Pulsar instance or a group of clusters you want to manage. A Pulsar Manager is capable of managing multiple environments.
195
195
@@ -228,12 +228,12 @@ Use the default account (`pulsar`) and the default password (`pulsar`) to log in
228
228
229
229
### Configure environment
230
230
231
-
The puslar-manager supports multiple environment configurations and can manage multiple environments conveniently.
231
+
The pulsar-manager supports multiple environment configurations and can manage multiple environments conveniently.
232
232
233
233
Here, the service URL represents the service IP address of the broker. If you run Pulsar manager in the standalone mode, it should be set to "http://127.0.0.1:8080".
234
-
You can easily find it in the client.conf file of your pulsar-manager.
234
+
You can easily find it in the client.conf file of your pulsar-manager.
235
235
236
-
And the bookie URL represents the service IP address of the bookkeeper. If you run Pulsar manager in the standalone mode, it should be set to "http://127.0.0.1:6650".
236
+
And the bookie URL represents the service IP address of the bookkeeper. If you run Pulsar manager in the standalone mode, it should be set to "http://127.0.0.1:6650".
@@ -286,7 +286,7 @@ Because the code for connecting the casdoor has been added in Pulsar-manager, we
286
286
287
287
#### Step1. Deploy Casdoor
288
288
289
-
Firstly, the Casdoor should be deployed.
289
+
Firstly, the Casdoor should be deployed.
290
290
291
291
You can refer to the Casdoor official documentation for the [Casdoor](https://casdoor.org/docs/overview)
292
292
@@ -298,7 +298,7 @@ After a successful deployment, you need to ensure:
298
298
299
299
Then you can quickly implement a casdoor based login page in your app with the following steps.
300
300
301
-
#### step2. Configure Casdoor
301
+
#### step2. Configure Casdoor
302
302
303
303
Configure casdoor can refer to [casdoor](https://door.casdoor.com/login)(Configure casdoor's browser better not use one browser with your develop browser).
0 commit comments