[GH-ISSUE #535] Migrate to Forked Silex Version in Flyimg Organization #195

New issue

Closed

opened 2026-02-25 22:34:35 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 22:34:35 +03:00

Owner

Originally created by @sadok-f on GitHub (Oct 25, 2024).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/535

Originally assigned to: @sadok-f on GitHub.

Currenttly Flyimg relies on the Silex micro-framework, which is now deprecated and no longer supported. To ensure long-term maintainability and compatibility with modern components, we need to migrate to a forked version of Silex, available in the Flyimg organization, which incorporates the latest Symfony components and has been adapted to meet Flyimg's specific requirements.

Tasks:

Replace existing Silex dependency with the Flyimg forked version.
Update any incompatible components or code structures to align with the latest Symfony components.
Thoroughly test the application to ensure functionality remains consistent.
Document any code changes or additional setup required for contributors.

Acceptance Criteria:

Project runs without errors using the Flyimg forked Silex version.
All tests pass with the new setup.
Documentation is updated where necessary.

Additional Context: Switching to this forked version will help keep the project up-to-date with the latest Symfony features and security improvements, while preserving the familiar Silex micro-framework structure.

Originally created by @sadok-f on GitHub (Oct 25, 2024). Original GitHub issue: https://github.com/flyimg/flyimg/issues/535 Originally assigned to: @sadok-f on GitHub. Currenttly Flyimg relies on the Silex micro-framework, which is now deprecated and no longer supported. To ensure long-term maintainability and compatibility with modern components, we need to migrate to a forked version of Silex, available in the Flyimg organization, which incorporates the latest Symfony components and has been adapted to meet Flyimg's specific requirements. **Tasks:** 1. Replace existing Silex dependency with the Flyimg forked version. 2. Update any incompatible components or code structures to align with the latest Symfony components. 3. Thoroughly test the application to ensure functionality remains consistent. 4. Document any code changes or additional setup required for contributors. **Acceptance Criteria:** - [x] Project runs without errors using the Flyimg forked Silex version. - [x] All tests pass with the new setup. - [x] Documentation is updated where necessary. Additional Context: Switching to this forked version will help keep the project up-to-date with the latest Symfony features and security improvements, while preserving the familiar Silex micro-framework structure.