All,
  In a fit of frustration, I wrote a travis-ci script that automatically 
generates a plugin library hosted on github from a repo containing 
plugins.  I think it's a cleaner and simpler way to get started hosting a 
plugin library than anything else I've seen thus far.  I'm looking for 
feedback, both on the instructions and the build process itself.  The repo 
itself is available at https://github.com/mklauber/tw5-plugins-template and 
you should be able to simple fork it to your own repository, follow the 
setup instructions, and start adding plugins to the `plugins` directory.  

I've tried to make the setup as simple as possible, but any suggestions 
would be welcomed.  


This repository is designed to serve as a template for hosting your plugins 
> in a plugin library. Plugins placed in the plugin folder will be hosted on 
> the github pages site for this repository automatically, and commits to the 
> master branch will automatically update the library. This README assumes 
> familiarity with git and github.
> <https://github.com/mklauber/tw5-plugins-template#setup>Setup:
>    
>    - 
>    
>    Setup a github.com account if you do not have one.
>    - 
>    
>    Fork this repository to your own github account.
>    - 
>    
>    In gui/Library.tid replace {GITHUB PAGES URL} with the github pages 
>    url where you're planning to host this. Typically, this is of the form 
> {github 
>    username}.github.io/{repo name}. So for example, if my repository was 
>    available at https://github.com/mklauber/tw5-plugins I would replace 
> {GITHUB 
>    PAGES URL} with mklauber.github.io/tw5-plugins.
>    Commit and push this code to github.com
>    - 
>    
>    Sign into travis-ci.org with your github credentials.
>    - 
>    
>    Enable builds for your forked repository.
>    - 
>    
>    Generate a github token, ala 
>    
> https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/
>  to 
>    allows travis-ci to upload to your github pages.
>    - 
>    
>    Go to settings for your travis-ci job and add an environment variable 
>    with the name GITHUB_TOKEN and the set the value to the github token 
>    string from the previous step.
>    - 
>    
>    At this point, travis should attempt to build and publish your 
>    plugins. If all goes well, check your library at {github 
>    username}.github.io/{repo name}.
>    
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/30d71016-8f1b-4520-b96d-22f30703b645%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to