13 mintes in to video, and I love it already! thanks for sharing proper knowledge,
@microapis
2 ай бұрын
Thank you for your supportive comment @venil82 🙌!
@polatkaya418
7 ай бұрын
Came from your comment on my Post in Reddit, absolute teacher!
@microapis
7 ай бұрын
Thank you for your kind words and for visiting 🙌!
@user-nl3tt6dc1i
29 күн бұрын
Hey man, thanks for your work. Im spinning up a personal project and i chose Flask for the RESTapi. This video is perfect, thank you. Subbed btw haha
@microapis
29 күн бұрын
Thank you I'm so glad you found it useful 🙌! Flask is an excellent choice and very powerful when used properly. Good luck with your project and feel free to reach out if you have any questions!
@self.improved
Ай бұрын
Really nice video, and I appreciate your experiential knowledge. This is something that isn't easy to find.
@microapis
Ай бұрын
Thank you for your kind words 🙏! This is the exact reason why I created this channel 🚀🚀!
@jbjc3924
7 ай бұрын
very exited to get started thank you for putting this together
@microapis
7 ай бұрын
Thank you! Glad to help if something isn't clear or you need any help!
@mlsandreas
7 ай бұрын
Thank you for this video!! waiting for more content. So My question flask or fastapi , what is your choice?
@microapis
7 ай бұрын
Thank you @mlsandreas! If I'm going to build just an API, FastAPI is my choice. If I'm going to render HTML and such, I go with Flask. You can render HTML with FastAPI via Starlette too, but I just find Flask more convenient. Also I like the concept of middleware in Flask (aka plugins) slightly more. However, for the most part I find both frameworks very similar. Do you have a preference?x
@mlsandreas
7 ай бұрын
@@microapis i prefer flask because i want to use it not for apis but for web apps too
@microapis
7 ай бұрын
That makes perfect sense! Only recommendation I make to organisations making this move is to use to use a proper Flask framework (aka plugin) for the API implementation 🚀
@chidobg84
6 ай бұрын
Excellent work sir, thank you for your work. Do you know of anyway to avoid using the CDN for the OPEAPI_SWAGGER_UI_URL and other external urls? Assuming policy does not allow use of CDNs.
@microapis
2 ай бұрын
Thank you for your question! A workaround would be serving the Swagger UI assets from your own domain. For example, you can download the assets here: cdn.jsdelivr.net/npm/swagger-ui-dist/. You could serve them from Flask, from an S3 bucket if you use AWS, from Cloudflare if you use that, or any other alternative.
Пікірлер: 19