https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hosting-wordpress.html

Please support HTTPS. Dr. Loraine has a certificate for lorainelab.org domain. Also provide domain name, e.g., test.lorainelab.org.

Please also provide me with a bitbucket repo to upload all the code.

Current setup for WordPress needs the files to be placed in the default root directory of httpd , this setup is interfering with the reverse proxy setup done for Jira and confluence and preventing the opening of wp-login.php file

I am still trying to figure out some solution for the login page. But I want to know what possible alternatives would be considerable incase I am not able to figure the issue with the interfering reverse proxy setups.
1. I read something about tomcat to run php. we can then modify the port(this way ports will be seperate) in server.xml for that tomcat and follow the same config we use in reverse proxy setup of jira and confluence.
2. AWS Elastic beanstalk needs more exploration here we will use the db setup already done via ansible
3. Use some other separate lightweight server like t2 micro
4. Docker idea.

In either case all 4 options can use the already developed db setup. [~aloraine] Please advise on the above.
Incase of docker idea. Please send me any documents on the docker setup of wordpress idea

Please provide me with a t2.micro instance with an ubuntu v20 image and associate the IP address of that instance to test.lorainelab.org..Please also provide me with SSL certificates of lorainelab.org. The ones I have are for bioviz.org

[~aloraine]

Codebase added to bitbucket: https://bitbucket.org/chesterdias/lorainelabs/src/master/

test.lorainelab.org is currently redirecting to testjira IP address. [~aloraine] Could you please check that?

Code is added to the repository with SSL capability.Ensure to use the correct cname while creating the SSL certificate

Please update the documentation and make sure everything is explained clearly so that we can re-use these when needed.

Documentation is updated.

Re-opening for a refresh and revision of the playbooks.

Update:

• Established that I can install an entirely new, fresh Wordpress instance
• Established that I can also install a copy of our existing Wordpress by installing a fresh Wordpress instance and then deploying an sql and a "tarball" backup containing wp-content tarball

Next:

• Add copying of .htaccess file from source (a backup)
• Create playbooks for creating the backup files, which will include:

• .htaccess file

The new playbooks code is version-controlled here: https://bitbucket.org/lorainelab/wordpress/src/main/

The README explains how to run the playbooks.
There still needs to be a set_vars_example.yml for people to follow. Adding that next.

Added example setup_vars.yml, aws_vars.yml and inventory.ini files. Included instructions on how to manually run certbot on the host.

Done for now!