Jump to content

Community

sobrenome

+Clients
  • Content Count

    2,028
  • Joined

  • Last visited

4 Followers

About sobrenome

  • Rank
    Community Regular

Recent Profile Visitors

11,950 profile views
  1. What's the best image size for clubs hero image? Yes. We have to do it manually now, reducing the actual size in css.
  2. I will try to configure and give a feedback. In IPS settings I will have to set the SMTP mode, right?
  3. Thanks! It’s a testing website! The point is to show how many assets are loaded by post before register and how long they take to load. It’s a feature the should be loaded only if the guest started typing some post.
  4. I have noticed this today. It promotes a very hard slowdown:
  5. Hello, I have the app already installed. How can I access the details for configure Amazon SES? Thanks. Maybe I will have the same issue you had. Could please tell what Cloudflare firewall setting had to be changed? Thanks. Now I see. Thanks a lot for sharing.
  6. My bad. We can use the custom URL field to solve this issue.
  7. The Amazon S3 bucket accepts two types of URL formats to deliver the stored files: 1) bucket name as subdomain: BUCKET-NAME.s3.sa-east-1.amazonaws.com/example/example.png 2) bucket name as a folder: s3.sa-east-1.amazonaws.com/BUCKET-NAME/example/example.png IPS chose the last approach, which does not allow the use of a CNAME in Cloudflare to put it in front of Amazon S3, or even a CNAME without Cloudflare to hide Amazon URL. I would really appreciate if IPS could change the URL generated to Amazon S3 storage to be the first option (bucket name as subdomain), or ate least to give us the option to choose between them. Using Cloudflare in front Amazon can help us save a lot of money. And in some countries, Cloudflare has many more POPs than Amazon. If anyone has any other solution, I appreciate. Here follows the Cloudflare tutorial to put it on front of Amazon S3: ====== I actually just set this up - you don’t need to enable “static hosting” on a S3 bucket as long as the bucket name is the same as the FQDN; So if you want wow.example.com as the custom domain: create a bucket named exactly wow.example.com go to Cloudflare -> DNS tab and create a CNAME. Name is wow and target is wow.example.com.s3.us-east-1.amazonaws.com Note: replace us-east-1 with the region where you created your S3 bucket. AD3415E1-BA50-43F6-985D-7CD0C5F1EF13.jpeg2208×411 92 KB Now I would recommend creating a page rule that matches wow.example com/* so that you can set “cache level” to “cache everything” (also set “SSL” to “Full”) ====== https://community.cloudflare.com/t/is-it-possible-to-use-cloudflare-aws-s3-without-setting-up-s3-static-hosting/52711/13
  8. Nice, we use it also. Did not know that it has AWS email already!
  9. Very good news! CSS and JS are the major concerns: https://developers.google.com/speed/pagespeed/insights/?hl=pt-br&url=https%3A%2F%2Finvisioncommunity.com%2Fforums%2Ftopic%2F452996-445-release-and-mobile-speed-up%2F
  10. Resize images is awesome! Great news!
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy