Package to publish to the server???

Sep 20, 2010 at 8:23 PM

The think I like about GEMS is the ability to publish from the tool.  What if any thought has been put into a publish or push feature?  My current feed automation is not a scalable solution for a community supported feed.  I am thinking of a users registering for a key and than using that key when they publish or push a package.  IF that package name is already assigned to another user than they cannot publish a package with a duplicate name.  Thoughts?

Sep 20, 2010 at 8:26 PM
Yes - this is perhaps the "killer" feature of gems. Ease of getting your stuff up to the server.
It asks for a username/password the first time and stores it from then on.
 
You can also add/remove other "owners" so they can also publish the same gem.
____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder
Sep 20, 2010 at 8:28 PM

Note that the plan is to later switch to a fancy feed server with a web UI and all, so the current feed is definitely temporary.

But we should indeed explorer the idea of publishing from the cmd line (though probably not in the first release).  In such a model, I assume the feed server always hosts the package itself, rather than point to an external package?

Coordinator
Sep 20, 2010 at 8:36 PM

Yeah, we'll have to loop in Brad Millington and Louis DeJardin (aka Mr. Spark) on that discussion. Brad is driving the fancy schmancy gallery/feed implementation. The idea was to support AtomPub for publishing packages. In our case, I think the nupack.exe should be the way to do that.

Sep 20, 2010 at 8:37 PM
davidebb wrote:

In such a model, I assume the feed server always hosts the package itself, rather than point to an external package? 

Yes, I think the big benifit here is to make it really easy for someone to share their pacakge. Push it up to the server and store it there. That way the author can concentrate on the value add of creating the package, and forget about the logistics.

Sep 20, 2010 at 8:42 PM

As long as the publishing is part of the main packaging tool and the destination is overridable, that works for me.

Sep 20, 2010 at 8:49 PM
Just remember that our requirements are for history. All versions of a package should be available in the feed. This may be different than what they would be doing with orchard. Or maybe not. :D
____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder
Coordinator
Sep 20, 2010 at 8:53 PM

Yep! All on the same page.

Sep 21, 2010 at 1:54 PM

I would really like to see the publishing infrastructure put into the server project in this repository.  The gallery could be written on top of it, but I think people like myself, representing enterprises could use a drop in package repository that supports publishing. IMHO