Object Lambda functions to transform objects via a webhook. Expand and
refine the developer docs from
c4d71bc1a5/docs/lambda/README.md
into a new page in the user documentation.
Staged
http://192.241.195.202:9000/staging/DOCS-754/linux/html/developers/transforms-with-object-lambda.html
Notes for reviewers:
In addition to the items noted in inline comments, some general things
to confirm:
* Accurate usage/terminology? Is this how we talk about the relevant
topics?
* Any technical points that need more/more correct detail?
* What would someone need to know to go from trying this dev example to
having a real function in their production environment?
[x] Add new docs page in Developers
[x] Add envars to envar list
Fixes https://github.com/minio/docs/issues/754
- Proxying MinIO based on subdomains of a single hostname
- Proxying MinIO based on subpath of a single hostname
- Including the websocket upload logic
Updates `mc` reference docs for several releases of the MinIO Client.
- Adds missing flags to `mc admin trace`
- Updates `disk` -> `drive` throughout the docs, but not in all cases.
- Adds `--airgap flag` to `mc support profile` and `mc support perf`
commands.
- Updates the flags for `mc ilm add` command
- Adds `mc license unregister` command.
Closes#571Closes#614Closes#627Closes#633
This is the initial work for what should be a git-managed set of nginx
configs we can include into the Nginx Docs server.
The idea here is we manage redirects in git, and either chron-copy them
to a location we can include via the sites-available/<file>, *or* we
just include them from the git path (if nginx tolerates that)
I can't really _test_ these right now since they are using live URLs. if
we move forward with the soft-launch, we'll have a few opportunities to
maybe test a subset of these URLs and see what happens.
Please let me know if there is anything *obviously* wrong here.
ToDo: The Legacy Docs redirects
