You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/01/09 19:41:35 UTC
[jira] [Commented] (REEF-4) Create a REEF website on Apache
infrastructure
[ https://issues.apache.org/jira/browse/REEF-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271674#comment-14271674 ]
Markus Weimer commented on REEF-4:
----------------------------------
This is done, isn't it?
> Create a REEF website on Apache infrastructure
> ----------------------------------------------
>
> Key: REEF-4
> URL: https://issues.apache.org/jira/browse/REEF-4
> Project: REEF
> Issue Type: Task
> Components: Website
> Reporter: Markus Weimer
>
> REEF has a web presence at http://www.reef-project.org That presence is built using WordPress and run on a Linux VM hosted on Microsoft Azure.
> As per [this guide|http://incubator.apache.org/guides/sites.html] we shall have a website on Apache Infrastructure. The guide also assumes that the website is static (e.g. not require PHP and MySQL like WordPress does).
> Hence, we have two options:
> # Figure out how to move WordPress onto Apache servers.
> # Drop WordPress and make a static website as per the instructions.
> The actual choice shall be left to the person doing the work, but I would favor the second option, as it lowers the long-term cost of maintaining the site: REEF would not be on the hook for installing security updates on the stack that runs WordPress.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)