[FEATURE] Add Separate Dockerfiles for Dev & Production Builds

[dwisiswant0]

Describe your feature request

Splitting the Dockerfiles into two: one for development and one for production.

The development Dockerfile will keep the current multi-stage build process, while the production one will be built from scratch, with no unnecessary dependencies like chromium. This will make the production image leaner, more secure, and easier to maintain.

Describe the use case of the feature

Improve our container deployment process by using a super minimal image for production. Since we don’t need stuff like chromium and other build-related packages in production, the scratch-based image will keep things small and simple, without any extra bloat.

The development Dockerfile will keep all the tools and dependencies needed for local testing and building. The production Dockerfile will be stripped down and optimized for deployment - ready to be pushed to container registries (Docker Hub/GHCR/Artifact Registry). This setup also makes things easier when we need to update/rollback images in cloud envs.

Describe alternatives you've considered

No response

Additional context

Here's what the Dockerfiles would look like:

1. Development Dockerfile (same as now)

nuclei/Dockerfile

Lines 1 to 15 in c8cc419

	# Build
	FROM golang:1.21-alpine AS build-env
	RUN apk add build-base
	WORKDIR /app
	COPY . /app
	RUN go mod download
	RUN go build ./cmd/nuclei
	# Release
	FROM alpine:3.18.6
	RUN apk upgrade --no-cache \
	&& apk add --no-cache bind-tools chromium ca-certificates
	COPY --from=build-env /app/nuclei /usr/local/bin/
	ENTRYPOINT ["nuclei"]

2. Production Dockerfile

FROM scratch

COPY nuclei /

ENTRYPOINT ["/nuclei"]

The idea is to keep both files in the repo (maybe as Dockerfile for dev and Dockerfile.prod for production). This way, the dev Dockerfile keeps all the build stuff, and the scratch one will be used for production.

Additional references:

• https://docs.docker.com/build/building/base-images/#create-a-base-image
• https://goreleaser.com/customization/docker/#how-it-works

[dwisiswant0]

Blocked by #5692