[
https://issues.apache.org/jira/browse/KAFKA-13882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697160#comment-17697160
]
ASF GitHub Bot commented on KAFKA-13882:
----------------------------------------
qingwei91 commented on PR #410:
URL: https://github.com/apache/kafka-site/pull/410#issuecomment-1457134844
Hi @mimaison , another way I can think of is to avoid using .htaccess in the
docker, and inject all config required in httpd.conf instead.
https://github.com/apache/kafka-site/pull/410/commits/4d7397f17d10e64d3fadf4e8722e492bdf131fba
I am not sure if this is better since we now have duplicated config
I also wonder if .htaccess is actually used in the actual deployment, as it
requires modifying httpd.conf
> Dockerfile for previewing website
> ---------------------------------
>
> Key: KAFKA-13882
> URL: https://issues.apache.org/jira/browse/KAFKA-13882
> Project: Kafka
> Issue Type: Task
> Components: docs, website
> Reporter: Tom Bentley
> Assignee: Lim Qing Wei
> Priority: Trivial
> Labels: newbie
>
> Previewing changes to the website/documentation is rather difficult because
> you either have to [hack with the
> HTML|https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes#ContributingWebsiteDocumentationChanges-KafkaWebsiteRepository]
> or [install
> httpd|https://cwiki.apache.org/confluence/display/KAFKA/Setup+Kafka+Website+on+Local+Apache+Server].
> This is a barrier to contribution.
> Having a Dockerfile for previewing the Kafka website (i.e. with httpd
> properly set up) would make it easier for people to contribute website/docs
> changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
