Psake
common
| Psake | common | |
|---|---|---|
| 5 | 4 | |
| 1,536 | 164 | |
| 0.0% | 2.4% | |
| 0.0 | 9.7 | |
| over 1 year ago | 6 days ago | |
| PowerShell | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Psake
-
Achieving single command Infrastructure deployment using PowerShell DSC.
You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?
- How do you guys make sense of a complex project on GitHub?
-
How do you specify Debug or Release when calling Invoke-psake?
I use the psake PowerShell module to "build" my PowerShell modules. My psakefile.ps1 contains the logic needed to update the manifest with an incremented version, any new function/cmdlet names, and so on. Then it copies everything from .\src\ to .\output\modulename\version. All I do is call Invoke-psake build or Invoke-psake test, and this works great as-is for "pure powershell modules".
-
What build tool(s) do people use for their applications?
I've used psake (powershell+make) https://github.com/psake/psake - the main thing that attracted me to this was that it wasn't an XML based system (Nant/MSbuild), and it handled task prerequisites very nicely. While some devs find powershell a bit of a pain to learn, they generally become useful very quickly, and I think it's useful to be able to do some level of powershelling anyway.
-
pake: Just another Make but with Powershell
GitHub - psake/psake: A build automation tool written in PowerShell
common
-
Improve Jupyter Notebook Reruns by Caching Cells
Dockerfile and Containerfile also cache outputs as layers.
`docker build --layers` is the default: https://docs.podman.io/en/latest/markdown/podman-build.1.htm...
container/common//docs/Containerfile.5.md: https://github.com/containers/common/blob/main/docs/Containe...
-
Is it possible to generate the default `containers.conf`?
https://github.com/containers/common/blob/main/pkg/config/containers.conf ? But it's empty save for the comments, since it's supposed to be customized by your distribution. Still, starting point.
-
buildah/podman overlay on build context
Argh, the fix is rw on the mount line, not ro=false. This is missing from the documentation (https://github.com/containers/common/blob/main/docs/Containerfile.5.md).
-
File contents intermediate layers from building
A good resource to start is the Containerfile man page.
What are some alternatives?
Cake - :cake: Cake (C# Make) is a cross platform build automation system.
metatar - Manipulate tar file metadata, list tar files or convert tar to cpio. For some projects, this can replace fakeroot and cpio, when creating an initrd image that is compatible with the Linux kernel. Used in production in at least one company.
Invoke-Build - Build Automation in PowerShell
FlubuCore - A cross platform build and deployment automation system for building projects and executing deployment scripts using C# code.
MSBuild - The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.
NUKE - 🏗 The AKEless Build System for C#/.NET
FAKE - FAKE - F# Make
CS Make - Sake Build
sake - :robot: sake is a task runner for local and remote hosts