New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared Scenarios #384
Comments
Maybe github gists? I'm thinking of allowing automatic import and export of gists. |
Also, awesome Scenario! |
I like the idea of being able to publish/load scenarios from anywhere public, but I also like the idea of having a 'central' place that we can find them (yet still have individual control over keeping it updated) Gist is definitely one option, but I would almost be inclined to have a full git repo that people can submit their scenarios to so there is one central location to find them (think homebrew formulae, etc) If you did go the route of having a 'scenario directory' type repo, I think having the ability to specify (if it doesn't already) who made the scenario, their url/website/email/etc, and some other stats like that. I would also see it as being a convenient storage place, but not necessarily something we would have to clone to access the scenarios in (seems like there could be a lot of potential for bloat if you only wanted a couple of scenarios, yet that being said each scenario is probably pretty small, so may not actually matter that much?) |
https://github.com/caskroom/homebrew-cask also does this. For now we could share raw links to gists and pastebins (like http://pastebin.com/raw.php?i=jts6rHyK). If someone wants to make a directory site that hosts Scenarios with tags and search and stuff, that'd be amazing. And I'll work on adding author information to the exports. |
So I don't currently have my server running huginn opened to the world. I see you can share scenarios via a .json file. Is there a place we could share these? Maybe a wiki page? Just a thought.
Also. Free and Mistake Game Deal Notifier Scenario.
The text was updated successfully, but these errors were encountered: