[chirp_devel] Windows Server availability

[Patrick Lang]

It sounds like this could be just another post build script that could be run on the same build server. Is that true?

Otherwise I think this could be done as an Azure automation job using the free tier of service. 
https://azure.microsoft.com/en-us/pricing/details/automation/


Cheers,
Patrick ae7pl

Sent from a tiny keyboard

> On Oct 5, 2016, at 3:41 PM, Philip Arola via chirp_devel <chirp_devel at intrepid.danplanet.com> wrote:
> 
> Hello all,
>  
> I have been maintaining the CHIRP installation package for Windows at https://chocolatey.org/packages/chirp.install.  The source files for the package is https://github.com/philiparola/chocolatey-packages.  For those unfamiliar with Chocolatey, it’s basically ‘apt-get’ for Windows.
>  
> So far, I’ve been manually updating packages when there is a new release.  There is an automated method to do this, and CHIRP is one of those few packages that is perfect for this, particularly because you have a download folder called ‘latest’ AND an email notification.  I would set this up in a heartbeat, but alas, I have no Windows Server to run this on, and leaving my desktop on perpetually isn’t the best solution.
>  
> I am unfamiliar with your compilation process and your development process, so excuse the potentially dumb question.  Is there some sort of Windows Server installation dedicated to CHIRP?  It doesn’t even have to be a server, it could be desktop Windows; as long as it is running, connected, and running an application whenever a release is coming up, it will work.  I would need access to the server, or I would have to delegate access to someone else to administrate the Chocolatey package (which I am totally fine with).
>  
> -Philip Arola
> -KG7VAM
> -philiparola at hotmail.com
>  
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20161008/ca3c446f/attachment-0001.html