If someone asked me the question "what layout should I use for my Go code repository?", I'd start by asking back "what are you building: an executable, or a library?"
Create a directory named however you want your final executable to be called (e.g. "mycommand"), change into that directory, and create the following files:
| // -------------------------------------------------- | |
| // require modules | |
| // -------------------------------------------------- | |
| const pkg = require('./package.json') | |
| const path = require('path').posix | |
| const exec = require('child_process').execSync | |
| const BannerPlugin = require('webpack/lib/BannerPlugin.js') | |
| // -------------------------------------------------- | |
| // Prerender routes |
| module.exports = function () { | |
| // | |
| // [ express middleware ] | |
| // Generate a /fake/images route for testing images source | |
| // | |
| // images service origin: | |
| // - PICSUM(https://picsum.photos) | |
| // Created by David Marby & Nijiko Yonskai | |
| // Having trouble? Poke @DMarby on Twitter | |
| // Images from unsplash |