You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 current dependencies requiring php-64bit: phinx and zipstream-php. This makes the project unusable on 32bit architectures such as arm/v7 (old but still viable Raspberry PIs, for example, ideal for self-hosting@home).
Desired Behavior
The ideal outcome would be the project supporting 32bit architectures, by adopting compatible dependencies.
Additional Context
I haven't been able to assess the impact of zipstream-php, and its replaceability. Phinx, on the other hand, seems to be a show-stopper, because they explicitly don't support 32bit, thus the initial migrations are not working (I've also tried using a previous version without the explicit 64bit requirement, but I get the same error described in the linked issues). In order to accomplish 32bit support, the entire migration system should probably be replaced.
I think this request is also somehow linked to #206
The text was updated successfully, but these errors were encountered:
Description
There are 2 current dependencies requiring php-64bit: phinx and zipstream-php. This makes the project unusable on 32bit architectures such as arm/v7 (old but still viable Raspberry PIs, for example, ideal for self-hosting@home).
Desired Behavior
The ideal outcome would be the project supporting 32bit architectures, by adopting compatible dependencies.
Additional Context
I haven't been able to assess the impact of zipstream-php, and its replaceability. Phinx, on the other hand, seems to be a show-stopper, because they explicitly don't support 32bit, thus the initial migrations are not working (I've also tried using a previous version without the explicit 64bit requirement, but I get the same error described in the linked issues). In order to accomplish 32bit support, the entire migration system should probably be replaced.
I think this request is also somehow linked to #206
The text was updated successfully, but these errors were encountered: