In case somebody else needs to create a collection of private/shared elements, I discovered that bitbucket offers unlimited private git repositories on their free plan (<= 5 collaborators). This means that I am able to use the seed-element flow to create a repository per element and just change the repository link to point to bitbucket instead of github. The steps to publish the github pages documentation presumably won't work, but as it's a private collection, I'm not bothered.
On Tuesday, July 22, 2014 6:41:13 PM UTC+2, Keith Garrod wrote: > > I am trying to create a collection of elements that can be shared between > multiple private projects. > > I want to include testing (polymer-test-tools) and to use my own > components in Polymer designer. I am finding it challenging to set up a > directory structure which supports private/shared elements and is > consistent with the existing toolset. > > The tooling seems to be geared towards creating a repository for each > element. That's all very well for public elements, but not so great for > private/shared > elements. My private/shared collection will easily exceed 50 elements > (github large plan). Apart from anything else, that's $1/month/element, > which seems like a lot for hosting a few lines of code! > > I do understand that the tooling is nascent, but I am wildly excited about > the potential of Polymer for my project and would really appreciate any > pointers . > > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/0fd70bf6-38b1-42fa-ae00-6680cc417eb1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
