What about dependencies? Client-side resources such as .js and .css files, configuration files maybe, migrating the data even? A web app is (virtually) never just its server side code.
That's very interesting! Do you just append the bundles to the executable and then have it read itself? I didn't look at the code, admittedly.
It generates Go code which is compiled in to the package.
The original article didn't discuss deploying assets, only the app/code. I suppose that might have been implicit, but I typically handle them separately.