joomla / joomla/framework.joomla.org
Automate Deployments
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 37
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
The new Jenkins CI system for joomla.org should be utilized to automate code deployments for this repository. To that, the following steps are required:
- Remove compiled assets from this repository
- Laravel Mix manifest
- SRI manifest
- CSS/JS
- Adjust the live server to support a minimal downtime deployment workflow
- New
deploymentsdirectory
- New
- Create a job on the Jenkins system to deploy changes for the application
- Package is extracted to
deploymentsprovisioning space - Add some kind of "maintenance mode" (
./artisan downand./artisan upthing) to deploy database schema changes as required - Change
public_htmlto point to new deployment
- Package is extracted to
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's deployment configuration, the Jenkins system for joomla.org, and the live server's public_html layout. The work is complete when compiled assets are removed, deployments can be staged with minimal downtime, required schema changes run with maintenance mode, and Jenkins switches public_html to the new deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100