How publishing works in neos?

Neos / Flow FAQ
#1

I am a newbie to neos although I have many experiences in CMS before. I find there is no such Publishing tool clearly defined to publish static content easily to multiple remote destinations which is quite common practice at Enterprise. Besides Varnish approach which is a caching approach, I do want to know how to simply publish the static html, css, js to a remote hosting account like GoDaddy.com? Or maybe I need a 2nd Neos instance to be deployed remotely to act as an “Apache” equivalent? Or can I just use “Publish” to publish static content ONLY via FTP to another server?

Thanks.

SW

#2

Hi,

Neos is not (currently) and static sitebuilder.

You can check: https://github.com/SimplyAdmire/SimplyAdmire.Neos.PageCache (but it’s still a caching approach).

It’s should be possible to use a command controller to build a static version of a site, and publish it somewhere. My vision for this kind of package:

  1. Neos installation with cloud storage configured (S3, Rackspace, …)
  2. Create a CommandController to browse the site and save a static version of the site
  3. Publish / Deploy to somewhere
#3

Thx. If I’d like to setup this on AWS, I should have one EC2 using S3 storage then using CloudFront as CDN? If I need host this in a corp LAN, I will face the security issue if I put neos in a DMZ. So, I assume I should use Varnish in DMZ to cache the content? Any bible regarding how to setup a Varnish with Neos?

#4

Hi Steven

Not sure what exactly you mean here, setting up the static deployment on AWS or? If you do that there’s not really anything Neos specific regarding Varnish I’d say.

However if you mean setting up Neos normally on AWS using S3 and CloudFront + Varnish then these packages should help.

https://github.com/Flownative/flow-aws-s3 (https://packagist.org/packages/flownative/aws-s3)
https://github.com/mocdk/MOC.Varnish (https://packagist.org/packages/moc/varnish)

#5

If you wont to go to the static website so publishing only HTML + CSS, first you have to code the support for Neos to export the site as a static dump, should be doable.

By using the flow-aws-s3, your resource are published to S3 from your main neos server.

For hosting of the static website, service like https://www.netlify.com/ really rock, simple to use pretty powerful.