393c81d207
* WIP monolith naming restructure * rebuild homepage * updated broken home links * stabs in the dark * fixed duplicate-oss shortcode * move clustered and cloud-dedicated * clean-up serverless cruft * add distributed product redirects * standarize productPathData * switch back to findRE for productPathData * remove debugging code * move cloud dedicated content * new product dropdown * Jstirnaman/influxdb3 restructure (#5743) * LDAPS and LDAP Client Certificate Docs Add documentation via LDAP sample configuration for LDAPS and LDAP client certificates. These are new features in the yet-to-be released Enterprise 1.11.7 * Update bucket-schema.md ndjson.org goes to some sort of sports betting site. https://jsonlines.org/ is probably a better site. * fix(partitioning): improve clarity and consistency in partitioning, apply suggestions from @reidkaufmann * update shared links to use ambiguous version * WIP monolith docs * template updates for v3 and pro * move clustered and cloud-dedicated * switch back to findRE for productPathData * move cloud dedicated content * chore(influxdb3): port cloud-dedicated URLs from recent commit * chore(influxdb3/clustered): fix and update links * removed merge cruft --------- Co-authored-by: Geoffrey Wossum <gwossum@influxdata.com> Co-authored-by: Daniel Lo <wilburlo@gmail.com> Co-authored-by: Scott Anderson <scott@influxdata.com> --------- Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com> Co-authored-by: Geoffrey Wossum <gwossum@influxdata.com> Co-authored-by: Daniel Lo <wilburlo@gmail.com> |
||
---|---|---|
.. | ||
README.md | ||
ci-install-s3deploy.sh | ||
docs-website.yml | ||
edge.js |
README.md
Deploying the InfluxData Docs
Use the following command to deploy a CloudFormation stack using the template in this directory.
aws cloudformation deploy \
--template-file deploy/docs-website.yml \
--stack-name="${STACK_NAME}" \
--capabilities CAPABILITY_IAM \
--parameter-overrides \
AcmCertificateArn="${ACM_ARN}" \
DomainName="${DOMAIN_NAME}"
To only display actions that will be taken, in the --no-execute-changeset
option.
Without this option, the command executes and deploys the changeset.