2014-02-24 00:19:58 -0500 | received badge |
Nice Question
(source)
|
2014-02-24 00:17:45 -0500 | received badge |
Notable Question
(source)
|
2014-02-17 01:06:56 -0500 | received badge |
Notable Question
(source)
|
2013-12-12 21:18:55 -0500 | received badge |
Popular Question
(source)
|
2013-11-21 08:27:21 -0500 | received badge |
Student
(source)
|
2013-11-04 15:09:50 -0500 | received badge |
Famous Question
(source)
|
2013-10-21 10:40:14 -0500 | commented question | Askbot installation fails in migration due to 0 values in AutoField Hi Fitoria, thanks for the comment. This was using the MySQL database. Hope that helps! |
2013-10-13 21:57:24 -0500 | asked a question | Askbot installation fails in migration due to 0 values in AutoField Hi all, hope you can help with what seems to be a small problem. I'm trying to install askbot on a new server and have run into problems with the migration chain for target 'askbot' during setup. Any ideas? I've listed the libraries that pip install askbot installed for me at the end of the post. [root@orbital askbot-django]# python manage.py migrate askbot
/usr/lib/python2.6/site-packages/django/utils/hashcompat.py:9: DeprecationWarning: django.utils.hashcompat is deprecated; use hashlib instead
DeprecationWarning)
/usr/lib/python2.6/site-packages/django/core/management/__init__.py:465: DeprecationWarning: The 'execute_manager' function is deprecated, you likely need to update your 'manage.py'; please see the Django 1.4 release notes (https://docs.djangoproject.com/en/dev/releases/1.4/).
DeprecationWarning)
/usr/lib/python2.6/site-packages/django/core/management/__init__.py:409: DeprecationWarning: The 'setup_environ' function is deprecated, you likely need to update your 'manage.py'; please see the Django 1.4 release notes (https://docs.djangoproject.com/en/dev/releases/1.4/).
DeprecationWarning)
/usr/lib/python2.6/site-packages/django/conf/urls/defaults.py:3: DeprecationWarning: django.conf.urls.defaults is deprecated; use django.conf.urls instead
DeprecationWarning)
WARNING!!! You are using a 'locmem' (local memory) caching backend,
which is OK for a low volume site running on a single-process server.
For a multi-process configuration it is neccessary to have a production
cache system, such as redis or memcached.
With local memory caching and multi-process setup you might intermittently
see outdated content on your site.
Running migrations for askbot:
- Migrating forwards to 0170_auto__add_field_group_read_only.
> askbot:0055_auto__chg_field_question_thread
- Migration 'askbot:0055_auto__chg_field_question_thread' is marked for no-dry-run.
! Error found during real run of migration! Aborting.
! Since you have a database that does not support running
! schema-altering statements in transactions, we have had
! to leave it in an interim state between migrations.
! You *might* be able to recover with: (migration cannot be dry-run; cannot discover commands)
! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
! NOTE: The error which caused the migration to fail is further up.
Error in migration: askbot:0055_auto__chg_field_question_thread
ValueError: The database backend does not accept 0 as a value for AutoField.
Here are the libraries according to pip list : AddOns (0.6)
akismet (0.2.0)
amqp (1.0.13)
anyjson (0.3.3)
askbot (0.7.49)
Babel (0.9.4)
Beaker (1.3.1)
beautifulsoup4 (4.3.2)
billiard (2.7.3.34)
BytecodeAssembler (0.5.1)
cas (0.15)
celery (3.0.24)
chardet (2.1.1)
Cheetah (2.4.1)
Coffin (0.3.8)
decorator (3.0.1)
DecoratorTools (1.7)
distribute (0.6.10)
Django (1.5)
django-appconf (0.6)
django-celery (3.0.11)
django-compressor (1.2)
django-countries (1.0.5)
django-followit (0.0.3)
django-keyedcache (1.4-6)
django-kombu (0.9.4)
django-picklefield (0.3.0)
django-recaptcha-works (0.3.4)
django-robots (0.9.2)
django-threaded-multihost (1.4-1)
django-tinymce (1.5.1b2)
ethtool (0 ... (more) |
2013-09-08 14:21:26 -0500 | received badge |
Good Answer
(
source
)
|
2013-07-29 15:26:05 -0500 | received badge |
Nice Answer
(
source
)
|
2013-07-29 13:25:11 -0500 | received badge |
Popular Question
(source)
|
2013-03-29 12:33:32 -0500 | received badge |
Taxonomist
|
2013-03-26 13:30:29 -0500 | commented answer | Help with installing askbot-0.7.48 Very nice! Much more thorough than my mini-tutorial. Certainly a good gist since it incorporates more functionality (i.e., Elastic beanstalk). Thanks for the lead. |
2013-03-26 13:29:05 -0500 | received badge |
Supporter
(
source
)
|
2013-03-26 13:27:27 -0500 | received badge |
Famous Question
(source)
|
2013-03-14 10:21:55 -0500 | received badge |
Teacher
(
source
)
|
2013-03-14 10:21:55 -0500 | received badge |
Self-Learner
(
source
)
|
2013-03-14 06:18:27 -0500 | answered a question | Help with installing askbot-0.7.48 Here's what I was able to figure out. I think the install finally works.. pip install askbot now installs Django==1.5 instead of Django==1.4 which is needed, since Django==1.5 apparently isn't supported. You have to do a pip install -U Django==1.4 to revert Django back to 1.4 I previously tried to install Askbot via pip install askbot , rather than through the develop branch in github, but here it runs into problems. I'm trying to install with MySQL, but the python manage.py askbot migration doesn't work with InnoDB (dies around migration 101). Perhaps in the install instructions you should mention to set the DB to MyISAM by default. One way to do this is through the /etc/my.cnf file. For EC2, when using Apache, you need to install mod_wsgi as it is not part of the AMI image by default. |
2013-03-14 06:17:54 -0500 | asked a question | Help with installing askbot-0.7.48 I've tried to set up askbot a number of times on several different machines with varying levels of success, none of them complete. It seems that the pip install askbot doesn't work very well out of the box anymore. I ended up installing on Amazon EC2. This is a placeholder "question" for the answer that I was able to come up with. |