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
Currently, the deploy action pulls a Golang base image and runs the Dockerfile to compile the executable. This means every time we use the action, we're unnecessarily rebuilding the executable.
Instead, we could optimize this by pulling a minimal image with just the prebuilt Go executable. This would reduce build time, minimize dependencies, and improve efficiency without changing functionality.
Would you consider updating the workflow to use a prebuilt binary instead? Happy to discuss possible solutions!
The text was updated successfully, but these errors were encountered:
DarVoid
changed the title
Please use a built go executable for deployments
Use a built go executable for deployments
Feb 27, 2025
DarVoid
changed the title
Use a built go executable for deployments
Use a pre-built go executable for deployments
Feb 27, 2025
Currently, the deploy action pulls a Golang base image and runs the Dockerfile to compile the executable. This means every time we use the action, we're unnecessarily rebuilding the executable.
Instead, we could optimize this by pulling a minimal image with just the prebuilt Go executable. This would reduce build time, minimize dependencies, and improve efficiency without changing functionality.
Would you consider updating the workflow to use a prebuilt binary instead? Happy to discuss possible solutions!
The text was updated successfully, but these errors were encountered: