commit | 9d7947d09689c8056320a76157ca3e6c6933ac46 | [log] [tgz] |
---|---|---|
author | Claude Warren <claude@apache.org> | Tue Mar 28 09:05:48 2023 +0100 |
committer | GitHub <noreply@github.com> | Tue Mar 28 09:05:48 2023 +0100 |
tree | d1717a2adb76857ca936e2467b4466e08c43ff32 | |
parent | c298b54243927d32ec67431722a140e003ad06ce [diff] |
Update README.md Fixed formatting of publishing steps
This repo is a temporary solution to publishing the Apache Pekko website. The artifacts are built in the Pekko modules. A Pekko committer can use the commands below to copy these artifacts and commit them.
Anyone looking to help improve our docs should look at the Git repos (eg incubator-pekko) for the modules. Typically, sbt docs/paradoxBrowse
will build the docs and load them into your browser when they are ready.
Publishing the Apache Pekko web site requires:
incubator-pekko
repo, runsbt unidoc docs/paradox # next line requires Java 11 or above sbt -Dpekko.genjavadoc.enabled=true Javaunidoc/doc
incubator-pekko-site
and runmkdir -p content/docs/pekko/current/ mkdir -p content/api/pekko/current/ mkdir -p content/japi/pekko/current/
incubator-pekko-site
and runcp -r <path>/incubator-pekko/docs/target/paradox/site/main/ content/docs/pekko/current/ cp -r <path>/incubator-pekko/target/scala-2.13/unidoc/ content/api/pekko/current/ cp -r <path>/incubator-pekko/target/javaunidoc/ content/japi/pekko/current/
incubator-pekko-http
repo, runsbt unidoc docs/paradox # next line requires Java 11 or above sbt -Dpekko.genjavadoc.enabled=true Javaunidoc/doc
incubator-pekko-site
and runmkdir -p content/docs/pekko-http/current/ mkdir -p content/api/pekko-http/current/ mkdir -p content/japi/pekko-http/current/
incubator-pekko-site
and runcp -r <path>/incubator-pekko-http/docs/target/paradox/site/main/ content/docs/pekko-http/current/ cp -r <path>/incubator-pekko-http/target/scala-2.13/unidoc/ content/api/pekko-http/current/ cp -r <path>/incubator-pekko-http/target/javaunidoc/ content/japi/pekko-http/current/
git add
on the affected files and git commit
.git push
.git rebase asf-staging
followed by git push
.This approach is based on the support for publishing sites provided by INFRA team. See .asf.yaml features documentation.
This approach is based on the Apache Flume process, see How to Release - Update the Web Site.