- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for initial (0.2 sec)
-
doc/README.md
## For the release team At the start of a release development cycle, the contents of `next` should be deleted and replaced with those of `initial`. From the repo root: > cd doc > rm -r next/* > cp -r initial/* next Then edit `next/1-intro.md` to refer to the next version. To prepare the release notes for a release, run `golang.org/x/build/cmd/relnote generate`.
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Apr 26 21:24:36 GMT 2024 - 1.9K bytes - Viewed (0) -
internal/grid/README.md
## Streaming Requests Streams consists of an initial request with payload and allows for full two-way communication between the client and server. The handler function has this signature. Sample handler: ```go handler := func(ctx context.Context, payload []byte, in <-chan []byte, out chan<- []byte) *RemoteErr { fmt.Println("Got request with initial payload", p, "from", GetCaller(ctx context.Context))
Plain Text - Registered: Sun Apr 21 19:28:08 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 9.4K bytes - Viewed (0) -
docs/kms/README.md
### 1. Fetch the root identity As the initial step, fetch the private key and certificate of the root identity: ```sh curl -sSL --tlsv1.2 \ -O 'https://raw.githubusercontent.com/minio/kes/master/root.key' \
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/bucket/replication/README.md
namespace. In the rare event that target DR site is entirely lost and previously replicated objects to the DR cluster need to be re-replicated, `mc replicate resync start alias/bucket --remote-bucket <arn>` can be used to initiate a reset. This would initiate a re-sync between the two clusters by walking the bucket namespace and replicating eligible objects that satisfy the existing objects replication rule specified in the replication config. The status of the resync operation can be viewed...
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Tue Jan 24 23:46:33 GMT 2023 - 18.2K bytes - Viewed (0) -
docs/site-replication/README.md
- Bucket notification configuration - Bucket lifecycle (ILM) configuration ## Pre-requisites - Initially, only **one** of the sites added for replication may have data. After site-replication is successfully configured, this data is replicated to the other (initially empty) sites. Subsequently, objects may be written to any of the sites, and they will be replicated to all other sites.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Mon Feb 26 21:30:28 GMT 2024 - 3.4K bytes - Viewed (0)