PHP plugin - cannot easily run multiple versions concurrently

オープン
  • 何か問題がありますか？
#2,720 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go, nginx, php
領域
devtools

調査の方向性

Start by reading the PHP plugin and the automatic plugin-inclusion mechanism; the issue does not identify their file paths, so locate them in the repository. Then determine how package versions select plugins and how version-specific environment variables affect process-compose. Done means multiple PHP versions can run concurrently with the appropriate plugins and the behavior is covered by tests.

索引モデルが issue の本文から書いたものです。

説明

feature looks hard p3 processed triage
What problem are you trying to solve?

Hello,

Use case
I want to build a dev stack for our dev team based on devbox. The full featured application is micro-services oriented, so running a fully working application requires to run multiple smaller projects simultaneously. Those applications are mostly in PHP, but the required versions are not always the same. To avoid running a devbox for each project, which would be perfect to manage versions but hard to orchestrate and resource consuming (n web server process and m PHP FPM while 1 web server and less PHP FPM are really required).

What I am willing to achieve
A single stack built on devbox running a single web server (nginx) and multiple PHP-FPM to run all micro-services simultaneously from a centralized.

What makes it hard
Currently, when a PHP package is added, the generic PHP plugin is enabled. If another PHP package is added, the same plugin is used and that forbids to run concurrent PHP FPM servers with process-compose.

Good to know
Devbox is great, I love it :)

What solution would you like?

Solution : Split the official PHP plugin into PHP plugins by version

Duplicate the official PHP plugin : one per version (probably minor versions : 7.4, 8.0, 8.1, ...)
Each plugin has then to be modified to use version specific env vars.
I guess that is the main change on the plugin itself.
The other modification is probably to be done on the automatic plugin inclusion mechanism that should include the right plugin depending on the adde PHP package version (I do not know how that is done at the time and cannot evaluate the impact of such a change).

Main advantage : It would benefit to all devbox users.

Of course, I would be glad to participate actively to the implementation.

Alternatives you've considered

Selfish solution : create my own private plugins based on the official PHP plugins

I guess I would :

  • create thoses plugins by version in a private repo
  • disable php plugin
  • include manually the plugins by version in the full stack devbox config
主要言語
Go
スター
12.4k
フォーク
358
平均マージ
17時間 12分
マージ済み PR（30日）
31

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

jetify-com/devbox のほかの issue

jetify-com/devbox の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。