Make a cookie file to authenticate with, you’ll only need to do this until the cookie expires:
(*ZAM is working on a public oauth endpoint so in the future you’ll be able to get an access token. Right now you’ll need to get the auth cookies from our local login system.)
To use P3lim’s AddOn Packager Proxy: please see this thread.
Auto-pull from Curse:
You will need to:
If you don't already have the addon in question on WoWInterface - upload an old version of your addon to here, not the most recent version. Put in your description, screenshots, etc. If you already have the addon hosted here, skip to the next step.
Once you've uploaded it, give me a link to it here and on Curse, please.
Then I tick a couple boxes and it should grab the most recent from Curse, and from then on will auto-magically pull from Curse any time you update your addon there.
In addition you will need to provide written confirmation that we are pulling from Curse at your behest, via posting in this thread.
So - you guys killed the old, awesome, addon updaters from the past from pulling from your site, and now you're ok with pulling from Curse?
So - you guys killed the old, awesome, addon updaters from the past from pulling from your site, and now you're ok with pulling from Curse?
Funny how things work.
In the past, when updating the curse svn or github etc., you grapped the newest version from there and uploaded it here.
So technically, it's the same, just automated.
Is there a method to query which wowi-svn is connected to a project?
So that I could query the addon-list, query the addons for related svn, check out from svn , build zip and finally upload to wowi (and curse)?
__________________
The cataclysm broke the world ... and the pandas could not fix it!