laurilehmijoki / s3_website

Manage an S3 website: sync, deliver via CloudFront, benefit from advanced S3 website features.
Other
2.25k stars 187 forks source link

Octopress uses 'public' default output directory, s3_website expects Jekyll's _site #48

Closed alexandroid closed 9 years ago

alexandroid commented 10 years ago

It would be nice to override default site root in s3_website.yml so one does not have to invoke s3_website push --site public.

Alternatively, s3_website can fallback to public if _site does not exist. Since it's positioned to work with Octopress it looks weird that it does not find public by default... am I missing something?

laurilehmijoki commented 10 years ago

s3_website does not yet recognise Octopress. Let's add the public dir into the default lookup directories.

See examples: https://github.com/laurilehmijoki/s3_website/blob/master/lib/s3_website/paths.rb#L4 https://github.com/laurilehmijoki/s3_website/blob/master/lib/s3_website/jekyll.rb

Edit: Remember to add an example of Octopress support: https://github.com/laurilehmijoki/s3_website/blob/master/features/nanoc-support.feature

sondr3 commented 10 years ago

Also, Octopress 3 is supposed to be a gem so this might not be a problem in the future.

laurilehmijoki commented 9 years ago

Closing as inactive. Please reopen if needed.