PHP Packages - Copy installed plugins and settings to new PHP version
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
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
| 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
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 Packagespage 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
- 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.
More from webmin/webmin
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules listOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webmin/webmin#2801 · 6 comments ·
Maintainers usually reply within 1 day
-
Needs Triage Stale
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
webmin/webmin#2613 · 5 comments ·
Maintainers usually reply within 1 day
-
Needs Triage Stale
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webmin/webmin#2574 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
area:infra bug security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ilia-sokolov/OfficeAgent.NET#84 ·
Maintainers usually reply within 13 days
-
bug triage:owned
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[Bug]: Fix invalid reusable workflow paths in CI and deployment workflowsPossibly taken @anshulchikhale30-p claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
podman-container-tools/podman.io#812 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nutmos/expensetrackr#157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
janitor-team/janitor#2613 ·
Maintainers usually reply within 1 day