[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[H-source-users] Deciding what to do with the server side code

From: Damien Zammit
Subject: [H-source-users] Deciding what to do with the server side code
Date: Mon, 19 Jul 2021 18:15:25 +1000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0

Hi Yuchen,

On 19/7/21 12:19 pm, Yuchen Pei wrote:
> I had a look at the server code and compared the files with the 
> latest commits on the repo, and it appears to me the only unmerged 
> change is commit efd48dee15bbdf3a5a2b6a5cf724ca586568b53e. So the 
> server code is rather up to date.

If that is true, and the server code is completely up to date
except for a single commit, that would change my opinion on what to do:
we should keep the framework as php, but try to upgrade to php7.

In that case, I would say we should just see if we can find a version of 
that works on php7, and try to migrate a copy of the site to a testing 
Then when we have it working without a populated database, we can work out how 
migrate the production database.

(Latest release seems to be 0.4.1 in 2010, but there has been activity in SVN 

$ svn checkout https://svn.code.sf.net/p/easygiant/code/trunk easygiant-code

It would likely be less work to port EasyGiant framework to php7 than rewrite 
the whole site in django.
Unfortunately, the source code of easygiant is embedded in the root folder of 
the site, so one cannot separate
this into a submodule.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]