Building for production

From go run to a shippable binary

All course long your inner loop was go run . — compile and run in one step, nothing left on disk. To ship, you run go build instead. It produces a single, self-contained executable: your whole program plus every dependency, statically linked into one file.

That's the payoff Go promised back in module 00. There's no runtime to install on the server, no node_modules, no interpreter. You copy one file and run it:

go build -o pawwalk .
./pawwalk

-o pawwalk names the output. Without it, Go names the binary after the folder. That's the artifact you deploy.