Developer forum

Re: [midgard-dev] Distribute JCR schemas by default

Henri Bergius — Fri, 13 Jan 2012 23:55:06 +0000

+1, makes life easier when we want to support NoCR and other interfaces besides PHPCR. On Jan 12, 2012 2:24 AM, "Piotr Pokora" piotrek.pokora@gmail.com wrote:

Hi!

I created a ticket for this proposal: https://github.com/midgardproject/midgard-core/issues/137

I think we should include these schemas as default ones.

Piotras
dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Distribute JCR schemas by default

Piotr Pokora — Thu, 12 Jan 2012 10:20:11 +0000

Hi!

I created a ticket for this proposal: https://github.com/midgardproject/midgard-core/issues/137

I think we should include these schemas as default ones.

Piotras

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Midgard2 now works on PHP 5.4

Henri Bergius — Wed, 28 Dec 2011 10:35:08 +0000

Hi,

Great news! Piotras got PHP 5.4 working with the Midgard2 extension (in ratatoskr branch). Seems we get quite a nice boost:

PHPCR-ODM tests on PHP 5.3 and Midgard2: Memory: 83.50Mb

PHPCR-ODM tests on PHP 5.4 and Midgard2: Memory: 61.50Mb

So about one fourth less memory usage. Not bad :-)

Note that this also puts us very close to the Jackalope PHPCR provider (which uses 58.25Mb of memory for the same tests). But with Jackalope you also have the Jackrabbit Java process running, while Midgard2 keeps everything inside PHP.

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Jabber: henri.bergius@gmail.com Microblogs: @bergie

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Looking plugin into labtech

Marko Sykes — Tue, 27 Dec 2011 03:50:09 +0000

HI list looking for someone to make a plugin to labtech software RMM.

http://www.labtechsoftware.com

http://www.labtechsoftware.com/component/k2/itemlist/category/339-4z-reference.html

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Midgard2 PHPCR provider is now 1.0

Henri Bergius — Fri, 23 Dec 2011 09:40:24 +0000

Hi,

I'm happy to announce that we were able to release the first stable version of the Midgard2 PHPCR provider yesterday: http://packagist.org/packages/midgard/phpcr

Simply put, PHPCR is the future of Midgard's PHP API. Instead of having our own repository APIs, we follow the well-documented and tested PHP Content Repository specification. This allows much better compatibility with other projects, and for example the possibility to choose whether to store contents in Midgard or Apache Jackrabbit on per-deployment basis. This obviously doesn't mean that the current Midgard2 API is going away, but just that there is something better and more compatible available on top of that.

PHPCR provides a nice set of capabilities that are either similar to, or surpass the traditional Midgard features: * Your content model is constructed out of a tree of Nodes that can contain other Nodes or Properties * Properties can be of many different types, including the typical strings and floats, but also binaries (similar to our blobs) and dates * Properties can be multivalued (think of multiple images in same property, or a person having multiple emails) * Queries can be either constructed with Query Object Model or SQL2 (http://docs.jboss.org/modeshape/latest/manuals/reference/html/jcr-query-and-search.html#jcr-sql2-query-language) * Queries support tree constraints (ISDESCENDANTNODE, ISCHILDNODE) and joins * Content can be exported and imported via a standard XML format * There is a comprehensive Node Type system that allows you to define your content model. The full definitions can be read and introspected via PHP * Nodes also support mixins, allowing you to add per-object metadata * There are also the unstructured nodes (nt:unstructured) for cases where you don't want to have constraints on what to store and how

On top of PHPCR, there is also a Doctrine ODM that the Midgard2 provider also supports. That gives you more capabilities, like: * More traditional object access with getters and setters to the repository (https://github.com/doctrine/phpcr-odm#readme) * Multilingual content storage (http://blog.liip.ch/archive/2011/12/18/multilanguage-support-for-doctrine-phpcr-odm.html)

More about PHPCR: http://phpcr.github.com/

Some code examples: https://github.com/bergie/phpcr-midgard2/tree/master/examples

You can see Midgard's test status for both SQLite and MySQL storage back-ends in our Continuous Integration environment: http://travis-ci.org/#!/bergie/phpcr-midgard2

Once you have Midgard2 and our PHP extension available, installation is easy. Add a composer.json file into the root folder of your project: "require": { "midgard/phpcr": ">=1.0" }

Install with Composer: $ wget http://getcomposer.org/composer.phar $ php composer.phar install

Copy MgdSchemas: $ sudo cp vendor/midgard/phpcr/data/share/schema/* /usr/share/midgard2/schema/ $ sudo cp vendor/midgard/phpcr/data/share/views/* /usr/share/midgard2/views/

...and then just start using the repository in your application. PHPCR can obviously be used side-by-side with traditional Midgard2 or other PHP code.

What will happen next: * Support for PHP 5.4 and Postgres (needs work on Midgard2 level) * Performance optimization * Features work, including versioning * More tools for PHPCR. Think of Asgard that would allow you to work with any repositories! * PHPCR support built-in for MidCOM and MVC?

/Bergie

PS. For those interested in PHPCR, there will be a meetup in Paris in January: http://lanyrd.com/2012/phpcr-meetup-paris/

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Jabber: henri.bergius@gmail.com Microblogs: @bergie

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

tip of the day: DM2 schemas vs $this

Eero af Heurlin — Thu, 01 Dec 2011 12:35:11 +0000

See commit http://trac.midgard-project.org/changeset/27082

tl/dr: don't use $this directly, it will break extending and instantiating the schema from elsewhere.

/Rambo

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Re: [midgard-dev] Continuous Integration is here

Ferenc Szekely — Thu, 17 Nov 2011 12:50:06 +0000

Hello,

On 17/11/11 11:48, Henri Bergius wrote:

Hi,

In the last couple of days, I've deployed Continuous Integration for various Midgard libraries. We're using the hosted Travis service for this: http://travis-ci.org/

Just tested it with midgardmvc_core and the help of Bergie. Brilliant.

I am not a big test writer, but I will dedicate time for developing test cases for my components. It will surely save time in the long run. The integration with github is just great.. Spamming #nemein is.. well.. we can think about it :)

I would like to propose the following:

We integrate as many of our components with Travis as possible. This means they need to be installable and testable on their own

The development workflow should change to

Make the necessary changes in your own fork of a component and push there, not to the 'midgardproject' blessed account

See what Travis says of your changes

If a build breaks, the absolute first priority is to fix it. Don't leave red flags!!

When it is green, it should be OK to push to 'midgardproject'

Additional manual testing may be necessary before a release, at least with our current test coverage

Will work for me. I admit that I never ran the php unit tests on midgardmvc_core before my pull requests in the past. With this process I will not be able to skip those tests at all. I hope this will speed getting my changes to upstream ;)

This all should make the Midgard development process smoother, and ensure problems don't slip by accident into releases. Ultimately it should allow us to have a more tight release cycle as maintainers like Piotras have a better picture of the current state and quality of various components.

But for this to work, we really need to ensure our components have adequate tests, and that if builds break they get fixed as soon as possible.

Let's dedicate an upcoming release for tests. Maybe that will motivate us enough to write more tests ;)

/Henri

-ferenc
dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Continuous Integration is here

Henri Bergius — Thu, 17 Nov 2011 09:55:11 +0000

Hi,

In the last couple of days, I've deployed Continuous Integration for various Midgard libraries. We're using the hosted Travis service for this: http://travis-ci.org/ Some CI basics: http://en.wikipedia.org/wiki/Continuous_integration

Travis supports connecting your personal GitHub repositories there, and configuring the continuous integration with two scripts: an installation script, and a test script. Then it gets notified every time you push. Then it builds your project and runs the tests. If the test script returns with code 0, the build is OK, if not, then it failed. Travis will send emails to the committers and notify on the

midgard IRC channel.

Some setup examples:

midgardmvc_core
- config: https://github.com/bergie/midgardmvc_core/blob/master/.travis.yml
- install with Midgard: https://github.com/bergie/midgardmvc_core/blob/master/tests/travis_midgard.sh
- install without Midgard: https://github.com/bergie/midgardmvc_core/blob/master/tests/travis_nomidgard.sh
midgard-php5
- config: https://github.com/bergie/midgard-php5/blob/ratatoskr/.travis.yml
- install: https://github.com/bergie/midgard-php5/blob/ratatoskr/.travis/install.sh
- test: https://github.com/bergie/midgard-php5/blob/ratatoskr/.travis/test.sh

The Travis worker is essentially a clean Ubuntu virtual machine set up just for that test instance. You have root, so quite a lot is possible as part of the setup. Some notes on the PHP environment: http://about.travis-ci.org/docs/user/languages/php/

I would like to propose the following:

We integrate as many of our components with Travis as possible. This means they need to be installable and testable on their own
The development workflow should change to
- Make the necessary changes in your own fork of a component and push there, not to the 'midgardproject' blessed account
- See what Travis says of your changes
- If a build breaks, the absolute first priority is to fix it. Don't leave red flags!!
- When it is green, it should be OK to push to 'midgardproject'
- Additional manual testing may be necessary before a release, at least with our current test coverage

This all should make the Midgard development process smoother, and ensure problems don't slip by accident into releases. Ultimately it should allow us to have a more tight release cycle as maintainers like Piotras have a better picture of the current state and quality of various components.

But for this to work, we really need to ensure our components have adequate tests, and that if builds break they get fixed as soon as possible.

A quick example of CI in practice. I had a pull request from Ferenc. Instead of just merging it to 'midgardproject', I merged it to my private repository and then pushed. Travis sent me an email saying that the build broke: http://travis-ci.org/bergie/midgardmvc_core/builds/315937 I checked the situation and noticed that this was because a test was hardcoded for a particular jQuery version. I fixed the test to be version number agnostic, and pushed again. Now the build succeeded: http://travis-ci.org/bergie/midgardmvc_core/builds/315952 This gave me the confidence to push the changes to 'midgardproject': https://github.com/midgardproject/midgardmvc_core/pull/64

What do you guys think?

/Henri

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Jabber: henri.bergius@gmail.com Microblogs: @bergie

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Re: [midgard-dev] Community analysis of Midgard

Piotr Pokora — Fri, 04 Nov 2011 10:25:06 +0000

Hi!

The new Coral project that aims to produce community analytics of various free software projects just chose Midgard as one of their "reference projects":

Cool! :)

Guys! Let's keep the good work!

Piotras

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev

Community analysis of Midgard

Henri Bergius — Fri, 04 Nov 2011 09:30:14 +0000

Hi,

The new Coral project that aims to produce community analytics of various free software projects just chose Midgard as one of their "reference projects": https://twitter.com/#!/kyyberi/status/132384452826497024

More about Coral: http://www.open-coral.org:1480/

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Jabber: henri.bergius@gmail.com Microblogs: @bergie

dev mailing list dev@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/dev