I see there is an option to specify an external repository for a project. However, I can't find any information in the knowledge base, or anywhere else, about what this feature actually does.
Obviously it is to specify the URL of a repository on another site, but I'd like to know why I would want to do this. Does it just show the URL when someone clicks on my project page's Repository tab? Does it connect my off-site repository to the CurseForge packager somehow?
from what i can tell, it allows you to use an offsite repo with CF packager. Other than that you retain all the same features of a project (comments, tracker, planning, ect)
I see there is an option to specify an external repository for a project. However, I can't find any information in the knowledge base, or anywhere else, about what this feature actually does.
Obviously it is to specify the URL of a repository on another site, but I'd like to know why I would want to do this. Does it just show the URL when someone clicks on my project page's Repository tab? Does it connect my off-site repository to the CurseForge packager somehow?
It makes the wowace repo "sync" with the specified repo URL.
Lets say you do your development on wowinterface's SVN, you can specify that SVN as the external repo, and have wowace "svn checkout" on a daily basis automatically from that external repo. New zips are then packaged by the wowace packager and synced to Curse if there are new commits.
AFAIK this feature is also locked down and requires an admin to approve any changes to the external repo URL. It bypasses all the security precommit hooks so usage of it is restricted to only trusted authors with secure svn repos.
AFAIK this feature is also locked down and requires an admin to approve any changes to the external repo URL. It bypasses all the security precommit hooks so usage of it is restricted to only trusted authors with secure svn repos.
Note that I said admin, not moderator.
It bypasses the hooks, but the files are put into the queue for manual moderation.
Basically it saves you the step in uploading the file from a remote repo.
Obviously it is to specify the URL of a repository on another site, but I'd like to know why I would want to do this. Does it just show the URL when someone clicks on my project page's Repository tab? Does it connect my off-site repository to the CurseForge packager somehow?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt makes the wowace repo "sync" with the specified repo URL.
Lets say you do your development on wowinterface's SVN, you can specify that SVN as the external repo, and have wowace "svn checkout" on a daily basis automatically from that external repo. New zips are then packaged by the wowace packager and synced to Curse if there are new commits.
Cladhaire uses this to distribute some of his addons on wowace/curse, such as http://wow.curseforge.com/addons/tomtom/repositories/mainline/
Note that I said admin, not moderator.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's not well documented, as you've pointed out.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt bypasses the hooks, but the files are put into the queue for manual moderation.
Basically it saves you the step in uploading the file from a remote repo.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThen you can push to both repo:
I think you can even have only one command to push using git aliases.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium