use OC_ env prefix

Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>

docs/ocis/development/beta-testplan.md

@@ -32,7 +32,7 @@ to access oCIS remotely please refer to the [Basic Remote Setup]({{< ref "../dep
 
 ## additional tips
 - to allow basic auth (e.g. to easily access oCIS using curl commands) you have to set `PROXY_ENABLE_BASIC_AUTH=true` environment variable
-- if you cannot use real SSL Certificates set `OCIS_INSECURE=true` as environment variable
+- if you cannot use real SSL Certificates set `OC_INSECURE=true` as environment variable
 
 
 # Testplan

docs/ocis/development/debugging.md

@@ -21,7 +21,7 @@ For debugging there are two workflows that work well, depending on your preferen
 
 #### Use the debug binary and attach to the process as needed
 
-Run the debug binary with `OCIS_LOG_LEVEL=debug bin/ocis-debug server` and then find the service you want to debug using:
+Run the debug binary with `OC_LOG_LEVEL=debug bin/ocis-debug server` and then find the service you want to debug using:
 
 ```console
 # ps ax | grep ocis
@@ -145,7 +145,7 @@ make debug-docker
 ```
 2. Change the tag label:
 ```bash
-export OCIS_DOCKER_TAG=debug
+export OC_DOCKER_TAG=debug
 ```
 3. Run docker compose
 Building the docker compose command depends on what you want to debug, for example `ocis` and `collaboration` with the `collabora` supports.

docs/ocis/development/testing.md

@@ -96,8 +96,8 @@ To run the tests that require an antivirus service (tests tagged with `@antiviru
 
 ```bash
 START_ANTIVIRUS=true \
-OCIS_ASYNC_UPLOADS=true \
-OCIS_ADD_RUN_SERVICES=antivirus \
+OC_ASYNC_UPLOADS=true \
+OC_ADD_RUN_SERVICES=antivirus \
 POSTPROCESSING_STEPS=virusscan \
 BEHAT_FEATURE='tests/acceptance/features/apiAntivirus/antivirus.feature' \
 make -C tests/acceptance/docker test-ocis-feature-ocis-storage
@@ -167,10 +167,10 @@ The test suites transferred from ownCloud core have `coreApi` prefixed
 
 ### oCIS Image to Be Tested (Skip Local Image Build)
 
-By default, the tests will be run against the docker image built from your current working state of the oCIS repository. For some purposes it might also be handy to use an oCIS image from Docker Hub. Therefore, you can provide the optional flag `OCIS_IMAGE_TAG=...` which must contain an available docker tag of the [owncloud/ocis registry on Docker Hub](https://hub.docker.com/r/owncloud/ocis) (e.g. 'latest').
+By default, the tests will be run against the docker image built from your current working state of the oCIS repository. For some purposes it might also be handy to use an oCIS image from Docker Hub. Therefore, you can provide the optional flag `OC_IMAGE_TAG=...` which must contain an available docker tag of the [owncloud/ocis registry on Docker Hub](https://hub.docker.com/r/owncloud/ocis) (e.g. 'latest').
 
 ```bash
-OCIS_IMAGE_TAG=latest \
+OC_IMAGE_TAG=latest \
 make -C tests/acceptance/docker localApiTests-apiGraph-ocis
 ```
 
@@ -206,7 +206,7 @@ To start oCIS:
 IDM_ADMIN_PASSWORD=admin \
 ocis/bin/ocis init --insecure true
 
-OCIS_INSECURE=true PROXY_ENABLE_BASIC_AUTH=true \
+OC_INSECURE=true PROXY_ENABLE_BASIC_AUTH=true \
 ocis/bin/ocis server
 ```
 
@@ -319,7 +319,7 @@ PROXY_ENABLE_BASIC_AUTH=true \
 ### Run the Tests
 
 ```bash
-OCIS_WRAPPER_URL=http://localhost:5200 \
+OC_WRAPPER_URL=http://localhost:5200 \
 TEST_SERVER_URL="https://localhost:9200" \
 BEHAT_FEATURE=tests/acceptance/features/apiAsyncUpload/delayPostprocessing.feature \
 make test-acceptance-api
@@ -356,7 +356,7 @@ ocis/bin/ocis init --insecure true
 
 # run oCIS
 PROXY_ENABLE_BASIC_AUTH=true \
-OCIS_ADD_RUN_SERVICES=notifications \
+OC_ADD_RUN_SERVICES=notifications \
 NOTIFICATIONS_SMTP_HOST=localhost \
 NOTIFICATIONS_SMTP_PORT=2500 \
 NOTIFICATIONS_SMTP_INSECURE=true \
@@ -399,7 +399,7 @@ ocis/bin/ocis init --insecure true
 
 # run oCIS
 PROXY_ENABLE_BASIC_AUTH=true \
-OCIS_INSECURE=true \
+OC_INSECURE=true \
 SEARCH_EXTRACTOR_TYPE=tika \
 SEARCH_EXTRACTOR_TIKA_TIKA_URL=http://localhost:9998 \
 SEARCH_EXTRACTOR_CS3SOURCE_INSECURE=true \
@@ -481,8 +481,8 @@ PROXY_ENABLE_BASIC_AUTH=true \
 ANTIVIRUS_SCANNER_TYPE="clamav" \
 ANTIVIRUS_CLAMAV_SOCKET="tcp://host.docker.internal:3310" \
 POSTPROCESSING_STEPS="virusscan" \
-OCIS_ASYNC_UPLOADS=true \
-OCIS_ADD_RUN_SERVICES="antivirus"
+OC_ASYNC_UPLOADS=true \
+OC_ADD_RUN_SERVICES="antivirus"
 ocis/bin/ocis server
 ```
 
@@ -516,11 +516,11 @@ IDM_ADMIN_PASSWORD=admin \
 ocis/bin/ocis init --insecure true
 
 # run oCIS
-OCIS_URL="https://localhost:9200" \
+OC_URL="https://localhost:9200" \
 PROXY_ENABLE_BASIC_AUTH=true \
-OCIS_ENABLE_OCM=true \
+OC_ENABLE_OCM=true \
 OCM_OCM_PROVIDER_AUTHORIZER_PROVIDERS_FILE="tests/config/local/providers.json" \
-OCIS_ADD_RUN_SERVICES="ocm" \
+OC_ADD_RUN_SERVICES="ocm" \
 OCM_OCM_INVITE_MANAGER_INSECURE=true \
 OCM_OCM_SHARE_PROVIDER_INSECURE=true \
 OCM_OCM_STORAGE_PROVIDER_INSECURE=true \
@@ -552,8 +552,8 @@ The second oCIS instance should be available at: https://localhost:10200/
 
 {{< hint info >}}
 To enable ocm in the web interface, you need to set the following envs:
-`OCIS_ENABLE_OCM="true"`
-`OCIS_ADD_RUN_SERVICES="ocm"`
+`OC_ENABLE_OCM="true"`
+`OC_ADD_RUN_SERVICES="ocm"`
 {{< /hint>}}
 
 #### Run the Acceptance Test

docs/ocis/development/tracing.md

@@ -37,13 +37,13 @@ to get started:
       ```
    2. Enabling and configuring tracing on oCIS itself will forward the configuration to all services:
       ```console
-      OCIS_TRACING_ENABLED=true \
-      OCIS_TRACING_ENDPOINT=localhost:6831 \
-      OCIS_TRACING_COLLECTOR=http://localhost:14268/api/traces \
+      OC_TRACING_ENABLED=true \
+      OC_TRACING_ENDPOINT=localhost:6831 \
+      OC_TRACING_COLLECTOR=http://localhost:14268/api/traces \
       ./bin/ocis server
       ```
       If you want to set individual tracing configuration for each service, make sure to set
-      `OCIS_TRACING_ENABLED=false`.
+      `OC_TRACING_ENABLED=false`.
 3. Make the actual request that you want to trace.
 4. Open up the [Jaeger UI](http://localhost:16686) to analyze request traces.