So I decided to build a process to fix this into our DevOps pipeline. ![]() The big issue we ran into was that Swagger lacked the capability to quickly and easily display Swagger documents to the whole team. We wanted these APIs documented to assist with both understanding what was available to use, and also to assist with testing, and decided to go with Swagger. Our PHP application is using Laravel as the back end, and we are utilizing the inherent capabilities to setup PHP APIs to pass information back and forth from our UI to the back-end. While I promised this post would cover setting up CD for your pipeline, I realized that I left out a fairly useful (but in my mind unique) part of the process. On my last two posts I went through setting up CI for your PHP project.
0 Comments
Leave a Reply. |