Folder Structure
Motivations
- Clear feature ownership
- Module usage predictibility (refactoring, maintainence, you know what's shared, what's not, prevents accidental regressions, avoids huge directories of not-actually-reusable modules, etc)
version: '3.7' | |
services: | |
app: | |
command: tail -f /dev/null | |
image: golang:1.12.6-stretch | |
environment: | |
# All of your dependencies will be found right here under /code/.go/pkg/mod | |
- GOPATH=/code/.go | |
ports: |
version: '3.7' | |
services: | |
app: | |
command: tail -f /dev/null | |
image: golang:1.12.6-stretch | |
ports: | |
- 8000:8000 | |
volumes: | |
# This is go modules cache, without it you will have to |
### SYMBOLIC LINK FILES | |
# Create a new symbolic link file named MySymLinkFile.txt in C:\Temp which links to $pshome\profile.ps1 | |
cd C:\Temp | |
New-Item -ItemType SymbolicLink -Name MySymLinkFile.txt -Target $pshome\profile.ps1 # File | |
# Target is an alias to the Value parameter | |
# Equivalent to above | |
New-Item -ItemType SymbolicLink -Path C:\Temp -Name MySymLinkFile.txt -Value $pshome\profile.ps1 | |
# Equivalent to above |
# | |
# CORS header support | |
# | |
# One way to use this is by placing it into a file called "cors_support" | |
# under your Nginx configuration directory and placing the following | |
# statement inside your location block(s): | |
# | |
# include cors_support; | |
# | |
# A limitation to this method is that Nginx doesn't currently send headers |