-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is chash ready for vchamilo shell upgrade ? #46
Comments
POC track :
|
found a way through, almost reaching to target. Needs some little changes in VChamilo (fix early loading of database.lib.php, recognize PHP_SAPI status aside CLI_SCRIPT definition) but the most part is in chash UpgradeCommand.php Most attention should be given to the configuration.php file handling during migration (pre 110 to post 1.10). It has to be copied from the older instance and reworked to fit the new VChamilo invocation, along with sys_root and database change. |
got context switching ok but fail on a : While the class is supposed to be Chash\DoctrineExtensions\DBAL\Types\UTCDateTimeType |
@jmontoyaa could you answer Valery's questions please? |
Hi guys, let me update you with the upgrade process in progress : |
Hi @vfremaux, this is a highly specialized topic, so not really something we usually do as community effort (we do publish all the developments we do, but specific stuff like that usually go through BeezNest's commercial support). If you need urgent assistance, there is always that option. |
@ywarnier I agree it is, now atually i am the "end of the chain" tech expert and have no matter in the poduct owner choices or budget allocation. I relay however the message that this high level of industrialisation is hard to reach without support of the core technology makers, what strong ever could be my technology insight and power. I hope they hear the message... |
Hi, can you copy and paste the chash command that you're using? |
Hi Julio
Vchamilo plugin (beeznest version) tells it would be compatible with chash. I digged dep into chash upgrade command and did not noticed any special coding for driving the configuration virtual switch when not in Web server environment. Is that exact or i missed something ? having 170 chamilos to raise to 1.11.x last branch, I not sure i may miss this step ;-)
If i understood the picture, an upgrade uses two paths, the old one and the new one, and gets material from older to newer. In my case i will need actually upgrade-database-only option as content transfer must be handled from outside. I've identifed the location when confg loads. just guessing ensuring a old virtual instance matchs a new corresponding virtual instance seems not so trivial at a glance. would you share an opinion on that point ?
The text was updated successfully, but these errors were encountered: