Search Options

Results per page
Sort
Preferred Languages
Advance

Results 451 - 460 of 794 for friends (0.07 sec)

  1. licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Wed Jul 26 01:07:39 UTC 2023
    - 11.1K bytes
    - Viewed (0)
  2. licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Wed Jul 26 01:07:39 UTC 2023
    - 11.1K bytes
    - Viewed (0)
  3. licenses/github.com/AdaLogics/go-fuzz-headers/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Jun 28 18:00:28 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  4. licenses/github.com/go-jose/go-jose/v3/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Tue Jan 10 18:24:50 UTC 2023
    - 11.1K bytes
    - Viewed (0)
  5. licenses/github.com/go-jose/go-jose/v4/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Apr 08 17:05:56 UTC 2024
    - 11.1K bytes
    - Viewed (0)
  6. licenses/github.com/go-openapi/jsonpointer/LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  7. LICENSE

       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Sun Nov 10 03:50:12 UTC 2024
    - Last Modified: Mon Jan 11 04:26:17 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  8. docs/en/docs/environment-variables.md

    For example, when you type `python` in the terminal, the operating system looks for a program called `python` in the **first directory** in that list.
    
    If it finds it, then it will **use it**. Otherwise it keeps looking in the **other directories**.
    
    ### Installing Python and Updating the `PATH`
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Sep 08 20:36:53 UTC 2024
    - 7.9K bytes
    - Viewed (0)
  9. helm-releases/minio-4.0.15.tgz

    use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Sep 21 11:07:01 UTC 2022
    - 20K bytes
    - Viewed (0)
  10. helm-releases/minio-3.4.2.tgz

    use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Dec 21 02:58:25 UTC 2021
    - 15.2K bytes
    - Viewed (0)
Back to top