overview for Drun

[SOFTWARE REQUEST] Core for new API in c/webdev@programming.dev

[–] Drun@lemmy.world 1 points 5 months ago

They certainly do (from database). Maybe you're right - main reason I didn't wanted to use current stack is because outdated PHP curl (TLSv1, eh), but I can probably achieve the same with “exec”.

I'll look into that.

[SOFTWARE REQUEST] Core for new API in c/webdev@programming.dev

[–] Drun@lemmy.world 1 points 5 months ago (2 children)

:(

[SOFTWARE REQUEST] Core for new API in c/webdev@programming.dev

[–] Drun@lemmy.world 1 points 5 months ago

It has so much. I think it may be a problem to maintain it just for the API. Perhaps, there’s something a little bit more compact?

15

[SOFTWARE REQUEST] Core for new API (lemmy.world)

submitted 5 months ago by Drun@lemmy.world to c/webdev@programming.dev

6 comments fedilink

I am currently working on a fairly old website service for the company's internal needs. The stack is quite old - PHP 5.3. It so happened that company can't abandon it right now.

... In short, I received a task to develop a REST API for this service. It is clear that I cannot use the current stack. What can I use as a standalone core for the new API? The main thing for me is the speed of development and ease of learning. For example, I would like Bearer authorization / some rights model out of box.

Something like Laravel, but separate instance of it just for the API seems a little overkill for me. What you can advise me? Any boilerplates / software recommendations are welcomed.

PS: My database is MSSQL 2016, so it could be a problem.

this is all in c/fuckcars@lemmy.world