plesk / wordpress-aws-scaler Goto Github PK

site should be reachable via HTTPS (best is if HTTP redirects to HTTPS) --> needs certificate in ELB.

User need to have the ability to upload S3 files

Hi guys,

I followed you tutorial presented on code talks and I am curious how can you connect WP to S3 without any plugin? I never did this type of config and I am curios about it. Thank you

Later edit: I figured out the plugin but now the question is how do you set up WP under the ELB? Currently I have two ec2 instances under ELB and if I try to login, the pages simply redirects to it self. Thank you again

without CloudWatch Alarms AutoScaling does not work

We want users to be able to specify a domain name that should be automatically be configured in route53 and passed to the WordPress site inside the docker container. Route53 needs to point to the ELB then.

When running "manage_wordpress.sh list" you will see that it shows the auto scaling instances double. Normally maybe not a problem but you can now see it due to the other auto scaling instances.

Add the PHP deamon but not newrelic-sysmond. This should be installed on the server (EC2) itself

https://docs.newrelic.com/docs/servers/new-relic-servers-linux/installation-configuration/enabling-new-relic-servers-docker
http://code.tutsplus.com/tutorials/how-to-monitor-docker-based-applications-using-new-relic--cms-24891

Hi,
There is no such file called manage-wordpress.sh. So running the command sh manage-wordpress.sh cannot find the file.
If I change the file name to manage_wordpress and run it:

sh manage-wordpress.sh
manage-wordpress.sh: 16: manage-wordpress.sh: function: not found

manage-wordpress.sh: 53: manage-wordpress.sh: function: not found
manage-wordpress.sh: 57: manage-wordpress.sh: [[: not found

manage-wordpress.sh: 66: manage-wordpress.sh: function: not found
manage-wordpress.sh: 68: manage-wordpress.sh: [[: not found
manage-wordpress.sh: 75: manage-wordpress.sh: [[: not found
manage-wordpress.sh: 105: manage-wordpress.sh: function: not found
manage-wordpress.sh: 107: manage-wordpress.sh: Syntax error: "(" unexpected (expecting "}")

You need to delete all files first before removing the bucket

New API set need to be created separately from the user. This so that on multiple servers, multiple keys can exists

When trying to deploy this, AWS says it cannot find the AMI ami-64385917. Is this a private one, and if so, what AMI was it based off ?