Trouble Installing head version on Ubuntu 14.04

[Paul Whipp]

Hi there,

I'm taking a look at Mayan which looks potentially very useful. I am an experienced Django/Python programmer.

Following your instructions at https://mayan.readthedocs.org/en/latest/intro/installation.html to create a local test installation went very well (nice clear instructions) until just before syncing the db.

When I launch the shell (just to check everything before syncing up the db) I get:

ImportError: No module named signaler

pip installed everything in the (dev) requirements fine. and there is no easy help available via google.

I could just drop 'signaler' from the list but I worry that it is likely to be crucial.

How can I obtain the missing module?

I'm hopeful that as it is the last module in the INSTALLED_APPS that this is the only thing preventing me getting my test installation up and running.

Thanks in anticipation,

Paul Whipp

Github: https://github.com/pwhipp
Office: 07 3103 2894 (Australia Only)
Mobile: +61 410 545 357

Skype: paul_whipp

Django, Python, and PostgreSQL web application developer

[Lachlan Musicman]

Paul,

Seems to be here?

https://github.com/rosarior/mayan_appsembler/tree/master/apps/signaler

cheers
L.

> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Mayan EDMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mayan-edms+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
The idea is that a beautiful image is frameable. Everything you need
to see is there: It’s everything you want, and it’s very pleasing
because there’s no extra information that you don’t get to see.
Everything’s in a nice package for you. But sublime art is
unframeable: It’s an image or idea that implies that there’s a bigger
image or idea that you can’t see: You’re only getting to look at a
fraction of it, and in that way it’s both beautiful and scary, because
it’s reminding you that there’s more that you don’t have access to.
It’s now sort of left the piece itself and it’s become your own
invention, so it’s personal as well as being scary as well as being
beautiful, which is what I really like about art like that.
-----------------------------------------------------------------------------------------------------------
Adventure Time http://theholenearthecenteroftheworld.com/

[Lachlan Musicman]

Sorry, here

https://github.com/rosarior/mayan/tree/master/apps/signaler
cheers
L.

[Paul Whipp]

Thanks for the quick response. I can see it there, along with a lot of other modules, which I guess I'm going to need as well. I don't understand how the mayan_appsembler repo is intended to fit in with the mayan_edms repo.

I've cloned mayan_appsembler and added its apps to my virtualenv path.

Then I hit 'registration' as a missing module so I installed 'django-registration' (hope that is the one) - missing from requirements.txt?

Then I hit 'bootstrap' as a missing module so I installed django-bootstrap (ditto) - missing from requirements.txt?

Then I hit

...

  File "/home/paul/wk/cccs/mayan_appsembler/apps/storage/conf/settings.py", line 16, in <module>

    {'name': u'FILESTORAGE_LOCATION', 'global_name': u'STORAGE_FILESTORAGE_LOCATION', 'default': os.path.join(settings.PROJECT_ROOT, u'document_storage'), 'exists': True},

  File "/home/paul/.virtualenvs/mayan/local/lib/python2.7/site-packages/django/conf/__init__.py", line 55, in __getattr__

    return getattr(self._wrapped, name)

AttributeError: 'Settings' object has no attribute 'PROJECT_ROOT'

It seems that the installation guide is missing something substantial.

How should I set about getting a working local copy where I'm confident that I have the right dependencies so that I can explore the code and consider contributing?

Cheers,

Paul

On 9 July 2014 08:05, Lachlan Musicman <dat...@gmail.com> wrote:

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mayan-edms+...@googlegroups.com.

[Roberto Rosario]

Hi Paul,

The mayan_appsembler repository is a custom fork of Mayan for the appsembler platform (https://dashboard.appsembler.com/appstore/app/48/mayan/) and is not meant for general usage.  Deploy from https://github.com/mayan-edms/mayan-edms (or the older https://github.com/rosarior/mayan-edms if getting errors) into a virtualenv as Mayan has quite a bit of dependencies that could clash with system wide libraries if deployed system wide. The signaler app is a Mayan app [https://github.com/mayan-edms/mayan-edms/tree/master/mayan/apps/signaler] so I am at a loss as to why your install is saying it is missing.  Registration and bootstrap are Mayan apps too, the requirements.txt has all the 3rd party apps required. Mayan has now moved to Django 1.6 and a Django 1.6 project structure which even simplified the installation. I've updated the installation instructions and simplified them [http://mayan.readthedocs.org/en/latest/intro/installation.html]. Just tried a clean install and had no app errors. Give it a second go following this new instructions. Thanks,

--Roberto

> email to mayan-edms+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.



--
The idea is that a beautiful image is frameable. Everything you need
to see is there: It’s everything you want, and it’s very pleasing
because there’s no extra information that you don’t get to see.
Everything’s in a nice package for you. But sublime art is
unframeable: It’s an image or idea that implies that there’s a bigger
image or idea that you can’t see: You’re only getting to look at a
fraction of it, and in that way it’s both beautiful and scary, because
it’s reminding you that there’s more that you don’t have access to.
It’s now sort of left the piece itself and it’s become your own
invention, so it’s personal as well as being scary as well as being
beautiful, which is what I really like about art like that.
-----------------------------------------------------------------------------------------------------------
Adventure Time http://theholenearthecenteroftheworld.com/

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to mayan-edms+unsubscribe@googlegroups.com.

[Lachlan Musicman]

Yes, I apologise for sending you on the appsembler path, my bad.


cheers
L.

On 9 July 2014 15:13, Roberto Rosario

>>> > email to mayan-edms+...@googlegroups.com.

>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> The idea is that a beautiful image is frameable. Everything you need
>>> to see is there: It’s everything you want, and it’s very pleasing
>>> because there’s no extra information that you don’t get to see.
>>> Everything’s in a nice package for you. But sublime art is
>>> unframeable: It’s an image or idea that implies that there’s a bigger
>>> image or idea that you can’t see: You’re only getting to look at a
>>> fraction of it, and in that way it’s both beautiful and scary, because
>>> it’s reminding you that there’s more that you don’t have access to.
>>> It’s now sort of left the piece itself and it’s become your own
>>> invention, so it’s personal as well as being scary as well as being
>>> beautiful, which is what I really like about art like that.
>>>
>>> -----------------------------------------------------------------------------------------------------------
>>> Adventure Time http://theholenearthecenteroftheworld.com/
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Mayan EDMS" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to

>>> mayan-edms+...@googlegroups.com.

>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
> --
>

> ---
> You received this message because you are subscribed to the Google Groups
> "Mayan EDMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to mayan-edms+...@googlegroups.com.

[Paul Whipp]

Thanks Guys,

As an experiment I've directly cloned your repo and done the exact instructions again from scratch. It worked fine.

Then I went back and tried again with our fork and it failed. Doh! My bad though so I'll sort it. Must be something to do with our customised settings.

Thanks for the help.

[Paul Whipp]

OK. I've partially sorted this. It was a problem with the settings where I'd wrongly assumed that BASE_DIR meant the project's root directory.  I've tidied up the settings preparatory to deploying to production etc here.

I can now './manage.py shell' and import all the modules OK which is good progress. I still have a bizarre import issue though:

If I run syncdb, I get "django.core.exceptions.ImproperlyConfigured: ImportError installation: cannot import name Installation"

[To make things easier with my IDE etc. I've also added mayan/mayan/apps to the virtual env path]

In the 'django syncdb' call the error appears like this:

Traceback (most recent call last):

  File "/home/paul/.virtualenvs/mayan/bin/django-admin.py", line 5, in <module>

    management.execute_from_command_line()

  File "/home/paul/.virtualenvs/mayan/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line

    utility.execute()

  File "/home/paul/.virtualenvs/mayan/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/paul/.virtualenvs/mayan/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/paul/.virtualenvs/mayan/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/paul/.virtualenvs/mayan/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module

    __import__(name)

  File "/home/paul/.virtualenvs/mayan/local/lib/python2.7/site-packages/south/management/commands/__init__.py", line 10, in <module>

    import django.template.loaders.app_directories

  File "/home/paul/.virtualenvs/mayan/local/lib/python2.7/site-packages/django/template/loaders/app_directories.py", line 25, in <module>

    raise ImproperlyConfigured('ImportError %s: %s' % (app, e.args[0]))

django.core.exceptions.ImproperlyConfigured: ImportError installation: cannot import name Installation

DEBUG:scheduler:Scheduler shut down on exit

If I run 'django shell' I can execute the command 'from installation import Installation' without a problem.

I'm investigating this but would love to know if you have any ideas.

[Mathias Behrle]

* Paul Whipp: " Re: [Mayan EDMS: 712] Trouble Installing head version on Ubuntu
14.04" (Thu, 10 Jul 2014 08:08:47 +1000):

Hello Paul,

[...]

> [To make things easier with my IDE etc. I've also added mayan/mayan/apps to
> the virtual env path]

Did you try without that?

Cheers,
Mathias

[Paul Whipp]

Yes. No difference :(

[Paul Whipp]

The problem was that I'd re-enabled adding the debug_toolbar which I like using. Very deceptive, getting a subtle import error sometimes as a result of including an app but such is life. Read on for a fixed debug toolbar configuration and a simpler way to handle settings.

Adding debug_toolbar as an INSTALLED_APPS causes:

(mayan)~/wk/cccs/mayan $ django syncdb

...

django.core.exceptions.ImproperlyConfigured: ImportError installation: cannot import name Installation

Remove it from the installed_apps and this problem goes away.

Some googling found this: https://github.com/django-debug-toolbar/django-debug-toolbar/issues/524 so I've set up the debug toolbar explicitly in my development configuration. This is all done in the settings except for the debug urls which needed adding to mayan/urls.py (line 68 on).

I think I've substantially improved the mayan settings configuration. My solution is based upon two scoops (with the addition of the 'includes' folder and secrets.py).

Notice how you can keep each site configuration safely in the repo and that it is nice and simple (no more conditional stuff in settings checking the debug and then only having one possible 'development' configuration).

The site secrets are kept in a secrets.py file which is not stored in the repository (secrets.py.example makes it easy to create a secrets.py for local development or for production as needed - the only time you need to share them around might be if you are also copying the databases about although it is probably unnecessary even then unless you are relying upon data using the secret_key).

I prefer my secrets.py solution to the two scoops use of environment variables because it keeps everything in Python and I prefer using the 'includes' subfolder because you can then tell at a glance what files in the settings folder are actually there to be used as settings. In complex applications I often have other settings/includes for special purposes (such as supporting different kinds of developer or sites using different deployment methods).

Cheers,

Paul

[Roberto Rosario]

Thanks for the debug_toolbar archaeology!

I've been trying to improve the way settings situation [https://github.com/mayan-edms/mayan-edms/tree/master/mayan/config] now that we are close to a PyPI package and I like your solution. There are some things I would like to keep as they are now (default DB backend to sqlite instead of PostgreSQL) so that Mayan 'just works' as soon as it is installed. I'll pull your changes and tweak as necessary.

Thanks a lot Paul!

--Roberto

[Roberto Rosario]

No worries :)
Thanks for the help.

[Paul Whipp]

It is a pleasure to contribute to what is looking like a very impressive package.

For our use case we need to incorporate Mayan into our existing sites. I'll begin working on that once the staff have completed their review of its functionality (assuming they approve it). I'll have to work out a process where I can keep a clean fork of mayan (to generate pull requests where I feel I can contribute further), any customisations not suitable for inclusion and our site specific stuff.

[Paul Whipp]

btw, I'm new to pull requests. Hope you didn't mind my experimenting with the contributors.rst.

[Roberto Rosario]

Thanks a lot. I hope the review team finds it a worthy addition to the products you offer.

Disclaimer: I am not a Git expert, but I think a fork with two branches would be the best choice. One branch is the vanilla Mayan and another with your company specific code. You can merge from the vanilla to the company specific one almost straight away, dealing with conflicts only when there are commits the vanilla branch that write over files that are also present in the company branch (which should be very few if any). For improvements in the company branch that you want to merge to the vanilla branch you can use the cherry-pick command and just merge specific commits. 

On Friday, July 11, 2014 6:20:30 PM UTC-4, Paul Whipp wrote:

It is a pleasure to contribute to what is looking like a very impressive package.

For our use case we need to incorporate Mayan into our existing sites. I'll begin working on that once the staff have completed their review of its functionality (assuming they approve it). I'll have to work out a process where I can keep a clean fork of mayan (to generate pull requests where I feel I can contribute further), any customisations not suitable for inclusion and our site specific stuff.

On 11 July 2014 11:13, Roberto Rosario <roberto...> wrote:

No worries :)
Thanks for the help.

On Jul 9, 2014 1:16 AM, "Lachlan Musicman" <dat...@gmail.com> wrote:

Yes, I apologise for sending you on the appsembler path, my bad.


cheers
L.

On 9 July 2014 15:13, Roberto Rosario

>>> > email to mayan-edms+unsubscribe@googlegroups.com.

>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> The idea is that a beautiful image is frameable. Everything you need
>>> to see is there: It’s everything you want, and it’s very pleasing
>>> because there’s no extra information that you don’t get to see.
>>> Everything’s in a nice package for you. But sublime art is
>>> unframeable: It’s an image or idea that implies that there’s a bigger
>>> image or idea that you can’t see: You’re only getting to look at a
>>> fraction of it, and in that way it’s both beautiful and scary, because
>>> it’s reminding you that there’s more that you don’t have access to.
>>> It’s now sort of left the piece itself and it’s become your own
>>> invention, so it’s personal as well as being scary as well as being
>>> beautiful, which is what I really like about art like that.
>>>
>>> -----------------------------------------------------------------------------------------------------------
>>> Adventure Time http://theholenearthecenteroftheworld.com/
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Mayan EDMS" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to

>>> mayan-edms+unsubscribe@googlegroups.com.

>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Mayan EDMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to mayan-edms+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.



--
The idea is that a beautiful image is frameable. Everything you need
to see is there: It’s everything you want, and it’s very pleasing
because there’s no extra information that you don’t get to see.
Everything’s in a nice package for you. But sublime art is
unframeable: It’s an image or idea that implies that there’s a bigger
image or idea that you can’t see: You’re only getting to look at a
fraction of it, and in that way it’s both beautiful and scary, because
it’s reminding you that there’s more that you don’t have access to.
It’s now sort of left the piece itself and it’s become your own
invention, so it’s personal as well as being scary as well as being
beautiful, which is what I really like about art like that.
-----------------------------------------------------------------------------------------------------------
Adventure Time http://theholenearthecenteroftheworld.com/

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to mayan-edms+unsubscribe@googlegroups.com.

[Roberto Rosario]

No worries, make sure you merge with mayan-edms/master before doing a pull request so that patches apply as cleanly as possible.  If there are no conflicts I can merge directly from github otherwise I have to do a manual merge and your patches might take longer to get merged. 

That is probably something good to put in the docs :)

 

On Friday, July 11, 2014 6:22:28 PM UTC-4, Paul Whipp wrote:

btw, I'm new to pull requests. Hope you didn't mind my experimenting with the contributors.rst.

On 12 July 2014 08:20, Paul Whipp <paul....@gmail.com> wrote:

It is a pleasure to contribute to what is looking like a very impressive package.

For our use case we need to incorporate Mayan into our existing sites. I'll begin working on that once the staff have completed their review of its functionality (assuming they approve it). I'll have to work out a process where I can keep a clean fork of mayan (to generate pull requests where I feel I can contribute further), any customisations not suitable for inclusion and our site specific stuff.

On 11 July 2014 11:13, Roberto Rosario <robert...> wrote:

No worries :)
Thanks for the help.

On Jul 9, 2014 1:16 AM, "Lachlan Musicman" <dat...@gmail.com> wrote:

Yes, I apologise for sending you on the appsembler path, my bad.


cheers
L.

On 9 July 2014 15:13, Roberto Rosario

>>> > email to mayan-edms+unsubscribe@googlegroups.com.

>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> The idea is that a beautiful image is frameable. Everything you need
>>> to see is there: It’s everything you want, and it’s very pleasing
>>> because there’s no extra information that you don’t get to see.
>>> Everything’s in a nice package for you. But sublime art is
>>> unframeable: It’s an image or idea that implies that there’s a bigger
>>> image or idea that you can’t see: You’re only getting to look at a
>>> fraction of it, and in that way it’s both beautiful and scary, because
>>> it’s reminding you that there’s more that you don’t have access to.
>>> It’s now sort of left the piece itself and it’s become your own
>>> invention, so it’s personal as well as being scary as well as being
>>> beautiful, which is what I really like about art like that.
>>>
>>> -----------------------------------------------------------------------------------------------------------
>>> Adventure Time http://theholenearthecenteroftheworld.com/
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Mayan EDMS" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to

>>> mayan-edms+unsubscribe@googlegroups.com.

>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Mayan EDMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to mayan-edms+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.



--
The idea is that a beautiful image is frameable. Everything you need
to see is there: It’s everything you want, and it’s very pleasing
because there’s no extra information that you don’t get to see.
Everything’s in a nice package for you. But sublime art is
unframeable: It’s an image or idea that implies that there’s a bigger
image or idea that you can’t see: You’re only getting to look at a
fraction of it, and in that way it’s both beautiful and scary, because
it’s reminding you that there’s more that you don’t have access to.
It’s now sort of left the piece itself and it’s become your own
invention, so it’s personal as well as being scary as well as being
beautiful, which is what I really like about art like that.
-----------------------------------------------------------------------------------------------------------
Adventure Time http://theholenearthecenteroftheworld.com/

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/300U2OswhW0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to mayan-edms+unsubscribe@googlegroups.com.

[Paul Whipp]

I should have thought of that, thanks.

To unsubscribe from this group and all its topics, send an email to mayan-edms+...@googlegroups.com.

[Scott Graham]

I am trying to install Mayan-edms on Ubuntu 14.04 Desktop in an attempt to demo it.
I followed the installation instructions and have got it running.
I have been able to load documents and view the thumbnails of the first page of the loaded documents.
But I have found that it will core dump when I click on the file name in the Documents view or when I submit a document to the OCR queue.
Would I be better off installing on the Server version?
 I am new to Django and Python but do work in the field.  I am doing this as a volunteer, any suggestions would be helpful.

thanks,
        -Scott

[Paul Whipp]

Hi Scott,

I have it running on 14.04 desktop so I don't think trying the server version will make a difference. I haven't used the OCR features but everything else seems to work fine.

Not sure I can help you with your core dump but it's content may shed more light on the problem.

[Scott Graham]

Thanks for your response.
I see the message:
Segmentation fault (core dumped)
(venv)ubuntu@ubuntu-Vostro-200:~$
But I do not find a file.

I am thinking that is must be something more basic about the install that I am not doing correctly.
For instance, I read in the requirements:
Execute pip install -r requirements/production.txt to install the python/django dependencies automatically.
I did not do this. I don't see where the requirements/production.txt file is coming from.
or  perhaps I need something done in Setup with Metadata Sets or Metadata Types.

Regards,
-Scott

[Scott Graham]

From looking at the syslog, I have found that the core dumps are occurring with error 4, 5 and 6 in libgs.sl.9.10.

-Scott

[Scott Graham]

Correction:
From looking at the syslog, I have found that the core dumps are occurring with error 4, 5 and 6 in libgs.so.9.10.

-Scott

[Roberto Rosario]

Looks like issue #23 (https://github.com/mayan-edms/mayan-edms/issues/23). Tim found some discussions regarding calling executables from inside a Django view, it seems to cause unexpected memory leaks and memory corruption. Being a Django issue we can't fix it, but are finding a way to work around it and at the same time increase the scalability of Mayan ( https://github.com/mayan-edms/mayan-edms/issues/57). This should make it into the next version.

On Oct 5, 2014 7:57 PM, "Scott Graham" <toxm...@gmail.com> wrote:

From looking at the syslog, I have found that the core dumps are occurring with error 4, 5 and 6 in libgs.sl.9.10.

-Scott

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+...@googlegroups.com.