~speguero/powerpkg

ea16aebc8db22b25b7fdb6676544594597aca901 — Steven Peguero 4 years ago 10ff79b
Retire project

- Added appropriate badges to README.
- Updated README header for improved wording.
- Updated LICENSE copyright.

I will never forget working on this project late at night from coffee shops and
restaurants in Cambridge, Massachusetts back in the mid-2010s, all in preparation
for a package hosting migration project at work. Thanks for the memories,
powerpkg!
3 files changed, 7 insertions(+), 4 deletions(-)

M LICENSE
M README.md
A badge/project_status.svg
M LICENSE => LICENSE +1 -1
@@ 1,6 1,6 @@
The MIT License (MIT)

Copyright (c) 2015-2017 Steven Peguero
Copyright (c) 2015-2020 Steven Peguero

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal

M README.md => README.md +5 -3
@@ 1,10 1,12 @@
# powerpkg

![Header](/readme/header.gif)
![[Project Status: Retired]](/badge/project_status.svg)

`powerpkg` is a Windows-focused script that provides IT departments a standard framework for unattended software deployment packaging from within a corporate network.
![](/readme/header.gif)

Similar to Ansible and its playbook file functionality, `powerpkg` is accompanied and leveraged by a [configuration file](#package-file-packagexml) that can contain the necessary commands and verification processes to build a package and guarantee a seamless deployment to an end-user's workstation via a company's distribution tool of choice, whether it's Microsoft SCCM or Ivanti/LANDesk.
`powerpkg` is a portable package deployment orchestrator that allows Windows administrators to orchestrate software package installations with specific rules and exceptions directly from a target machine.

Similar to Ansible and its playbook functionality, `powerpkg` is controlled by a [configuration file](#package-file-packagexml) that can contain the necessary rules and exceptions to build a package and guarantee a seamless package deployment to an end-user machine via a company's distribution tool of choice, whether that choice is Microsoft SCCM or Ivanti/LANDesk.

*This project was proudly written in PowerShell.*


A badge/project_status.svg => badge/project_status.svg +1 -0
@@ 0,0 1,1 @@
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="134" height="20"><linearGradient id="b" x2="0" y2="100%"><stop offset="0" stop-color="#bbb" stop-opacity=".1"/><stop offset="1" stop-opacity=".1"/></linearGradient><clipPath id="a"><rect width="134" height="20" rx="3" fill="#fff"/></clipPath><g clip-path="url(#a)"><path fill="#555" d="M0 0h87v20H0z"/><path fill="#e05d44" d="M87 0h47v20H87z"/><path fill="url(#b)" d="M0 0h134v20H0z"/></g><g fill="#fff" text-anchor="middle" font-family="DejaVu Sans,Verdana,Geneva,sans-serif" font-size="110"> <text x="445" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="770">project status</text><text x="445" y="140" transform="scale(.1)" textLength="770">project status</text><text x="1095" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="370">retired</text><text x="1095" y="140" transform="scale(.1)" textLength="370">retired</text></g> </svg>
\ No newline at end of file