El 02/09/16 a las 14:15, Michael Hall escribió:
On 09/02/2016 01:06 PM, Evan Dandrea wrote:
On Fri, 2 Sep 2016 at 04:30 Mark Shuttleworth <[email protected]
<mailto:[email protected]>> wrote:
Remember they can also build postgres INTO their own snap (and it
actually might be worth exporting a shared pg part so people can do
that trivially).
And this is exactly what happened with Mongo. Gustavo wrote a Mongo
snap. The Rocket.Chat guys picked it up and used it as a part. Then we
pushed it to the parts server (`snapcraft search mongodb`) so others can
benefit.
+1 to a postgres part.
Yet another option would be to use the new content interface to build
postgresql snap that can share it's binaries and libraries into your
snap, so you can call them to setup and manage a local database in your
own application's directories.
Yes, this is indeed an option for snaps from the same publisher. But you
are now discussing inter snap communication and while the content
interface seems good in the beginning, some things might be better
served by using an interface specific to databases (as this is the topic
at hand).
--
Snapcraft mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
