You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I saw that there are three different images for the piped: piped-frontend, piped-proxy, piped.
These images are reasonable to separate from micro-service point of view and have some technical advantages such as easier version maintenance for different moving parts.
In the user's point of view, the docker-compose file complicates the deployment and maintenance for server admin. I am just wondering is it a good ideas that these services can be consolidated into a "All in One" style image? I totally understand if this is not preferred. In that case, please close this ticket.
Thank you for your work.
The text was updated successfully, but these errors were encountered:
Hi, I saw that there are three different images for the piped: piped-frontend, piped-proxy, piped.
These images are reasonable to separate from micro-service point of view and have some technical advantages such as easier version maintenance for different moving parts.
In the user's point of view, the docker-compose file complicates the deployment and maintenance for server admin. I am just wondering is it a good ideas that these services can be consolidated into a "All in One" style image? I totally understand if this is not preferred. In that case, please close this ticket.
Thank you for your work.
The text was updated successfully, but these errors were encountered: