- Sort Score
- Num 10 results
- Language All
Results 401 - 410 of 686 for emitting (0.05 seconds)
-
helm-releases/minio-3.1.0.tgz
will be displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 12 18:19:27 GMT 2021 - 14.3K bytes - Click Count (0) -
helm-releases/minio-3.1.1.tgz
will be displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Sep 13 16:43:10 GMT 2021 - 14.3K bytes - Click Count (0) -
helm-releases/minio-3.1.6.tgz
will be displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Sep 23 19:56:39 GMT 2021 - 14.5K bytes - Click Count (0) -
doc/godebug.md
It is also possible to set the default `GODEBUG` for a given program (discussed below). When preparing any change that is permitted by Go 1 compatibility but may nonetheless break some existing programs, we first engineer the change to keep as many existing programs working as possible. For the remaining programs, we define a new GODEBUG setting that allows individual programs to opt back in to the old behavior.
Created: Tue Dec 30 11:13:12 GMT 2025 - Last Modified: Wed Dec 03 00:18:09 GMT 2025 - 24.7K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/helper/CrawlingInfoHelper.java
* Also stores any accumulated information parameters and clears the info map. * * @param sessionId the session ID for the crawling information * @param create if true, creates a new crawling info regardless of existing records * @throws FessSystemException if unable to store the crawling session */ public synchronized void store(final String sessionId, final boolean create) {Created: Sat Dec 20 09:19:18 GMT 2025 - Last Modified: Thu Aug 07 03:06:29 GMT 2025 - 15.2K bytes - Click Count (0) -
cmd/admin-handlers-idp-config.go
func (a adminAPIHandlers) AddIdentityProviderCfg(w http.ResponseWriter, r *http.Request) { ctx := r.Context() addOrUpdateIDPHandler(ctx, w, r, false) } // UpdateIdentityProviderCfg: updates an existing IDP config for openid/ldap. // // POST <admin-prefix>/idp-cfg/openid/dex1 -> update named config `dex1` // // POST <admin-prefix>/idp-cfg/openid/_ -> update (default) named config `_`
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Feb 18 16:25:55 GMT 2025 - 12.7K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/app/web/api/admin/dataconfig/ApiAdminDataconfigAction.java
return null; }); return asJson(new ApiUpdateResponse().id(dataConfig.getId()).created(true).status(Status.OK).result()); } /** * Updates an existing data config setting. * * @param body the request body containing updated data config information * @return JSON response with result status */ // PUT /api/admin/dataconfig/settingCreated: Sat Dec 20 09:19:18 GMT 2025 - Last Modified: Thu Aug 07 03:06:29 GMT 2025 - 8.5K bytes - Click Count (0) -
src/main/java/jcifs/smb/SmbNamedPipe.java
* writes to, reads from, and closes the pipe in a single operation. * <li><code>TransactNamedPipe</code> A message-type pipe call that * writes to and reads from an existing pipe descriptor in one operation. * <li><code>CreateFile</code>, <code>ReadFile</code>, * <code>WriteFile</code>, and <code>CloseFile</code> A byte-type pipe can
Created: Sat Dec 20 13:44:44 GMT 2025 - Last Modified: Sat Aug 16 01:32:48 GMT 2025 - 6.2K bytes - Click Count (0) -
src/main/java/jcifs/internal/smb2/rdma/RdmaTransport.java
import jcifs.DfsReferralData; import jcifs.SmbSession; import jcifs.SmbTransport; import jcifs.smb.SmbException; import jcifs.smb.SmbTransportInternal; /** * RDMA-enabled SMB transport that wraps existing SMB transport * and adds RDMA capabilities for direct memory access operations. */ public class RdmaTransport implements SmbTransportInternal {Created: Sat Dec 20 13:44:44 GMT 2025 - Last Modified: Sat Aug 23 05:11:12 GMT 2025 - 8.9K bytes - Click Count (0) -
helm-releases/minio-3.6.0.tgz
will be displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Mar 13 22:44:21 GMT 2022 - 17.9K bytes - Click Count (0)