Addon Packager Proxy
This is the official topic for the Addon Packager Proxy release tool.
Quote:
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. |
Quote:
|
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: Code:
2015-01-18T10:09:46.308890+00:00 heroku[api]: Enable Logplex by [email protected] |
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?
|
Quote:
Edit: https://github.com/p3lim/addon-packa.../wiki/Updating |
Quote:
Quote:
|
Quote:
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 |
Quote:
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 :)
|
Quote:
Code:
if ( GetLocale() ~= "deDE" ) then 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. |
Quote:
|
Quote:
|
Quote:
The issue ticket on GitHub will be updated whenever something changes on their end. |
0.4.0 is out, two major changes:
|
All times are GMT -6. The time now is 10:59 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI