I have to move an old confluence wiki space from an old busted machine to a fancy new xserve. Confluence 3.x will not allow imports of 2.x exports so I cannot install and license 3.x and then import the old data. Oh and to make it extra fun the owner(s) of the old box won't give me access. They are willing to transfer the attachments folder and the spaces content folder but I'm not a wiki wizard and do not know if that will help me at all.
Oh Stack Overflow I beseech thee! How is one to move a confluence installation?
It is certainly possible to go from 2.7 to 3.x, but you need to follow the steps as detailed by atlassian - we upgraded 2.5.7 to 3.2. by going over 2.7.4 (which is a necessary step)
(Probably you will be able to upgrade directly from 2.7.2 to 3.5)
The trick is that you need to setup the 2.7.2 environment,before you can start the upgrade: setup the 2.7.2 home directory, import the database into the appropriate database ...
Once that you have the 2.7.2 up and running, upgrading to 3.5 should be straightforward.
Ask the owner if you can get the complete home directory (which contains the attachments) and the xml database.
Francis
Related
I am using Pycharm and want to install an older version of Django. However, PC only seems to install V2. How can I configure Pycharm to install an older version?
This is about installing an older version, NOT changing a version that has already been installed. I want to configure Pycharm to INSTALL a specific version.
Specifically for installing through PyCharms UI, you can specify which version of a package you want to install in the package manager. Navigate to
File -> Settings(or Preferences on MacOs) -> Project: [project name] -> Project interpreter
and click on the + sign under the cog icon. Then search for Django and specify the version you want to install from the drop down menu below the Description field.
However, if you want to install a different version through the terminal, you should write something along the lines of
pip install Django==[your_version]
As far as I know, there is no way to change the version on creating a new project unless you use your own interpreter when creating a new project.
So you can first create your virtual environment with the django version you want, and then select that venv when creating a new django project:
virtualenv venv
source venv/bin/activate
pip install django==2.1
When you want to create a new project, select Existing Environment instead of New environment using... and use your custom venv.
It's not possible at the moment. The only workaround, as mentioned by Pedram, is to use the existing interpreter with needed version of Django installed.
I filed a feature request about that, feel free to vote and leave comments.
You may also find useful the following feature request https://youtrack.jetbrains.com/issue/PY-33804
I have a project which is done with Laravel 5.6. But My current server doesn't have php 7.1 installed yet. How is it possible to downgrade to Laravel 5.5?
I also down graded my project also, but then I was getting ton of errors. But most of them were about unfamiliar key words and unsupported packages. So, success depends on your project’s dependencies and also your effort.
Follow these steps.
Backup your project
Change the value of Laravel version inside the composer.json to Laravel 5.5
Delete vendor folder
Run composer install
** By then you will have to take care of any issues in your own code because there should be new functionalities in earlier versions which
is not used in older.
Or
Go to this page and do the instructions in reverse order
How can I setup a Django 1.5.1 app running with Python 3.3 to access a MySQL database? I tried using MySQLdb but apparently it doesn't support Python 3.3.
My next intention was to use Connector/Python, but what am I supposed to put for the "Engine" key of the Databases dictionary of the settings.py file?
If someone could provide detailed steps of how to get Django to work with Connector/Python, that would be great!
MySQLdb is the Python interface to MySQL [supported by django]. Version 1.2.1p2 or later is required for full MySQL support in Django.
At the time of writing, the latest release of MySQLdb (1.2.4) doesn’t support Python 3. In order to use MySQL under Python 3, you’ll have to install an unofficial fork, such as MySQL-for-Python-3.
This port is still in alpha. In particular, it doesn’t support binary data, making it impossible to use django.db.models.BinaryField.
Basically your only options to avoid Alpha quality drivers are:
Don't use python 3.
Don't use MySQL.
Hopefully this makes the choice easier: http://grimoire.ca/mysql/choose-something-else
REF: https://docs.djangoproject.com/en/dev/ref/databases/#python-3
I'm installing Solr to be used with Haystack / Django.
How do I go about installing Solr? Do I need to follow the online instructions exactly and install services like Tomcat?
The above questions I just commented make all the difference if you are set on installing / setting this up yourself. OR you could use a hosted service (read: easy).
Try out http://websolr.com I'm loving it.
If you are on OSX and want a local Solr instance just to try out for some development, this is an awesome tutorial: http://realityloop.com/blog/2011/07/19/setting-multicore-apache-solr-os-x-using-homebrew
essentially brew install solr, and then some configuration.
If you are trying to do a production level solr server on a linux operating system, I would suggest working with an instruction set specific to that distribution and the version you are using. OR even better, bite the bullet and pay someomne who knows what they are doing to set it up (make sure your indexes won't fail or go down).
Does anyone know how to / can anyone link to simple instructions for how to upgrade from Django 1.1 to Django 1.2?
I can find masses of documentation on the differences between them, the changes you'll need to make to your project etc.
What I can't find is actually how to upgrade!
Thanks.
I usually create a symlink from my Python site-packages directory to the Django version I am using. When I change versions I merely change the symlink to point at the right version. Here is the documentation for creating a symlink. The docs mention the development version but you can do it for any version.
Django 1.2 is fully compatible with 1.1, so your projects could stay the same way.
To update django in your server:
If you already have a svn repository, just update it, Otherwise uninstall Django and then download it again from here http://www.djangoproject.com/download/ I have never had problems with trunk version, but that is your decision.
svn co http://code.djangoproject.com/svn/django/trunk/ django-trunk
cd django-trunk
sudo python setup.py install
First, follow the instructions for removing old versions of Django
Then, you can follow these steps to pull the released branch of 1.2.x:
svn co http://code.djangoproject.com/svn/django/branches/releases/1.2.X/ django
cd django
sudo python setup.py install
I agree with uanefren, though. Using trunk has never posed any issues for me, and it probably has the best ongoing support and most current documentation.
Here's a good link using pip: how do you install django older version using easy_install?, which essentially comes down to:
pip install --upgrade django==1.2.5 (Which is the latest version of 1.2, AFAIK)
Also, before upgrading, make sure you read:
https://docs.djangoproject.com/en/1.2/releases/1.2/
and
https://docs.djangoproject.com/en/1.2/ref/contrib/csrf/#ref-csrf-upgrading-notes
As 1.2 implemented breaking changes for CSRF tokens. Also, make sure your save and delete methods include **kwargs, as the multiple database change adds a kwarg to the save (and possibly the delete) method(s).
If you run Activestate, you can use pypm install django==1.2.5 instead.
Imho most common problem of upgrade like this is CSRF protection changes you will meet in you Upgrading way.
Main thing here is to read https://docs.djangoproject.com/en/1.3/releases/ of your django version. 1.2 is in your case.
This update has some backwards incompatible changes with CSRF protection described almost fist in 1.2 release changes.
There also some articles like http://garmoncheg.blogspot.com/2011/07/django-upgrading-django-from-11-to-125.html on blogs. Here is a brief look at this problem.
Hope this will help someone with those issues.