Installation fails on ubuntu 13.10

[johanovic]

Hi folks,

The installation fails on Ubuntu 13.10. Both in a virtualenv and in a virtualbox the demosite does not get up and running.

The virtualbox install gives me the following traceback:

Traceback (most recent call last): File "./manage.py", line 10, in

execute_from_command_line(sys.argv) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/core/management/init.py", line 399, in execute_from_command_line

utility.execute() File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/core/management/init.py", line 392, in execute

self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/core/management/init.py", line 272, in fetch_command

klass = load_command_class(app_name, subcommand) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/core/management/init.py", line 75, in load_command_class

module = import_module('%s.management.commands.%s' % (app_name, name)) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module

import(name) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/south/management/commands/init.py", line 10, in

import django.template.loaders.app_directories File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/template/loaders/app_directories.py", line 25, in

raise ImproperlyConfigured('ImportError %s: %s' % (app, e.args[0])) django.core.exceptions . ImproperlyConfigured : ImportError wagtail.wagtailembeds: No module named requests

The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

chmod +x /tmp/vagrant-shell && /tmp/vagrant-shell wagtaildemo

I then ran pip install requests and synced the db. The following error I get is:

Internal Server Error: /admin/ Traceback (most recent call last): File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 90, in get_response response = middleware_method(request) File "/home/vagrant/.virtualenvs/wagtaildemo/src/wagtail/wagtail/wagtailcore/middleware.py", line 11, in process_request request.site = Site.find_for_request(request) File "/home/vagrant/.virtualenvs/wagtaildemo/src/wagtail/wagtail/wagtailcore/models.py", line 50, in find_for_request return Site.objects.get(hostname=hostname) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/manager.py", line 151, in get return self.get_queryset().get(_args, *_kwargs) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/query.py", line 301, in get num = len(clone) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/query.py", line 77, in len self._fetch_all() File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/query.py", line 854, in _fetch_all self._result_cache = list(self.iterator()) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/query.py", line 220, in iterator for row in compiler.results_iter(): File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 710, in results_iter for rows in self.execute_sql(MULTI): File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 781, in execute_sql cursor.execute(sql, params) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/backends/util.py", line 69, in execute return super(CursorDebugWrapper, self).execute(sql, params) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute return self.cursor.execute(sql, params) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in exit six.reraise(dj_exc_type, dj_exc_value, traceback) File "/home/vagrant/.virtualenvs/wagtaildemo/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute return self.cursor.execute(sql, params) ProgrammingError: relation "wagtailcore_site" does not exist LINE 1: ...ge_id", "wagtailcore_site"."is_default_site" FROM "wagtailco...

I cannot get any further.

I also tried the install in a virtualenv. Unsuccesfully. So far I did not get it to work.

BTW/ Honestly: pip + venv is really the way to go to sell your package in the django community. Virtualbox is nice, but a lot more of a hassle.

[tomdyson]

Thanks for the feedback, @wcapio. We're working to reduce the dependencies (Elasticsearch, Redis, npm) so developers can just pip install wagtail, but we're not quite there yet. @kaedroho can you look into this please? The first issue looks like a casualty of the embedly changes.

[kaedroho]

Apologies for that. It was my changes to wagtailembeds that caused this (I used requests, but didn't know/check that it was recently removed from requirements). I have now added requests back to requirements.

The database issues are most likely caused by the vagrant provision script crashing out due to the above issue. To solve this, you would also need to run "python manage.py migrate" after syncdb to make sure the wagtail tables are created.

[btipling]

I was able to get everything working fine on Ubuntu 13.10, although I had to install these things:

sudo apt-get install python-dev postgresql-server-dev-all libxml2-dev libxslt1-dev

pip install six

pip install -r ./requirements/base.py
pip install -r ./requirements/dev.py
pip install -r ./requirements/prod.py

I am actually using a virtualenv on vmware fusion

[johanovic]

@kaedroho and @tomdyson I can confirm that the current build works fine on a virtualbox in Ubuntu 13.10.

Here is my first impression (I am sorry, I know you did not ask for it, but I could not resist):

• The different apps in the codebase could have been split out into different, reusable apps. The current size of the codebase makes me a bit scared that this might not be maintained in the future, and hence not save.
• What does the license mean? Every site that uses wagtail needs to mention it explicitly? Frontend? Or backend?
• The whole take on CM is sooooo nice! This not only looks good, it is robust and intuitive.
• This redefines the standard for django CMS's. If this project gets the attention it needs, it is a game changer.
• It is really focused on content.
• Comes with a minimal template. Though this often looked down upon in the community, it really is a good thing to do because it gives you a nice impression of the aims of the package.
• Reactions on issues have been very fast.

Kudos Torchbox!!

[tomdyson]

Hi @wcapio - belated thanks for your first impressions! We're delighted that you're so positive about Wagtail. Some responses:

• The codebase is split into separate apps - wagtailsearch / wagtailimages / wagtailadmin etc. Did you mean that we should split them up even more?
• The license is intended to be very liberal. You don't have to mention Wagtail explicitly anywhere.

[johanovic]

Hi @tomdyson

When I think of different apps, I think about different standalone apps. For instance,

django-wagtail-search django-wagtail-admin django-wagtail-images ...

Each of these apps would have its own github repository and they would be able to plugin easily into the wagtail core, but they could also be replaced by another search app, for instance.

Each app would have its own tests, etc. In that sense wagtail would become more of an ecosystem rather than one big app. Someone could write django-wagtail-videos, for instance. Or django-wagtail-helpdesk or django-wagtail-templates.

Then django-wagtail would be the wagtailcore and it would have several of the other django-wagtail-something apps in its requirements. For this to work it would mean that the core is mainly focused on making these apps work together smoothly.

This would benefit the django community because django-wagtail-admin could be forked and changed into django-admin-new in order to only use the wagtail admin rather than the standard django admin.