Will Laravel Hyperf migrate Sanctum package?

[binaryfire]

Hi @albertcht

I've been checking out laravel-hyperf and I'm very impressed. I created my own Laravel-style Hyperf skeleton for internal use but we had to roll our own solutions for auth, CSRF protection etc. In the end it was too much maintenance so we went back to just using Hyperf for microservices.

Would it be possible to open up the "Discussions" tab on the main repo? I wanted to ask if you'll be adding Sanctum-style (session-based) API auth.

[albertcht]

Hi @binaryfire ,

Welcome to contribute to the discussion by submitting your thoughts and ideas here . The hyperf-packages repository houses the core components of Laravel Hyperf, and we've enabled the discussions feature to foster community engagement and collaboration.

Regarding the migration of the Sanctum package, while I think it won't be a difficult task, I cannot commit to a specific timeline for its completion at this juncture.

Moreover, we enthusiastically welcome any pull requests from the community as we prepare to undertake the Sanctum migration process. Your contributions can significantly accelerate our progress and enrich the project.

[binaryfire]

@albertcht Thanks! Re: contributions, I can't contribute entire components but I'm happy to make PRs for small things when I come across them.

[binaryfire]

Hi @albertcht. One suggestion: it'd be great if the Laravel-Hyperf version of Sanctum can use the same db schema and token encoding as the Laravel version. That would let us connect a Laravel-Hyperf app to an existing Laravel database and open up some interesting possibilities for using the frameworks together. For example a Laravel app for the Livewire UI and a Laravel-Hyperf service for high traffic endpoints.

[albertcht]

Yes, we always try to keep the same table schema and communication payload with Laravel components if possible, such as cache and lock. In that way Laravel Hyperf can communicate with existing Laravel applications. (We also plan to implement the queue package in the next step.)

slide reference

[binaryfire]

@albertcht Very nice!