Open Invoicing PSI

Why should PSI be developed with PHP? This question, many netizens have asked me, today writes a blog to say this course.

Generally speaking, the main reason is: Save money.

2011 I launched an open source project: CRM8000, then host on the Teamhost, Teamhost later evolved see here: http://segmentfault.com/a/1190000000374128.

So, Crm8000@qq.com became my registered email, followed by.

CRM8000 was included in the OSC time is: April 12, 2011.

This version of CRM8000, I wrote with Java + GWT + MySQL.

After that, I moved CRM8000 to www.tigris.org, I can not access it now, it seems to be the wall, with the memory of my Project URL is: http://abc.tigris.org, I can't verify today.

Then, it should be about 2012 years, I use Microsoft's full range of technology: ASP. NET + SQL Server began rewriting crm8000,host on http://www.codeplex.com, but you do not search, I have completely deleted it last year.

Then, in December 2014, I decided to rewrite CRM8000 with Grails. This is a grails rewrite of the CRM8000, now host on the OSC:.

As I wrote, I deployed CRM8000 to the demo platform provided by the OSC, and I was dumbfounded: grails applications require a lot of memory. At this point, I faced two choices: spend money on upgrading PAAs memory, or give up.

A few days a tangled, decided to give up, and then rewrite.

Through this, I have a good liking for grails, so I did not delete the CRM8000 on the OSC project, but to re-project, this is the PSI.

PSI Project I learned my lesson, starting with the first line of code, I tested it on the PAAs and then made my code compatible with PAAs.

The process is finished, it is a point of the PSI Project harvest and summary.

