Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

import config error #425

Closed
chakrihacker opened this issue Jan 13, 2017 · 8 comments
Closed

import config error #425

chakrihacker opened this issue Jan 13, 2017 · 8 comments

Comments

@chakrihacker
Copy link

I am using ubuntu 16.04 and my vagrantbox provision failed to run setup.sh so I ran it manually and I had couple of errors (installing setuptools and pyasn1) and now I am having import error

Traceback (most recent call last):
File "bin/create-db", line 9, in
from inbox.config import config
ImportError: No module named config

@ronnietucker
Copy link

ronnietucker commented Jan 15, 2017

Same here.

Finished installing dependencies.
Copying default development configuration to /etc/inboxapp
Copying default secrets configuration to /etc/inboxapp
Copying default mysql configuration to /etc/mysql/conf.d
2017-01-15T17:56:58.165185Z mysqld_safe Logging to syslog.
2017-01-15T17:56:58.169599Z mysqld_safe Logging to '/var/log/mysql/error.log'.
2017-01-15T17:56:58.221094Z mysqld_safe A mysqld process already exists
Traceback (most recent call last):
  File "bin/create-db", line 9, in <module>
    from inbox.config import config
ImportError: No module named config

Installing on Ubuntu 16.10. No VM using instructions from: http://techblog.danielpellarini.com/sysadmin/how-to-install-the-nylas-sync-engine-on-ubuntu-server/

@jacobduba
Copy link

+1

1 similar comment
@ajcollett
Copy link

+1

@itsjef
Copy link

itsjef commented Jan 17, 2017

+1

how do I work through this?

@ronnietucker
Copy link

Still no luck with this, but it sounds like the new versions of Nylar won't need the sync engine.

@jacobduba
Copy link

yea i cant wait until nylas basic comes out on linux.

@itsjef
Copy link

itsjef commented Jan 18, 2017

There is a workaround at #427. Works for me 😄

@chakrihacker
Copy link
Author

Since We got workaround I am closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants