Skip to content

Lets put the skeleton on PHP8.4/PHP8.5? #137

Description

@leoqbc

Hi guys I was facing some problems on updating my project to 8.4, but I've notice that on master(branch) there's already an addiction to solve the laminas/mime library problem, also we need to do some changes as:

  1. Rewrite project code from Runtime::coroutineEnable(true) to Runtime::coroutineEnable()(adapt to swoole 6)
  2. Update the Dockerfile headers to FROM hyperf/hyperf:8.4-alpine-v3.21-swoole
  3. Remove version: '3' from docker-compose.yml

In my opinion we just need to create a new release here and trigger it on Packagist to the updates.

Is there anything else you guys think we could change?

Is there someone there who can made this possible? we need to maintain this project as new users can test and start new projects with Hyperf, if this skeleton is lose we all lost a good tool.

Let me know what you think.

Have a good one!

Activity

  1. leocavalcante commented on Jan 27, 2026

    @leocavalcante
    Member

    Hi Leo,

    Thank you so much for taking the time to share these detailed observations and for caring about keeping the Hyperf skeleton project healthy and accessible! It's really great to see community members like you who are passionate about maintaining the tools we all rely on.

    Your suggestions are spot on:

    • Updating Runtime::coroutineEnable(true) to Runtime::coroutineEnable() for Swoole 6 compatibility
    • Updating the Dockerfile to FROM hyperf/hyperf:8.4-alpine-v3.21-swoole
    • Removing the deprecated version: '3' from docker-compose.yml
    • Cutting a new release to get the laminas/mime fix out to Packagist

    You've absolutely nailed the core principle here: the skeleton should remain as simple as possible, like a clean "Hello World", so that new users can run it without any friction. That first impression is everything when someone is evaluating a framework. If they hit roadblocks just trying to get the skeleton running, we risk losing them before they even see what Hyperf can really do.

    So any changes we make should focus on:

    1. Just working out of the box with the latest PHP/Swoole versions
    2. Minimal dependencies, only what's essential
    3. Clear, simple code that serves as a starting point, not a full application

    If you're interested in contributing these changes yourself, that would be incredibly valuable! The community would really appreciate it, and it sounds like you already have a clear understanding of what needs to be done. A PR with these updates would be very welcome.

    Let us know if you'd like to take this on or if there's anything we can help with!

    Have a great one too!

  2. leoqbc commented on Jan 29, 2026

    @leoqbc
    ContributorAuthor

    Hi @leocavalcante, thanks for kindly fast reply!

    I've notice that some of these code adaptations were already solved on the main branch, but still, there's no Dockerfile update from PHP8.3 to 8.4 nor 8.5, so I can work on these changes:

    • Updating the Dockerfile to FROM hyperf/hyperf:8.4-alpine-v3.21-swoole
    • Removing the deprecated version: '3' from docker-compose.yml
    • Changes on README.md to the version definitions

    Thanks again for your time, I'll send the PR soon

  3. leoqbc commented on Jan 30, 2026

    @leoqbc
    ContributorAuthor

    #138 Here's my PR fell free to give feedback, thanks. @leocavalcante

  4. leocavalcante commented on Jan 30, 2026

    @leocavalcante
    Member

    Closed by #138

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions