I am trying to import data from a newer version of neo4j to an older version, inside my heroku. When I restore from url, it seems like nothing happens. I am using a newer version in local. Is it possible that, this version difference preventing my restore?
Related
How can I download the user docs/documentation/manual for older ElasticSearch for offline usage?
Recently, the online documentation for older versions of ElasticSearch (for example, ElasticSearch 1.3.2) started to show this message:
WARNING: Version 1.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
What worries me most is the may be removed part. Right now, we don't have the resources to upgrade our software to support the latest ElasticSearch version, so we will need to keep working with the older versions for a while. How I will be able to give maintenance to our software if the Elastic company decides to remove the documentation for older versions of ElasticSearch? There is any way to download it from https://www.elastic.co/ or build it from some repository?
Thank you very much for your help!
You can clone the official elasticsearch repository to a local machine, change to branch to the version you want, in your cause branch 1.3, then you will have the documentation in the directory docs.
The documentation is in the .asciidoc format, you can try build it following the official instructions, or using other asciidoc to pdf/html converters.
I have a Laravel 5.4 project (web application), it's a huge product. I want to add some well known packages like error logging and debugging. Is there any simple way to update the Laravel from 5.4 to 5.5 or 5.6 without affecting the things what was already done? How can I do this?
You should never upgrade your production environment directly without testing. It would be better to set up a staging environment and test the upgrade there. If you don't have any problems there, consider upgrading the production environment.
If you want to know all changes from older versions to newer versions, check the upgrade guides in order:
https://laravel.com/docs/5.5/upgrade
https://laravel.com/docs/5.6/upgrade
https://laravel.com/docs/5.7/upgrade
I am using 5.6 version of sonar, want to upgrade to 6.7. Can I directly upgraded to 6.7 ?
I have 8-10 sonar projects hosted on a same instance of sonar server. I am not sure what would break after upgrade. I am thinking of following approach
Install (do not upgrade) a new version of sonar 6.7, this would run on the different port(s).
Create a copy of sonar database which I have with my older sonar version, attach that copy of DB to new installation of sonar (by updating the sonar configuration file).
Assuming everything works fine, retire the older version (sonar server & DB).
I am using dedicated database as SQL server.
Anybody tried this approach? does it work?
Atul
If you're using one of the supported databases, you can upgrade directly from 5.6 to 6.7.
Simply follow the Upgrade Guide - and make sure that you back up your DB first in case of troubles.
I have a large project running on Laravel 4.2 and now I would like to upgrade it to the latest release (5.4)
On the upgrading guide I can see the steps to upgrade from each release to the next one, but the 4.2 to 5.0 requires a fresh install. Hence the question: should I install 5.4 (and fix problems) or 5.0 (running each upgrade)?
I'm possibily using any Laravel functionality, and have organized repositories for my own custom methods; I also need to maintain the database. I need to upgrade because I would like to use event bradcasting with Laravel Echo.
Thanks
To those looking for an answer: update directly to latest version, then fix changes along the way.
Explanation:
At first I tried to upgrade version by version; it was a pain. Every single vendor had different packages for each version and that caused issues even before correcting the code. I couldn't start fixing my code because the installation requirements of the vendors were failing at a certain point of the upgrade process.
Upgrading directly to latest version requires the correction of many things, but at least those are only related to your code. In my case I had to remove Sentry (authentication), Laravel OAuth, and some others I don't remember in favor of some native packages which I hope will be maintained properly. The upside of this approach is that once you have all the packages you need installed you can work directly on your code... which is what you have to do anyway.
I ran into an issue today where my preview server was running an older version of a project instead of the most recently published version. The most recently published version was 1.0.4.10, but after some testing, I determined that version was not the version of the application that the server was retrieving.
After trying a few things, I tried publishing a new version under 1.0.5.0 instead of continuing with the 1.0.4.xx numbering, and that fixed the issue.
VS's auto increment feature recommended 1.0.4.10, but is there an issue with this being the same as 1.0.4.1? So maybe it was running 1.0.4.9? Or something behind the scenes I'm not aware of?