[Top][All Lists]

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

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

From: Yuchen Pei
Subject: Re: [H-source-users] Deciding what to do with the server side code
Date: Mon, 19 Jul 2021 19:47:02 +1000
User-agent: mu4e 1.4.13; emacs 27.2

Damien Zammit <damien@zamaudio.com> writes:

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.

Why does it make a difference? Even if the server code is much out of sync, provided we can get a php7 site to work on the staging, we can migrate over the production database (as you mentioned below), no?

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

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

$ 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.

Why would separating easygiant of the source into a submodule help? I thought the server software is very much just h-node.



PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0

Attachment: signature.asc
Description: PGP signature

reply via email to

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