recentpopularlog in


« earlier   
intoli/exodus: Painless relocation of Linux binaries–and all of their dependencies–without containers.
Painless relocation of Linux binaries–and all of their dependencies–without containers. - intoli/exodus
docker  dependencies  dependency  library  libraries  shared-libraries  andrew 
12 days ago by nharbour
Modules · golang/go Wiki · GitHub
A brief tour of other common functionality you might use: (go list -m all) View final versions that will be used in a build for all direct and indirect dependencies. (go list -u -m all) View available minor and patch upgrades for all direct and indirect dependencies. (go get -u) or (go get -u=patch) Update all direct and indirect dependencies to latest minor or patch upgrades. (go build ./...) or (go test ./...) Build or test all packages in the module when run from the module root directory. (go mod tidy) Prune any no-longer-needed dependencies from go.mod and add any dependencies needed for other combinations of OS, architecture, and build tags. (replace directive or gohack) Use a fork, local copy or exact version of a dependency. (go mod vendor) Optional step to create a vendor directory.
golang  go  modules  dependencies 
14 days ago by dlkinney
FFmpeg, SOX, Pandoc and RSVG for AWS Lambda
OK-ish way to add dependencies to your Lambda containers:
The basic AWS Lambda container is quite constrained, and until recently it was relatively difficult to include additional binaries into Lambda functions. Lambda Layers make that easy. A Layer is a common piece of code that is attached to your Lambda runtime in the /opt directory. You can reuse it in many functions, and deploy it only once. Individual functions do not need to include the layer code in their deployment packages, which means that the resulting functions are smaller and deploy faster. For example, at MindMup, we use Pandoc to convert markdown files into Word documents. The actual lambda function code is only a few dozen lines of JavaScript, but before layers, each deployment of the function had to include the whole Pandoc binary, larger than 100 MB. With a layer, we can publish Pandoc only once, so we use significantly less overall space for Lambda function versions. Each code change now requires just a quick redeployment.
serverless  lambda  dependencies  deployment  packaging  ops 
15 days ago by jm
It's time to use Swift Package Manager - Artsy Engineering
It's been three years, and Swift Package Manager (SPM) is at a point where it can be useful for iOS
projects. It'll take a bit of sacrifice and a l...
swift  dependencies 
15 days ago by nanoxd
Why You Should Consider hapi – hueniverse
When starting a new web application, your first decision is the platform: node, Go, Rails, etc. Your second decision is the framework. When it comes to node, there are plenty of great frameworks to…
nodejs  javascript  dependencies 
4 weeks ago by mattgrayson

Copy this bookmark:

to read