incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-706) Clerezza site deployment not working
Date Wed, 20 Jun 2012 08:00:46 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397343#comment-13397343
] 

Reto Bachmann-Gmür commented on CLEREZZA-706:
---------------------------------------------

I'm guilty. replacing platform.content.fsadaptor with the released version make things fast
again. My changes to the fsadaptor for CLEREZZA-705 should only affect perfomance when an
immediate change folder is registered. Actually one is registered: the one of the clerezza-site
project. 
                
> Clerezza site deployment not working
> ------------------------------------
>
>                 Key: CLEREZZA-706
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-706
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Daniel Spicar
>            Assignee: Daniel Spicar
>         Attachments: zz-706-wireshark.pcap
>
>
> There are some issues in deploy.sh:
> - The script tries to connect to people.apache.org via SSH but does not specify the SSH
user. Probabaly the system user name is used but that may be wrong.
> - The script tries to deploy the site to  '/www/incubator.apache.org/clerezza' but the
correct location is '/www/incubator.apache.org/content/clerezza'
> Issues probably related to offline site generator:
> - The site<id>.zip contains the old version of the page as *.html file (e.g. index.html)
and the new version of the page as *.xhtml file (e.g. index.xhtml). By default the apache
webserver configuration will use the index.html file and thus ignore changes. (not sure if
this happens under all circumstances but it happened when I tried to update the website)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message