This is what is used to drive some of the assignments of values in LocalSettings.php, the file in MediaWiki which drives the behaviour of the MediaWiki instance. Parameters to PHP can be passed via the EB environment variables. Which can be seen as good thing, as it forces the developer to abstract from the underlying LAMP stack. The biggest challenge is that you have very little control (in the traditional sense) within the EC2 instances launched by EB. This asks for some creativity combining the EB CLI with the lower level interface to the EB API via the AWS CLI. And the EB CLI doesn’t provide all the functionality you find in the EB GUI. But more importantly you don't want to manage another database! Web Application Deployment Elastic Beanstalkĭue to the high level nature of the EB GUI, the (also high level) EB CLI are not completely in sync. This means the database isn't running on the same instance as the web server, and allows to scale to multiple web servers using a single database. MediaWiki uses a LAMP stack (preferred) and I used the RDS service (single AZ) to provide the database layer to the web server(s). I have found that jq is the command line swiss army knife for JSON and reading basic values from even the most complex JSON is straightforward. No surprise, BASH backdates JSON by about a decade. One shortcoming of BASH is not being able to read JSON elegantly. These scripts are meant for those who have a free-tier AWS account to set up a wiki quickly while maintaining full control over the Mediawiki source code for development of a custom version of MediaWiki instance. Python, BASH is the universal screwdriver found everywhere -)Īnother motivation to use BASH is not to be dependent on any other 3rd party tools commonly used in bigger AWS environments (e.g. While BASH can be archaic and doesn’t result in more elegant code as e.g. The scripting language used is available on almost all UNIX, Linux and OS X hosts. Implementation considerations Language: BASH The source code is uploaded to S3 as zip file, EB is able to use this zip file on S3 to deploy the application in the instances it creates. 2 subnets are private and used for RDS to provision the MySQL database. 2 subnets are public internet facing and will be used by Elastic Beanstalk to deploy the Load Balancer and the web server instance(s). In the VPC 4 subnets are created and spread over 2 Availability Zones. The deployment scripts create a complete dedicated VPC, and RDS service, S3 storage and the deployment in Elastic Beanstalk (EB). Mediawiki deployment is done using Elastic Beanstalk. For more information on this and other Gmail issues related to outbound email from your application, refer to our Gmail SMTP troubleshooting page.The scripts are to assist in deploying MediaWiki on AWS EC2 and RDS. To proceed, you will need to manually confirm the validity of the authentication attempt before Gmail will permit the application to send outbound emails. When this happens, you will receive a Gmail security alert at the corresponding Gmail address. NOTE: If you are using Gmail as the outbound email server, your application’s attempts to send outgoing emails may be blocked by Gmail if it considers the authentication attempts to be suspicious. To configure the application to use other third-party SMTP services for outgoing email, such as SendGrid, refer to the FAQ. Replace USERNAME and PASSWORD with your Gmail account username and password respectively. This example shows how to configure it using a Gmail account. Add the following code to the end of the /opt/bitnami/mediawiki/LocalSettings.php MediaWiki configuration file according to your SMTP server settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |