Hey folks,
The CurseForge dev team is preparing some of the bigger, final touches on what will become the new WoW CurseForge and WowAce sites, and they're hoping to have everything wrapped up by the end of the month. When these new sites go live, there will be some noticeable improvements for developers of WoW projects.
The old, unreliable, and unpredictable Packager is being retired -- its replacement will be many times faster, much more resilient, and able to package multiple projects simultaneously. Additionally, the new Packager will be capable of operating directly from repositories on GitHub and Bitbucket via webhooks.
The Localization System is also being heavily upgraded, including a new UI to better serve translators -- it will be available for all projects. There's also no longer going to be a requirement to use a Version Control System to take advantage of this extremely useful feature. The new behavior is to have the localizations injected into any uploaded or packaged file for projects which have the feature enabled.
We’re all very excited to be able to announce this, and look forward to many more improvements in the future. Thanks for all the support.
Cheers,
Torhal and the entire CurseForge team
EDIT: When the transition occurs, repositories will be offline for roughly 24 hours. Normal file uploads will still be accessible.
-
View User Profile
-
Send Message
Posted Nov 18, 2016How annoying. :(
I guess this means I won't be maintaining repos on Curse for my libraries anymore. I'm not going to dig through my password vault and copy/paste my (long, random, secure) password into the terminal every time I want to push commits.
The biggest issue with this -- and the main reason I maintained a duplicate repo on Curse -- is that when addons embed my library from GitHub, I don't get any author rewards credit, like I do if they embed it from CurseForge. (I would if they also added my library to the "tools-used" section of their .pkgmeta, but that's extra work that doesn't benefit them, so they're probably not going to do it.)
Also, the API for uploading files, fetching localization data, etc. from a script seems to be broken, and there's no information about this in the knowledge base (which seems to have had most of its articles removed) or on the "docs" page. Is there no longer an API? If there is, where is the documentation about the changes so I can update my scripts to work?
-
View User Profile
-
Send Message
Posted Nov 5, 2016Woot! Fingers crossed for a smooth transition!
-
View User Profile
-
Send Message
Posted Nov 5, 2016Looking forward to it!