Addon Packager Proxy

Choonstertwo · 01-17-15, 08:21 PM

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.

p3lim · 01-17-15, 09:59 PM

Originally Posted by Choonstertwo

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.

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.

p3lim · 01-17-15, 10:47 PM

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

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

p3lim · 01-18-15, 04:24 AM

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]
2015-01-18T10:09:46.309368+00:00 heroku[api]: Release v2 created by [email protected]
2015-01-18T10:09:51.507285+00:00 heroku[api]: Set GIST_ID, SECRET_KEY, WOWI_USERNAME, WOWI_PASSWORD, QUERY_MAX_ATTEMPTS, QUERY_DELAY_SECONDS config vars by [email protected]
2015-01-18T10:09:51.507285+00:00 heroku[api]: Release v3 created by [email protected]
2015-01-18T10:09:54.990365+00:00 heroku[api]: Add papertrail:choklad add-on by [email protected]
2015-01-18T10:09:54.990365+00:00 heroku[api]: Release v4 created by [email protected]
2015-01-18T10:10:45.757870+00:00 heroku[api]: Scale to web=1 by [email protected]
2015-01-18T10:10:45.865426+00:00 heroku[api]: Release v5 created by [email protected]
2015-01-18T10:10:45.865426+00:00 heroku[api]: Deploy 44c533d by [email protected]
2015-01-18T10:10:48.385404+00:00 heroku[web.1]: Starting process with command `npm start`
2015-01-18T10:10:51.258711+00:00 app[web.1]: > [email protected] start /app
2015-01-18T10:10:51.258673+00:00 app[web.1]: 
2015-01-18T10:10:51.258713+00:00 app[web.1]: > node server.js
2015-01-18T10:10:51.258715+00:00 app[web.1]: 
2015-01-18T10:10:51.986545+00:00 app[web.1]: [LOG] Successfully fetched addon list.
2015-01-18T10:11:22.648216+00:00 app[web.1]: [LOG] Ping: Design for failure.
2015-01-18T10:16:24.491893+00:00 app[web.1]: [LOG] Received event for "oUF_Reputation" version "60000.11-Release".
2015-01-18T10:17:24.503682+00:00 app[web.1]: [LOG] Attempt #1 at querying CurseForge.
2015-01-18T10:17:24.840656+00:00 app[web.1]: [LOG] Found tag link on CurseForge.
2015-01-18T10:17:25.060691+00:00 app[web.1]: [LOG] Found file link on CurseForge.
2015-01-18T10:17:25.132239+00:00 app[web.1]: [LOG] Successfully downloaded file from CurseForge.
2015-01-18T10:17:25.838016+00:00 app[web.1]: [LOG] Successfully authenticated with WowInterface.
2015-01-18T10:17:25.922909+00:00 app[web.1]: [LOG] Found existing addon, previous version: "60000.10-Release".
2015-01-18T10:17:26.705615+00:00 app[web.1]: [LOG] Addon "oUF_Reputation" version "60000.11-Release" was successfully uploaded.

Gethe · 01-18-15, 08:00 PM

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?

jlam · 01-18-15, 08:03 PM

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?

p3lim · 01-18-15, 08:39 PM

Originally Posted by jlam

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.

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

Originally Posted by jlam

Is there a way to just provide the zipfile directly?

No.

Torhal · 01-18-15, 11:58 PM

Originally Posted by jlam

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?

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.

p3lim · 01-18-15, 08:18 PM

Originally Posted by Gethe

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'm gonna make a wiki article about it.

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