I'm facing a 403 forbidden issue for the Site Bucket access.
I'm not able to now if I made an error or if an aws update constraints dodgercms usage on AWS... Is it still usable on AWS S3?

How do you create and use other layouts?

I see "layouts" in the manager menu and in the source, but have tried creating another file next to entry.html, but have not figured out how to choose which layout to use when creating a new page (entry).

I get this message: Access Denied. Please make sure the user attached to the access key has access to data.site.com.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1427944232000",
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket",
                "s3:GetObject",
                "s3:DeleteObject",
                "s3:PutObject",
                "s3:GetBucketWebsite",
                "s3:PutBucketWebsite",
                "s3:DeleteBucketWebsite",
                "s3:GetBucketLogging",
                "s3:GetBucketVersioning",
                "s3:GetBucketLocation"
            ],
            "Resource": [
                "arn:aws:s3:::data.site.com",
                "arn:aws:s3:::data.site.com/*",
                "arn:aws:s3:::assets.site.com",
                "arn:aws:s3:::assets.site.com/*",
                "arn:aws:s3:::www.site.com",
                "arn:aws:s3:::www.site.com/*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": "sts:GetFederationToken",
            "Resource": "*"
        }
    ]
}

/*! dodgercms 0.0.2 2016-08-25 */

function(waterfallCb) { console.log("newdata in entry: " + newdata); var context = { newdata: newdata }, entry = dodgercms.templates["entry.html"], html = entry(context); waterfallCb(null, html)

It seems the menu system is totally dynamic which means that any bot wishing to index the site needs Javascript... Googlebot by default does not have Javascript enabled, Google has bots that can index Javascript but not all of its bots do so. So there needs to be a static way to allow the site to be indexed. Either we need a sitemap or we need to do something about the menu system and generate some static html for it... Thoughts?

Does the website/app need to be recompiled every time an entry gets added?

I think I followed all the steps but I just get an empty black space where the menu should be. Also, when I look at the site bucket there's no .dodgercms/data.json which according to the docs should be there.

The generated data json is incorrectly marking folders without an index file as having one. This is causing the menu to create links to folders which will produce a 404 since there is no index.html file present.

Getting the following error:

manager.project.com/s3-website-us-west-1.amazonaws.com says:

Access Denied. Please make sure the user attached to the access key has access to assets.project.com.

I've found a similar issue (#3) but the solution didn't resolve it for me.

Here are the steps that I took:

Setup data.project.com

Created data.project.com S3 bucket:

aws s3api create-bucket --bucket data.project.com --region us-west-1 --create-bucket-configuration LocationConstraint=us-west-1

Create data-cors.json:

{
  "CORSRules": [
    {
      "AllowedOrigins": ["*"],
      "AllowedHeaders": ["*"],
      "AllowedMethods": ["HEAD", "GET", "PUT", "POST", "DELETE"],
      "ExposeHeaders": ["ETag", "x-amz-meta-title", "x-amz-meta-label"]
    }
  ]
}

Edited data.project.com CORS:

aws s3api put-bucket-cors --bucket data.project.com --cors-configuration file://~/data-cors.json

Setup assets.project.com

Created assets.project.com S3 bucket:

aws s3api create-bucket --bucket assets.project.com --region us-west-1 --create-bucket-configuration LocationConstraint=us-west-1

Create assets-policy.json:

{
   "Statement": [
      {
         "Effect": "Allow",
         "Principal": "*",
         "Action": "s3:GetObject",
         "Resource": "arn:aws:s3:::assets.project.com/*"
      }
   ]
}

Edited assets.project.com policy

aws s3api put-bucket-policy --bucket assets.project.com --policy file://~/assets-policy.json

Create assets-cors.json:

{
  "CORSRules": [
    {
      "AllowedOrigins": ["*"],
      "AllowedHeaders": ["*"],
      "AllowedMethods": ["HEAD", "GET", "PUT", "POST", "DELETE"],
      "ExposeHeaders": ["ETag"]
    }
  ]
}

Edited assets.project.com CORS:

aws s3api put-bucket-cors --bucket assets.project.com --cors-configuration file://~/assets-cors.json

Setup project.com

Created project.com S3 bucket:

aws s3api create-bucket --bucket project.com --region us-west-1 --create-bucket-configuration LocationConstraint=us-west-1

Configure bucket as a website

aws s3 website s3://project.com/ --index-document index.html --error-document error.html

Create web-policy.json:

{
   "Statement": [
      {
         "Effect": "Allow",
         "Principal": "*",
         "Action": "s3:GetObject",
         "Resource": "arn:aws:s3:::datacoral.io/*"
      }
   ]
}

Edited project.com policy

aws s3api put-bucket-policy --bucket project.com --policy file://~/web-policy.json

Create web-cors.json:

{
  "CORSRules": [
    {
      "AllowedOrigins": ["*"],
      "AllowedHeaders": ["*"],
      "AllowedMethods": ["HEAD", "GET", "PUT", "POST", "DELETE"],
      "ExposeHeaders": ["ETag", "x-amz-meta-title", "x-amz-meta-label"]
    }
  ]
}

Edited project.com CORS:

aws s3api put-bucket-cors --bucket project.com --cors-configuration file://~/web-cors.json

Setup manager.project.com

Created manager.project.com S3 bucket:

aws s3api create-bucket --bucket manager.project.com --region us-west-1 --create-bucket-configuration LocationConstraint=us-west-1

Configure bucket as a website

aws s3 website s3://manager.project.com/ --index-document index.html --error-document error.html

Uploaded files to manager.project.com

aws --profile dccustomer s3 sync ~/dodgercms s3://manager.project.com/ --acl public-read

Created a user with the following policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1427944232000",
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket",
                "s3:GetObject",
                "s3:DeleteObject",
                "s3:PutObject",
                "s3:GetBucketWebsite",
                "s3:PutBucketWebsite",
                "s3:DeleteBucketWebsite",
                "s3:GetBucketLogging",
                "s3:GetBucketVersioning",
                "s3:GetBucketLocation"
            ],
            "Resource": [
                "arn:aws:s3:::data.project.com",
                "arn:aws:s3:::data.project.com/*",
                "arn:aws:s3:::assets.project.com",
                "arn:aws:s3:::assets.project.com/*",
                "arn:aws:s3:::project.com",
                "arn:aws:s3:::project.com/*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": "sts:GetFederationToken",
            "Resource": "*"
        }
    ]
}

When logging in via the manager.site.com bucket and creating a couple of files the navigation menu is not rendered correctly.

When accessing site.com it displays the default menu from the dodgercms website but doesn't generate the custom one.