s3_website | S3 website : sync , deliver via CloudFront | Static Site Generator library

by laurilehmijoki Scala Version: v3.4.0 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | s3_website Summary

s3_website is a Scala library typically used in Web Site, Static Site Generator, Jekyll applications. s3_website has no bugs, it has no vulnerabilities and it has medium support. However s3_website has a Non-SPDX License. You can download it from GitHub.

Manage an S3 website: sync, deliver via CloudFront, benefit from advanced S3 website features.

Support

Quality

Security

License

Reuse

Support

s3_website has a medium active ecosystem.

It has 2261 star(s) with 194 fork(s). There are 54 watchers for this library.

It had no major release in the last 12 months.

There are 73 open issues and 191 have been closed. On average issues are closed in 75 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of s3_website is v3.4.0

Quality

s3_website has 0 bugs and 0 code smells.

Security

s3_website has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

s3_website code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

s3_website has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

s3_website releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of s3_website

Get all kandi verified functions for this library.

s3_website Key Features

No Key Features are available at this moment for s3_website.

s3_website Examples and Code Snippets

No Code Snippets are available at this moment for s3_website.

Community Discussions

Trending Discussions on s3_website

How to fix "s3_website" issue while pushing Jekyll site on CloudFront through gitlab CI/CD?

Broken routes with react app on S3 hosting using s3_website gem

Cloudfront is inconsistent in serving HTTPS content

QUESTION

How to fix "s3_website" issue while pushing Jekyll site on CloudFront through gitlab CI/CD?

Asked 2019-Jul-31 at 01:55

I have created Pipeline in GitLabs and I am using docker as gitlab-runner. I want to push Jekyll website on s3 website. And to do so, I am using s3_website gem. I have 4 stages defined in my pipeline. Where I am building Jekyll, creating Artifacts using Gulp, executing test on my jekyll site and then deploying.

All steps are working fine but while doing deployment, I'm getting following error. And i could not figure it how to get this solve.

...

ANSWER

Answered 2019-Jan-18 at 18:05

We ran into this same error on CircleCI. If I understand correctly, the s3_website gem wraps a Java .jar that's using JRuby 1.7, and something must have changed in one of the Docker images or Ruby gems that causes it to start inheriting the system's Ruby 2+ path. As a result, its JRuby 1.7 tries to load Ruby gems that only work in Ruby 2.0 and above, so it runs into errors.

As a workaround, instead of letting the s3_website gem invoke the .jar file itself, I tell the s3_website gem to only download the .jar file, then I manually invoke it:

Source https://stackoverflow.com/questions/54175990

QUESTION

Broken routes with react app on S3 hosting using s3_website gem

Asked 2018-Feb-18 at 21:06

I am using S3_website gem to push a react build to my bucket. Everything works great but when I navigate to a custom url and I hit refresh, I get a 404 error because it tries to find this object in the bucket instead of executing the route.

I have the default config in the s3_website yml with no redirect rules.

...

ANSWER

Answered 2018-Feb-18 at 21:06

In your bucket properties under Error Document just use the same file as the Index Document which should be your index.html

Source https://stackoverflow.com/questions/48854822

QUESTION

Cloudfront is inconsistent in serving HTTPS content

Asked 2017-Oct-22 at 21:22

I'm trying to update my blog (jacopretorius.net) to use HTTPS. Instead of just trying this on the live version I have created a staging version to test this - staging.jacopretorius.net

My stack looks like this:

Jekyll
Amazon S3
Amazon Cloudfront
Amazon Route53

I am deploying the generated Jekyll content to an S3 bucket using the s3_website gem. This gem also updates the associated Cloudfront distribution. I configured the Cloudfront distribution to use my certificate and added the staging URL as a CName to the distribution. Lastly I added 2 aliases from Route 53 to point to the distribution, one for IPv4 and one for IPv5.

Everything seems to be working as expected, except for some bizarre behavior I don't understand. All the pages seem to be served via HTTPS, except for https://staging.jacopretorius.net/archive/. I thought this might be because the URL doesn't have an extension, but https://staging.jacopretorius.net/about/ is being served correctly. This is happening consistently in both Chrome and Safari.

When I dump the headers using curl the headers seem to indicate that the one URL (the /about/ one) is always a Cloudfront miss.

...

ANSWER

Answered 2017-Oct-22 at 20:51

The https://staging.jacopretorius.net/archive/ page is being served as secure when I load it. What makes you say it isn't being served secure exactly? If you type in https:// and see the page content then the page is being served over HTTPS, but if you don't see the green lock icon the browser doesn't think the page is fully secure. You need to click the little (i) icon in the Chrome browser address bar and see what the actual issue is. The browser wouldn't be displaying any page content at all if it had an issue with the SSL certificate on that page.

I see a message in Chrome that not everything on the page is secure. I think that's because the search form on the page has an http://www.google.com/search target. Try changing that to https://www.google.com/search (and clear the CloudFront cache for /archive/ after making the change).

Source https://stackoverflow.com/questions/46878946

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install s3_website

s3_website needs both Ruby and Java to run. (S3_website is partly written in Scala, hence the need for Java.).

Support

We (users and developers of s3_website) welcome patches, pull requests and ideas for improvement. When sending pull requests, please accompany them with tests. Favor BDD style in test descriptions. Use VCR-backed integration tests where possible. For reference, you can look at the existing s3_website tests. If you are not sure how to test your pull request, you can ask the gem owners to supplement the request with tests. However, by including proper tests, you increase the chances of your pull request being incorporated into future releases.

Find more information at: