Maintenance Container for asynchronous tasks

[PiyushRaj927]

Related issue Canasta#33
Related PRs Canasta#266, Canasta-DockerCompose#42
This PR adds a separate container to run maintenance script for MediaWiki installation

changes

The changes have been made using the base code from canasta and include the following modifications:

• Removal of Apache from Dockerfile and run-apache.sh along with related configuration files
• Updating the startup script to run the maintenance scripts as child processes
• Updating of the GitHub workflow (not tested)

testing

• Below is the process structure for the maintainance container

# pstree
docker-init---run-apache.sh-+-run-apache.sh---runuser---mwjobrunner.sh---sleep
                            |-run-apache.sh---runuser---mwtranscoder.sh---sleep
                            `-run-apache.sh---runuser---mwsitemapgen.sh---sleep

The sitemap script is disabled by default; It was enabled for testing purposes.

• The following parameters are modified in docker-image.yml from the Canasta repository to make it work for this repository
  • concurrency
  • on.push.branches
  • env.IMAGE_NAME
  • Image_ID
    I'm unfamiliar with GitHub workflow, so I cannot be sure if I have covered everything. Please let me know if I have missed something

I have tested the changes made by importing an existing wiki as well as creating a new one

PS- to locally test please edit the docker-compose.override.yml to point to the local images as there is no image in registry for this container

[jeffw16]

Not needed in maintenance container

[jeffw16]

The entire file is not necessary in this container and should be removed

[jeffw16]

This entire file is unnecessary in this container

[jeffw16]

Unnecessary file

[PiyushRaj927]

I have deleted the files as per the request.
Please review them.

[PiyushRaj927]

Hi @jeffw16, I was wondering if you had a chance to review my edits, and if there's anything I can do to help move the task forward. Please let me know if any further changes are required. Thanks

[jeffw16]

No, I have not had a chance to review your edits again. Sorry for taking so long; your patience is appreciated.

In case you are wondering if it looks bad to have a PR not merged in for being selected as a GSoC contributor: no, it's not. We're not counting it against any candidate who has a reasonable first draft of their code submitted in a PR. :)