Update naming stuff

to reflect changes from the repo itself

Author: Haarolean

.gitignore

@@ -0,0 +1 @@
+.idea

README.md

@@ -1,13 +1,13 @@
 ---
-description: About Kafka-UI
+description: About Kafbat-UI
 ---
 
 # About
 
-**UI for Apache Kafka** is a versatile, fast, and lightweight web UI for managing Apache Kafka® clusters. Built by developers, for developers.
+**Kafbat UI** is a versatile, fast, and lightweight web UI for managing Apache Kafka® clusters. Built by developers, for developers.
 
 
 
 The app is a free, open-source web UI to monitor and manage Apache Kafka clusters.
 
-UI for Apache Kafka is a simple tool that makes your data flows observable, helps find and troubleshoot issues faster and delivers optimal performance. Its lightweight dashboard makes it easy to track key metrics of your Kafka clusters - Brokers, Topics, Partitions, Production, and Consumption.
+Kafbat UI is a simple tool that makes your data flows observable, helps find and troubleshoot issues faster and delivers optimal performance. Its lightweight dashboard makes it easy to track key metrics of your Kafka clusters - Brokers, Topics, Partitions, Production, and Consumption.

configuration/audit-log.md

@@ -1,6 +1,6 @@
 # Audit log
 
-Kafka-UI allows you to log all operations to your kafka clusters done within kafka-ui itself.
+Kafbat-UI allows you to log all operations to your kafka clusters done within kafbat-ui itself.
 
 Logging can be done to either kafka topic and/or console.
 

configuration/authentication/aws-iam.md

@@ -4,7 +4,7 @@ description: How to configure AWS IAM Authentication
 
 # AWS IAM
 
-UI for Apache Kafka comes with a built-in [aws-msk-iam-auth](https://github.com/aws/aws-msk-iam-auth) library.
+Kafbat UI comes with a built-in [aws-msk-iam-auth](https://github.com/aws/aws-msk-iam-auth) library.
 
 You could pass SASL configs in the properties section for each cluster.
 
@@ -29,7 +29,7 @@ docker run -p 8080:8080 \
     -e KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM=AWS_MSK_IAM \
     -e KAFKA_CLUSTERS_0_PROPERTIES_SASL_CLIENT_CALLBACK_HANDLER_CLASS=software.amazon.msk.auth.iam.IAMClientCallbackHandler \
     -e KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG=software.amazon.msk.auth.iam.IAMLoginModule required awsProfileName="<PROFILE_NAME>"; \
-    -d provectuslabs/kafka-ui:latest 
+    -d ghcr.io/kafbat/kafka-ui 
 ```
 
 #### Configuring by application.yaml

configuration/authentication/oauth2.md

@@ -86,7 +86,7 @@ auth:
         user-name-attribute: email
         custom-params:
           type: google
-          allowedDomain: provectus.com # for RBAC
+          allowedDomain: kafbat.io # for RBAC
 ```
 
 ### Azure
@@ -116,7 +116,7 @@ auth:
 
 Example of callback URL for github OAuth app settings:
 
-`https://www.kafka-ui.provectus.io/login/oauth2/code/github`
+`https://kafbat.io/login/oauth2/code/github`
 
 For the self-hosted installation find the properties a little bit below.
 

configuration/authentication/sasl_scram.md

@@ -24,7 +24,7 @@ docker run -p 8080:8080 \
     -e KAFKA_CLUSTERS_0_PROPERTIES_SECURITY_PROTOCOL=SASL_SSL \
     -e KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM=SCRAM-SHA-512 \     
     -e KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG=org.apache.kafka.common.security.scram.ScramLoginModule required username="<KAFKA_USERNAME>" password="<KAFKA_PASSWORD>"; \
-    -d provectuslabs/kafka-ui:latest 
+    -d ghcr.io/kafbat/kafka-ui 
 ```
 
 #### Running From Docker-compose file
@@ -34,9 +34,9 @@ docker run -p 8080:8080 \
 version: '3.4'
 services:
 
-  kafka-ui:
-    image: provectuslabs/kafka-ui
-    container_name: kafka-ui
+  kafbat-ui:
+    image: ghcr.io/kafbat/kafka-ui
+    container_name: kafbat-ui
     ports:
       - "888:8080"
     restart: always

configuration/authentication/sso-guide.md

@@ -30,7 +30,7 @@ This is a main parameters required for enabling SSO
 
 ### Step 3
 
-To launch UI for Apache Kafka with enabled TLS and SSO run following:
+To launch Kafbat UI with enabled TLS and SSO run following:
 
 ```bash
 docker run -p 8080:8080 -v `pwd`/cert:/opt/cert -e AUTH_TYPE=LOGIN_FORM \
@@ -46,7 +46,7 @@ docker run -p 8080:8080 -v `pwd`/cert:/opt/cert -e AUTH_TYPE=LOGIN_FORM \
   -e SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_AUTH0_SCOPE=openid \
   -e TRUST_STORE=/opt/cert/ui-for-apache-kafka.p12 \
   -e TRUST_STORE_PASSWORD=123456 \
-provectuslabs/kafka-ui:latest
+ghcr.io/kafbat/kafka-ui
 ```
 
 In the case with trusted CA-signed SSL certificate and SSL termination somewhere outside of application we can pass only SSO related environment variables:
@@ -57,12 +57,12 @@ docker run -p 8080:8080 -v `pwd`/cert:/opt/cert -e AUTH_TYPE=OAUTH2 \
   -e SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_AUTH0_CLIENTSECRET=YXfRjmodifiedTujnkVr7zuW9ECCAK4TcnCio-i \
   -e SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_AUTH0_ISSUER_URI=https://dev-a63ggcut.auth0.com/ \
   -e SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_AUTH0_SCOPE=openid \
-provectuslabs/kafka-ui:latest
+ghcr.io/kafbat/kafka-ui
 ```
 
 ### Step 4 (Load Balancer HTTP) (optional)
 
-If you're using load balancer/proxy and use HTTP between the proxy and the app, you might want to set `server_forward-headers-strategy` to `native` as well (`SERVER_FORWARDHEADERSSTRATEGY=native`), for more info refer to [this issue](https://github.com/provectus/kafka-ui/issues/1017).
+If you're using load balancer/proxy and use HTTP between the proxy and the app, you might want to set `server_forward-headers-strategy` to `native` as well (`SERVER_FORWARDHEADERSSTRATEGY=native`), for more info refer to [this issue](https://github.com/kafbat/kafka-ui/issues/1017).
 
 ### Step 5 (Azure) (optional)
 
@@ -82,7 +82,7 @@ docker run -p 8080:8080 \
         -e AUTH_OAUTH2_CLIENT_AZURE_PROVIDER="azure" \
         -e AUTH_OAUTH2_CLIENT_AZURE_ISSUERURI="https://login.microsoftonline.com/{tenant_id}/v2.0" \
         -e AUTH_OAUTH2_CLIENT_AZURE_JWKSETURI="https://login.microsoftonline.com/{tenant_id}/discovery/v2.0/keys" \
-        -d provectuslabs/kafka-ui:latest"
+        -d ghcr.io/kafbat/kafka-ui"
 ```
 
 Note that scope is created by default when Application registration is done in Azure portal. You'll need to update application registration manifest to include `"accessTokenAcceptedVersion": 2`

configuration/compose-examples.md

@@ -4,4 +4,4 @@ description: A list of ready-to-go docker compose files for various setup scenar
 
 # Compose examples
 
-[https://github.com/provectus/kafka-ui/blob/master/documentation/compose/DOCKER\_COMPOSE.md](https://github.com/provectus/kafka-ui/blob/master/documentation/compose/DOCKER\_COMPOSE.md)
+[https://github.com/kafbat/kafka-ui/blob/main/documentation/compose/DOCKER\_COMPOSE.md](https://github.com/kafbat/kafka-ui/blob/main/documentation/compose/DOCKER\_COMPOSE.md)

configuration/configuration-file.md

@@ -16,15 +16,15 @@ Rather than writing your config from a scratch, it would be more convenient to u
 
 #### Providing a config path for the app instance:
 
-**Docker**: `docker run -it -p 8080:8080 -e spring.config.additional-location=/tmp/config.yml -v /tmp/kui/config.yml:/tmp/config.yml provectuslabs/kafka-ui`
+**Docker**: `docker run -it -p 8080:8080 -e spring.config.additional-location=/tmp/config.yml -v /tmp/kui/config.yml:/tmp/config.yml ghcr.io/kafbat/kafka-ui`
 
 **Docker compose**: 
 
 ```
 services:
-  kafka-ui:
-    container_name: kafka-ui
-    image: provectuslabs/kafka-ui:latest
+  kafbat-ui:
+    container_name: kafbat-ui
+    image: ghcr.io/kafbat/kafka-ui
     environment:
       KAFKA_CLUSTERS_0_NAME: local
       # other properties, omitted

configuration/configuration-wizard.md

@@ -4,17 +4,17 @@
 
 ![](../.gitbook/assets/image.png)![](<../.gitbook/assets/image (1).png>)
 
-By default, kafka-ui does not allow to change of its configuration in runtime. When the application is started it reads configuration from system env, config files (ex. application.yaml), and JVM arguments (set by `-D`). Once the configuration was read it was treated as immutable and won't be refreshed even if the config source (ex. file) was changed.
+By default, kafbat-ui does not allow to change of its configuration in runtime. When the application is started it reads configuration from system env, config files (ex. application.yaml), and JVM arguments (set by `-D`). Once the configuration was read it was treated as immutable and won't be refreshed even if the config source (ex. file) was changed.
 
 Since version 0.6 we added an ability to change cluster configs in runtime. This option is disabled by default and should be implicitly enabled. To enable it, you should set `DYNAMIC_CONFIG_ENABLED` env property to `true` or add `dynamic.config.enabled: true` property to your yaml config file.
 
 Sample docker compose configuration:
 
 ```
 services:
-  kafka-ui:
-    container_name: kafka-ui
-    image: provectuslabs/kafka-ui:latest
+  kafbat-ui:
+    container_name: kafbat-ui
+    image: ghcr.io/kafbat/kafka-ui
     ports:
       - 8080:8080
     depends_on:
@@ -35,11 +35,11 @@ When the dynamic config feature is enabled you will see additional buttons that
 
 #### Dynamic config files
 
-Kafka-ui is a stateless application by its nature, so, when you edit configuration during runtime, it will store configuration additions on the container's filesystem (in `dynamic_config.yaml` file). Dynamic config file will be overridden on each configuration submission.
+Kafbat-UI is a stateless application by its nature, so, when you edit configuration during runtime, it will store configuration additions on the container's filesystem (in `dynamic_config.yaml` file). Dynamic config file will be overridden on each configuration submission.
 
 During the configuration process, you can also upload configuration-related files (like truststore and keystores). They will be stored in `etc/kafkaui/uploads` a folder with a unique timestamp suffix to prevent name collision. In the wizard, you can also use files that were mounted to the container's filesystem, without uploading them directly.
 
-**Note**, that if the container is recreated, your edited (and uploaded) files won't be present and the app will be started with static configuration only. If you want to be able to keep the configuration created by wizard, you have to mount/copy the same files into newly created kafka-ui containers (whole `/etc/kafkaui/` folder, by default).
+**Note**, that if the container is recreated, your edited (and uploaded) files won't be present and the app will be started with static configuration only. If you want to be able to keep the configuration created by wizard, you have to mount/copy the same files into newly created kafbat-ui containers (whole `/etc/kafkaui/` folder, by default).
 
 Properties, specified where dynamic config files will be persisted:
 
@@ -50,4 +50,4 @@ Properties, specified where dynamic config files will be persisted:
 
 #### Implementation notes:
 
-Currently, the new configuration submission leads to a full application restart. So, if your kafka-ui app is starting slow (not a usual case, but may happen when you have a slow connection to kafka clusters) you may notice UI inaccessibility during restart time.
+Currently, the new configuration submission leads to a full application restart. So, if your kafbat-ui app is starting slow (not a usual case, but may happen when you have a slow connection to kafka clusters) you may notice UI inaccessibility during restart time.