Search the Community
Showing results for tags 'amazon'.
Has anyone come across this issue where Amazon Cloudfront seems to refuse to cache a certain small number of static objects? I've tried invaliding the cache (root path) several times to no avail. I had a look at the file permissions of the objects in question, and they seemed all ok. I've also gone into the Amazon Console and there are no errors logged. You can see more details of this here : http://www.webpagetest.org/performance_optimization.php?test=171106_A4_be80c122489ae6fabf5e2caadcac8123&run=1#use_of_cdn I recently upgraded this test site to PW 3.062 from PW 2.8.x and noticed this was happening. I'm also running the latest version of Procache on this site.
Hi there, I was looking for some Processwire + Amazon integration advice. I've never built an e-commerce platform before and surprisingly there's hardly any articles or forum posts when you type in variation searches of "Amazon + Processwire" Are there any 3rd party tools and services you recommend? Any gotchas I should be aware of ? Thanks in advance!
Hi all, I am trying to use Amazon S3 to store video files for a client. I am having trouble getting the SDK to work. I am sure it is a stupid error on my part but my head is sore from banging it against my desk and I thought I would finally ask for some help. I am running PW 3.0.11 on NGINX. 1. Amazon recommends using Composer to install the SDK. I was not sure where in the path to install the SDK so I put composer in the /site folder and installed the SDK there (putting vendor at the same level as modules), then I put the require and uses statements in _init.php. I always got an error saying it could not load the aws or s3 classes from the library. 2. So, then I tried to use aws.phar. I put that in the /site directory but once again, no matter what I do, it will not load with the following error: require(): Failed opening required '/site/aws.phar' The file is there with proper permissions and the code for loading is: // --- amazon S3 stuff require $config->urls->site . 'aws.phar'; $s3 = new Aws\S3\S3Client([ 'version' => 'latest', 'region' => 'us-standard', ]); So, here are my questions: 1. In general, where is the correct place to put a php library? It is not a PW module so I assume it should not go in the modules folder. 2. Should I use Composer to install the SDK? If so, where do I put the files? Should I add the AWS SDK to the main composer.json file or put it somewhere else? 3. If I don't use Composer, where do I put the aws.phar file so that PW can load it? 4. Should I not put the 'require' in the _init.php file and move it to another file (_func.php)? I am sure there is a massive face-palm in my future when this gets sorted out. Thanks
It is unfortunate that I must learn so many things the hard way. After changing my Amazon Elastic Beanstalk with deployed Processwire code the Amazon Elastic cloud removed the website content because it is a stateless environment. Here is the article that explains this: https://www.otreva.com/blog/deploying-wordpress-amazon-web-services-aws-ec2-rds-via-elasticbeanstalk/ I think my mistake is that inside the instance I stored content inside the instance that was running mysql and not the other instance that I thought was the database but I am not sure. Understanding elastic beanstalk as a stateless environment is very important and means that the server instance will terminate and rebuild automatically and any local content will not be replicated unless deployed through the beanstalk environment. This means you you should not ftp php code changes but should instead write scripts or use the EB CLI with GIT hooks to deploy new code or deploy a new zip file version through elastic beanstalk. So my question for the forum is will Processwire work in a stateless environment like Amazon Elastic Beanstalk? If all content including images, etc. is stored in an outside database (RDS) and connect to the Amazon EC2 instance then it should all work. If any content or settings are stored inside the EC2 instance like what I think happened to me with mysql running inside my EC2 instance then when Elastic Beanstalk terminates and rebuilds environments the content will be lost. It is scary to think that all the admin controls will be lost if they are not stored outside the EC2 instance inside the RDS database otherwise Elastic Beanstalk will wipe them out terminating and rebuilding, bummer. If anyone can add advise on this subject of PW running inside stateless environments it is much appreciated. Sincerely, March