Addon Packager Proxy
 

This is the official topic for the Addon Packager Proxy release tool.

For a more in-depth explanation and usage guide, see the readme on GitHub:
https://github.com/p3lim/addon-packager-proxy


This topic will be used for feedback and suggestions, all bug reports should be submitted to the issue
tracker on Github: https://github.com/p3lim/addon-packager-proxy/issues.

Enjoy.

Notice:
This application is no longer in active development, I strongly advice using an alternative solution (such as BigWigs' packager, which I've written a guide for)

This looks awesome. I already use Git with GitHub/CurseForge and tag each release, so this should fit in well with my existing process.

I've simplified the process quite a bit in v0.2.0, you no longer need to fork the repository, and you no longer have to do changes to core files for the application.

You now "deploy" the application directly to Heroku, setting the needed variables in a setup page.
The addon information will now be stored in a gist you create, the app will fetch that on every run.

I plan on adding a complete setup wizard to the app, removing the last few manual steps during the setup and letting the app do all the work.

I was getting 404 errors from the AddOn repository's webhook until I changed the URL from https://<APP_NAME>.herokuapp.com/webhook to https://<APP_NAME>.herokuapp.com/. Once I changed the URL and redelivered the create event, it found the packaged AddOn and uploaded it to WoWI without issue.

This is much better than manually uploading to WoWI and dealing with the BBCode changelog.

Yeah that was one of the changes I did earlier today/yesterday. I updated the wiki to reflect that, but since this is still alpha quality, make sure you check the commit log before updating.

Spent some time improving the markdown to bbcode conversion, pretty much untested right now.

https://github.com/p3lim/addon-packa...80ff4f23466acb

And there goes my first successful actual release (excluding testing), also showcasing the new markdown to bbcode support.

My full logs from deploy to successful upload for reference:

I have not used Heroku, so please excuse my ignorance. How would I handle updating the app to a more recent version of your repo?

I've not looked at the project code yet, but from the description I'm uneasy with using Curse's download bandwidth as part of a project to upload to WowInterface. Is there a way to just provide the zipfile directly?

I'm gonna make a wiki article about it.

Edit: https://github.com/p3lim/addon-packa.../wiki/Updating

I've got approval from Curse admins, it should not be a problem.

No.

Many authors, myself included, do this manually every time they make a release; let the CurseForge packager do its thing, navigate to the download for the new file, download it, navigate to the project management page on WoWInterface, then upload it. This merely automates what's already being done.

EDIT: This would be a completely different story were the utility made for end-users. In that case, bandwidth would be a definite concern.

Made some changes to how the app handles changelogs in 0.3.4.

Short version: They must be enabled per-addon in the addon list (the gist).

Long version: https://github.com/p3lim/addon-packa...wiki/Changelog

I know that from somewhere! I wish both sites just would have the packaging, changelog creation and also the translation, then I could just add both endpoints into my git config and push once release on both.

And this one sounds good, but as long it requires to make another repo on github, I am not bothered to check it out.

Dorwido, use our API instead: http://www.wowinterface.com/forums/s...ad.php?t=51835 :)

Saw that one too, even its only a quick documentation how to use it, I guess setting it up to easy push a new release takes some time too, I would really love to see here a packager too and allow the same tags as on curseforge (dunno if that would be a legal issue) for example for translation I use the following:

It fills the localisation automatic for all languages and the debug thing is removed on pushing and I do use it to not get lua errors in my developing enviorment.

Kinda could do then an
git commit
git tag
git push

And it appears on both sites and only need to go on the site for changing descriptions, that would save alot of time.

Currently it is to do the git stuff on curseforge, then download the file there, upload it here, copy&paste the changelog from curseforge and change the formatting, enter the new version number and copy&paste the description if any change and then upload here.

And the api here to use still need to know all those stuff have a local zip etc, that data need to be scraped somewhere as well?

Its late maybe I oversee something.

See this: https://github.com/p3lim/addon-packager-proxy/issues/4

any news about this one?

It's up to CurseForge, I requested it as a feature to one of their developers/admins, other than that I don't know.
The issue ticket on GitHub will be updated whenever something changes on their end.

0.4.0 is out, two major changes:

• Changelogs are pulled directly from the repository, not from the packaged zip.
  • This means that you don't have to bring the changelog along if you don't want to.
• Github can be considered optional, but the app would be semi-automatic. See issue #4.

Made a powershell script (sorry linux users) for easy force updating:
https://gist.github.com/p3lim/3385bc34b82a7f1cd0cc

Sorry if this is a nub question, but it's requiring me to put my credit card information in to use this app on Heroku. Will I be charged for using this app? Or is it basically just there to stay on file and I shouldn't get charged (using only this app)?

Heroku does indeed require a credit card when registering, but don't worry, unless you're making a large application, you won't ever get charged for anything.
They charge for something called "dynos", which are basically instances of virtual machines, and you can increase the amount and power for each application you've got.

This app is very small, it will never require anything serious, so go with the default choice when creating an app (ONE dyno, 1X power), as seen in this screenshot, and this setup is completely free, no hidden fees or anything:

Okay thanks!

Edit: Nevermind, I think I derped.

The wait time is in intervals, you can configure how many times it should check, and how often (with limits of course).

I'm having trouble getting it to even check at all. I honestly don't know much about any of this at all, so I wouldn't be surprised if it's a silly mistake.

Here is my log:
I kind of messed around with changing some of the keys trying to see if that's what was messing it up, but nothing seemed to help. The last I have it is set as default values. Also I couldn't get it to do anything at first until I realized the thing about taking the "webhook" out of the url for the app. I saw you mentioned you had updated that, but I don't think it was updated in the wiki under the addon list page (which is where I found the instructions).

Anyway, I kind of left it alone for a while so I could make some changes to my addon and then came back to try again when I finished. I've tried resending the webhook several times and it still won't do anything. I see in your log it starts doing it's business but the most it's wanting to do so far is just get the addon list.

Here is my addon.js:

I fixed the old details in the wiki, thanks for letting me know.
Also, you should use a different name for the app on Heroku, as suggested in the wiki.

Edit: sorted out in private messages, it was just confusion around outdated documentation on the wiki.

It's fine I made my own tool for this. Though it's incredibly buggy and I'm too ashamed of my code to post it on github.

Sometimes I hate myself for being a perfectionist >.>

Unfortunately, I can't seem to get the script working, it always fails right after WoWI authentication:

Any idea what's going wrong?

Seems like an issue with the WoWInterface API, I'll see if I can get dolby to take a look at it.

Try forcing it in a little, see this on how to:
https://github.com/p3lim/addon-packa...mment-74553204

403 is thrown if the user is not authenticated or the AddOn is disabled/banned. There is a text message that is given with the 403 that will distinguish the two. Looking at the AddOn its not disabled or banned so I'm sure there is an issue with ckaotik's authentication.

But then, why did the previous call return "Successfully authenticated with WowInterface."?
The API url works fine when I open it in the browser while logged in, but the script should do the same thing as it stores the cookie?

Edit: The 403 error reported something along the lines of "You must be logged in to use this API"

If the login is successful then to me that says something isn't capturing and storing the cookie OR isn't passing it on to wowi when making api calls?

Are you able to interact with the API via curl?
http://www.wowinterface.com/forums/s...ad.php?t=51835

I just tested via curl and haven't had any issues.

It is storing the cookie correctly, which is purged automatically when the heroku server node goes to sleep.
I'll see if I can add a manual purge function, but for now you can manually set the node to sleep if you want to.

Did you try a forced update by the way?

0.5.0 is out, changes:

• Cloned repositories should now merge instead of override, this should resolve some issues when updating an addon multiple times before the server sleeps.
• Compatible version flags on wowinterface are now updated automatically, based on the interface version in the toc file.
  • Example: If your interface version is 60200 it should be marked as compatible with 6.2 on wowinterface.
• Added a few more debugging messages

I'm getting a "Fetching failed with status 128" error when forcing an update on one of my AddOns.

Full log:AddOn Packager Proxy: 0.5.1
addons.json: https://gist.github.com/Choonster/2ce79d3eb7adee8bdb2d

Do you know what the issue might be?

I'll take a look at it tomorrow if I get a chance.

Yup, tried that too, but without success. The work order gets triggered, but the error remains.

Unfortunately, I'm still running into the same issue even on 0.5.1. Could this be because of my Heroku setup? I'm using the new "Free" dyno on EU servers.

0.5.2 is out, changes:

• Dependencies fixed (was fixed in 0.5.1 but forgot to make a changelog).
• Added a way to force update the addon list
  • your-app.herokuapp.com/updatelist
• Fixed issues with fetching and merging
• Replaced deprecated methods usage

It looks like this requirement could be avoided if you (p3lim) removed the dependency on the Papertrail logging app/plugin.

Papertrail is not a requirement, and the version I've added as an option is free anyways.

Even if I removed it as an option, Heroku still requires any user to register a credit card.

"Credit card information is not required for free apps without add-ons. It becomes a requirement once you wish to own more than 5 apps at a time, or to use add-ons other than postgresql:dev or pgbackups:plus –– even if the add-ons are free."

It doesn't matter that Papertrail is free; its mere presence triggers the verification requirement. It didn't appear to be optional, or removable, on the deployment screen, which is where I stopped since I'm not interested in giving an entity that claims it won't charge me any money information that has no purpose other than charging me money.

They must have changed their policy, when I was developing this they required a credit card just to make an app, no matter if it was free or not.

Considering that, I'm gonna remove Papertrail from the package. It's still nice to have for debugging, although Heroku's CLI can be used just as well:

0.5.3 is out, changes:

• Removed the Papertrail addon bundle
  • This allows the app to be installed without requiring a credit card

Last night I deployed, followed the setup instructions, added the webhooks, made a tag... and of course the CurseForge packager was AFK, so I wasn't able to see if it worked. Today there's finally a package on CurseForge, so I attempted to force an update, and got this error message:
Repository "BetterBattlePetTooltip" is not tracked.

...so something isn't set up correctly. Here's my addons.json gist:
https://gist.github.com/Phanx/ce8f911fc73b67363270

The GitHub repo for the addon in question is here:
https://github.com/Phanx/BetterBattlePetTooltip

The webhook is set to "create and push", and I've triple-checked that the Curse project name and WoWI ID are correct in the gist. Where did I screw up?

You can force-update the list, it usually fixes those issues.
https://secret-journey-8122.herokuapp.com/updatelist

You also have some errors in your list:
https://gist.github.com/Phanx/ce8f91...json-L187-L215

Thanks, seems to be working now. The "updatelist" link gave this error:
...but the forced-update URL for the addon correctly uploaded to WoWI.

Fixed: https://github.com/p3lim/addon-packa...84618b35472a47

New version out for that; 0.5.4

.pkgmeta
 

Atm my addon is hosted on Curseforge using their packager. I would prefer to use this method to host on github and release on both wowi and curse at the same time.
But I wonder how I replicate the functionality of the .pkgmeta?
My current pkgmeta looks like this.

For this tool to work (in it's current implementation) you need to use the repository on both GitHub and CurseForge.

Well that is fine. but how do I do with my externals? Should I change them from externals and just embed them manually or how should I go about it?

The CurseForge packager can't deal with submodules/externals, you would still need that metadata file.

HTTP is (apparently) no longer supported on Curse; I've submitted a pull request on GitHub switching the Curse URLs over to HTTPS.

0.6.0 is out, changes:

• Now using API tokens for WoWInterface authentication, generate one here.
• CurseForge is now only accepting HTTPS connections (thanks Phanx)

Big thanks to dolby for making this happen!

0.6.1 is out, changes:

• Now using HTTPS to communicate with WoWInterface too.

CurseForge has been redesigned, I can not guarantee this project will work until I've had a look at it.

0.7.0 is out, changes:

• Fixed warnings being thrown for positive responses from WoWInterface API
• Use the new compatibility API from WoWInterface (thanks to dolby!)
• Updated parsing of CurseForge and their website updates

APP will now flag the correct compatible game versions, first by checking the interface version in the toc file, with a fallback to the default (latest) game version.

Forgot to update here for the last few versions, but here are the changes:

0.7.1 is out, changes:

• Fixed changelog not being pushed correctly.

0.7.2 is out, changes:

• Fixed interface version detection

0.7.3 is out, changes:

• Fixed force updating
• Fixed CurseForge parsing
• Added support for WowAce as a fallback when project was not found on CurseForge
• Updated entire stack to latest versions

Awesome tool, really.
I was wondering if would be possibile to polish a bit the answers for updatelist and force.

• updatelist:

  I noted that if the gist contain a broken json, no warning is given.
  Maybe an answer with
  status: (success:failure)
  data: addons.json content
  would be nice

  force:

  status: (success/failure) message: descriptive result (could be updated to version x.x.x)

Good suggestions, however I've personally switched to a different system, so this project likely won't see any updates from me in a while, aside from things like bugfixes and PRs.

The system I'm using has a detailed guide (written by me) here:
http://www.wowinterface.com/forums/s...ad.php?t=55801

Advantages are:

• No need to set up a server (Heroku) and keep it up-to-date
• Settings are stored per-project (alike the .pkgmeta), not hidden in settings/gists
• No need to poll CurseForge for updates, which can't be guaranteed
• More widely adopted by larger projects (BigWigs in particular), so it should be considered more stable/long-term available

My guide has a hard dependancy on Git, but the script can just as well be run locally (which is way harder with this proxy project)