```yaml
    volumeMounts:
        - name: secret-volume
          mountPath: /<user-running-minio>/.minio/certs
```

Here the name of `volumeMount` should match the name of `volume` created previously. Also `mountPath` must be set to the path of
the MinIO server's config sub-directory that is used to store certificates. By default, the location is
`/<user-running-minio>/.minio/certs`.

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Installation Level.

```plaintext
/home/user/code/awesome-project/.venv/bin/python
```

và sử dụng chương trình đó.

////

//// tab | Windows

```plaintext
C:\Users\user\code\awesome-project\.venv\Scripts;C:\Windows\System32
```

Nghĩa là hệ thống sẽ bắt đầu tìm kiếm chương trình trong:

```plaintext
C:\Users\user\code\awesome-project\.venv\Scripts
```

    return user_id

# Модель Pydantic
class User(BaseModel):
    id: int
    name: str
    joined: date
```

Приклад використання цієї моделі:

```Python
my_user: User = User(id=3, name="John Doe", joined="2018-07-19")

second_user_data = {
    "id": 4,
    "name": "Mary",
    "joined": "2018-11-30",
}

my_second_user: User = User(**second_user_data)
```

/// info | Інформація

import org.apache.maven.api.Service;
import org.apache.maven.api.Session;
import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Nonnull;

/**
 * Builds the effective toolchains from a user toolchains file and/or an installation toolchains file.
 *
 * @since 4.0.0
 */
@Experimental
public interface ToolchainsBuilder extends Service {

    /**

            Specifies that this parameter can be configured directly by the user (as in the case of POM-specified
            configuration). This is useful when you want to force the user to use common POM elements rather than
            plugin configurations, as in the case where you want to use the artifact's final name as a parameter. In
            this case, you want the user to modify {@code <build><finalName/></build>} rather

                }
            }
        }
    }

    /**
     * Creates search conditions for user info queries based on pager criteria.
     *
     * @param pager The search log pager containing filter criteria
     * @param cb The user info condition bean to configure
     */
    private void createUserInfoCondition(final SearchLogPager pager, final UserInfoCB cb) {

    assertThat(response.request.header("User-Agent")).isNotNull()
    assertThat(response.request.header("User-Agent")).isEqualTo("user request")
    assertThat(response.networkResponse!!.request.header("User-Agent")).isEqualTo(
      "intercepted request",
    )
  }

  @Test
  fun applicationInterceptorThrowsRuntimeExceptionAsynchronous() {

     * @param domain The domain in which the username exists.
     * @param user The username.
     * @param password The user's password.
     * @param challenge The server challenge.
     * @param clientChallenge The client challenge (nonce).
     * @return the LMv2 response bytes
     */
    public static byte[] getLMv2Response(final String domain, final String user, final String password, final byte[] challenge,

    }

    // Test with different from names
    public void test_differentFromNames() {
        String[] fromNames = { "Administrator", "Support Team", "No Reply", "Test User" };

        for (String name : fromNames) {
            ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {
                private static final long serialVersionUID = 1L;

                @Override