PHP Packages - Copy installed plugins and settings to new PHP version

Open
#2,619 7 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
php
Domain
devops

Research direction

Start from the Manage PHP Packages page and trace the flow for installing a new PHP version. Compare how configuration and installed extensions are represented, then define completion as allowing users to selectively copy settings and extensions from an existing version during installation.

Written by the indexing model from the issue text.

Description

Needs Triage
SYSTEM INFORMATION
OS type and version Ubuntu Linux 22.04.5
Webmin version 2.610
Usermin version 2.510
Virtualmin version 7.50.2 Professional
Theme version 26.20
Apache version 2.4.52
Package updates 45 package updates are available
Background
Image

On this page you can install and delete installed version of PHP which for me is one of the best features added lately.

the feature request

When you install a new version you have to install all of the relevant PHP Extensions you want to use and reconfigure settings as needed.

This would allow me to set my PHP environment once and when I need to upgrade the PHP version all I have to do is install the new version of PHP and not worry about setting it all up again.

Proposed solutions

  • On the manage PHP Packages page when you install a new version you have the option to copy the configuration and installed modules from another version. You would have a check box for config and one for extensions
  • Set up a template for the various extensions and settings so everytie you install a new version of PHP it uses a template similiar to server templates.

Thanks

Dominant language
HTML
Stars
6.1k
Forks
804
Avg merge
2d 9h
Merged PRs (30d)
21

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from webmin/webmin

All issues in webmin/webmin

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.