Re:Thoughts on Go after writing 3 websites
by skrebbel on Tuesday January 01, 2013 @02:56AM
(#4992144)
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.
[ Parent
| on HN ]
Re:Thoughts on Go after writing 3 websites
by alecthomas on Tuesday January 01, 2013 @03:14AM
(#4992166)
I wrote gobundle[1] as one solution to this.
Re:Thoughts on Go after writing 3 websites
by StavrosK on Tuesday January 01, 2013 @10:10AM
(#4992705)
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.
Re:Thoughts on Go after writing 3 websites
by alecthomas on Tuesday January 01, 2013 @08:39PM
(#4994868)
It generates Go code which is compiled in to the package.
Re:Thoughts on Go after writing 3 websites
by eikenberry on Tuesday January 01, 2013 @03:41AM
(#4992199)
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.