I am having one codeigniter application with version 2.2.6. Is it good to use it in production OR I have to upgrade to 3.1
If YES how to upgrade? Version 3.x is still under development. What are the deprecated function (https://www.codeigniter.com/docs)
Its always better to use latest version for speed & security purpose.
But first you have to check your server PHP version, because CodeIgniter latest version 3.1.9 is not compatible with PHP 5.6
Your server must have PHP version 7.1 or 7.2 for CI 3.1.x
For upgrade CodeIgniter 2.2.6 to 3.1.x, you have to make few changes.
You can get steps for upgrade CI from here.
If your projects is not using deprecated CI functionality, then just replace "system" folder with latest version of CI will work.
My suggestion is to use CI latest version in production.
Related
I spent 1 week trying to upgrade Magento from version 2.2 to 2.4.
In order to proceed I have downloaded and I am using composer 1.
My PHP version is 7.1 - Perfectly compatible with Magento 2.2.
With composer 1 I was able to get a "composer require" without errors.
I then launched the "composer update" command but it goes into error due to the lack of php 7.4 or higher.
Now: I could also update the php and finish the "composer update" but then the "magento/upgrade" will not work because it is the one of Magento 2.2 which only works with php 7.1
Do you have solutions?
I am aspects to upgrade Magento
You have 2 solution:
1, If you dont want to upgrade magento 2.2 to magento 2.4, you can remove php7.4 and use php7.1 again.
2, Upgrade magento version to 2.4.x:
With magento <=2.4.3, you can use php7.4
With magetno >=2.4.4, you can use php8.1
Step by step to upgrade magento version you can read it here Upgrade magento version
For Magento 2.4.4, the minimum requirement of PHP version is 8.1 so you need to make sure to change the PHP version then run the composer require to upgrade.
Check the official documentation: https://devdocs.magento.com/guides/v2.4/release-notes/release-notes-2-4-0-open-source.html
https://devdocs.magento.com/guides/v2.4/release-notes/open-source-2-4-5.html
For upgrade process:
https://www.cloudways.com/blog/magento-2-4-upgrade/
https://devdocs.magento.com/guides/v2.4/comp-mgr/cli/cli-upgrade.html
Thanks
Currently I am using Rundeck 3.0.23-20190619.
Whether Rundeck 3.0.23-20190619 is stable version?
From the https://bintray.com/rundeck/rundeck-rpm/rundeck able to see the Rundeck 3.0.23-20190619 is not yet published as GA.
2.11.14-1.70.GA is the latest GA version with build date 2019-09-13T03:37:04.000Z.
Will the application developed with 3.0.23-20190619 compatible with 2.11.14-1.70.GA?
Right now the latest stable release is 3.1.2, you can check the latest version in the changelog here. The "GA" notation is not used anymore. In some cases, you can see some updates of 2.11 / 3.0 branches focused on backports, not for new features, etc.
Your projects and jobs are compatible using 2.11, 3.0 and 3.1 branches.
Suppose I have version 1.1.0 on a NuGet server.
I then continue development and push version 1.2.0.
Then I find a bug in version 1.1.0 and want to fix this.
At this point, can I still push version 1.1.1?
There's nothing in the NuGet spec or protocol that prevents it, so it might depend on which NuGet server you're using, but I would be extremely surprised if any server forbids it because it would be so short sighted, in my opinion.
Using NuGet.Protocol on nuget.org as an example, version 4.9.3 was release in January 2019, but versions 4.8.2, 4.7.2, 4.6.3, 4.5.2, 4.4.2 and 4.3.1 were released in March, two months later.
I would like to know whether it is possible to upload MongoDB from 2.2 to 3.2 without any intermediary upgrades. If it is possible please share a resource that can follow. I would like to know what things to looks out for when up grading
No you can't.
From the documentation,
Upgrade Requirements
To upgrade an existing MongoDB deployment to 3.2, you must be running a 3.0-series release.
To upgrade from a 2.6-series release, you must upgrade to the latest 3.0-series release before upgrading to 3.2. For the procedure to upgrade from the 2.6-series to a 3.0-series release, see Upgrade MongoDB to 3.0.
I use grafana 2.1 and created multiple dashboards, templates etc.
I would like to upgrade to grafana 2.6. Is there any way to upgrade to 2.6 without affecting the existing dashboards?
There are no breaking changes between 2.1 and 2.6. In theory upgrading should be a simple matter of installing the new packages. I personally have upgraded from 2.1.3 to 2.5 to 2.6 with no issues.
For windows version, I just had to copy the data/grafana.db and the data/plugins directory from the old installation to the new installation directory. Just make sure the newer version does not have any breaking changes.
You can upgrade Grafana to higher versions for better features and also import your previous dashboard to the new version without any problem by using Import/Export feature.