Hi there! I'm building my custom Headless CMS with next js for learning mainly and hosting my content for my future portfolio website. 2 days ago I noticed that next js doesn't serve static assets after build time in the public folder. It was stated in the docs and in my media directory of my project I've build an upload feature where I'm automatically compressing images(currently supporting only pngs,jpgs and gifs) and formting them to webps (gifs remaining the same). My backend creates 3 separate files small/medium/large and for the gifs - original ( I don't want to use cloudenary or any form of CDN for images). So far i have no issues other then in dev mode the hot reload doesn't work so I figured out ill use next dev for that 😄 ( I haven't setup ws properly to handle that in my server.js). My N 1 Question is is this gonna affect anything in production since so far I have no issues on my radar and testing went really good with 0 bugs. I haven't used a custom server before( Actually I did used one with socket.io for a meme game that I made with next js for some friends and myself). So please point out any cons that might be there in my approach, coz I'm afraid of a big rewrite of my Media section in the near future( atm It supports a lot of features and can link a given image to multiple content created by the user and vice versa ).