Re: [mezzanine-users] Using Wrap Bootstrap Theme with Mezzanine

2014-03-30 Thread Ola
Thanks, This is what I am looking for. Great tutorial

On Saturday, March 29, 2014 2:36:52 PM UTC-5, Josh Cartmell wrote:

 Hey Ola, if you haven't seen it, 
 http://bitofpixels.com/blog/mezzatheming-creating-mezzanine-themes-part-1-basehtml/might
  help.  It's a series of blog posts about creating themes for 
 Mezzanine.  What you got from wrapbootstrap is just html/css/js so you 
 still need to do all the django templating and necessary backend code.


 On Sat, Mar 29, 2014 at 6:15 AM, Ola ola.d...@gmail.com javascript:wrote:

 I bought a theme 
 https://wrapbootstrap.com/theme/unify-responsive-website-template-WB0412697, 
 that 
 I would like to use with mezzanine but I am confused on how to go about it. 
 I would appreciate a clear instructions on how to go about achieving this. 
 I have read some of the tutorials on this but I am still confused. Thanks 
 in advance. 
  
 -- 
 You received this message because you are subscribed to the Google Groups 
 Mezzanine Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to mezzanine-use...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[mezzanine-users] Re: Tried 3-4 heroku deployment tutorials but stuck on each one.

2014-03-30 Thread Ben Havilland
Hi all,
I just joined the group.  Kyle, it appears you have moved on but if anybody 
else is needs the current working Mezzanine/Heroku setup I've updated my 
tutorial and it addresses/fixes KeyError: u'ENGINE' the error you were 
getting.

I just ran through it from scratch with the latest packages with success:
http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/

There was a problem in the settings.py with the placement of the local 
settings and dynamic settings sections in the tutorial code.

Ben

On Tuesday, March 25, 2014 11:36:26 AM UTC-7, Kyle Pennell wrote:

 Hey all,
 Would love to get some help here if you could.  Hit the wall on what I can 
 do/try.

 I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
 triedJosh's tutorialhttps://gist.github.com/joshfinnie/4046138, 
 Ben's 
 Tutorialhttp://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/, 
 searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
 and interesting bugs on each one.

 So I'm trying Steven Elliot's tutorial http://stevenelliottjr.github.io/. 
  I reasoned that it was the newest (15 days ago) and might work better. 
  He's been extremely helpful on Twitter.

 Hit this roadblock here:


 (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic  
 
  

 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
 1.5 requires
 . Will fall back to the domains configured as sites.
   warn(You haven't defined the ALLOWED_HOSTS settings, which 

 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
   warn(TIME_ZONE setting is not set, using closest match: %s % tz)
 Traceback (most recent call last):
   File manage.py, line 29, in module
 execute_from_command_line(sys.argv)

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py,
  line 399, in execute_from_command_line
 utility.execute()

   File 
 /home/kpennell/mezz-site/mezzenv/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/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py,
  line 261, in fetch_command
 commands = get_commands()

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py,
  line 107, in get_commands
 apps = settings.INSTALLED_APPS

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py,
  line 54, in __getattr__
 self._setup(name)

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py,
  line 49, in _setup
 self._wrapped = Settings(settings_module)

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py,
  line 128, in __init__
 mod = importlib.import_module(self.SETTINGS_MODULE)

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/utils/importlib.py,
  line 40, in import_module
 __import__(name)
   File /home/kpennell/mezz-site/settings.py, line 442, in module
 set_dynamic_settings(globals())

   File 
 /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py,
  line 184, in set_dynamic_settings
 shortname = db[ENGINE].split(.)[-1]
 KeyError: u'ENGINE'


 So something with collect static doesn't work.  Something to do with 
 set_dynamic_settings.  I copied his tut verbatim and cloned the project he 
 gave me and both hit the snag there.

 I can post the code here if you want but thought pushing to github would 
 be easier:

 https://github.com/kpennell/mezz-try



 Any ideas?




-- 
You received this message because you are subscribed to the Google Groups 
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-30 Thread Stephen McDonald
I can't reproduce this - just did deploy of Mezzanine 3.0.9 to a fresh
ubuntu 12.04 machine without any issue.

Only thing I can think of is some mismatch between ALLOWED_HOSTS, Site
objects, and NGINX config - triple check those since the behaviour changes
with DEBUG False.


On Sat, Mar 29, 2014 at 5:25 AM, Josh Cartmell joshcar...@gmail.com wrote:

 I'm working on putting a dev server up for a client (to show them my
 progress) and figured I could do that quickly with the bundled fabfile and
 a VPS from Digital Ocean.  I'm using essentially unmodified deploy config
 (I commented out some SSL stuff in the nginx config) and the VPS is 64 bit
 Ubuntu 12.0.4.

 If I set DEBUG = True the site runs fine, but when it is false the site
 just says Internal Server Error.

 I've checked the nginx and supervisor logs and nothing shows up in either
 when the site produces the error.  Does gunicorn have a logfile and if so
 where is it?

 I also tried 64 bit Debian 7, and that also resulted in Internal Server
 Errors.

 Thanks!

 --
 You received this message because you are subscribed to the Google Groups
 Mezzanine Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to mezzanine-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-30 Thread Josh Cartmell
Thanks for giving it a shot Steve!  I didn't get it to work yet (since it
was just a non production demo I was satisfied to leave it with DEBUG True).

I'll triple check those things in the morning and let you know how it goes.

By the way, does gunicorn have a log of it's own or is it logged with nginx
and/or supervisor?


On Sun, Mar 30, 2014 at 4:16 PM, Stephen McDonald st...@jupo.org wrote:

 I can't reproduce this - just did deploy of Mezzanine 3.0.9 to a fresh
 ubuntu 12.04 machine without any issue.

 Only thing I can think of is some mismatch between ALLOWED_HOSTS, Site
 objects, and NGINX config - triple check those since the behaviour changes
 with DEBUG False.


 On Sat, Mar 29, 2014 at 5:25 AM, Josh Cartmell joshcar...@gmail.comwrote:

 I'm working on putting a dev server up for a client (to show them my
 progress) and figured I could do that quickly with the bundled fabfile and
 a VPS from Digital Ocean.  I'm using essentially unmodified deploy config
 (I commented out some SSL stuff in the nginx config) and the VPS is 64 bit
 Ubuntu 12.0.4.

 If I set DEBUG = True the site runs fine, but when it is false the site
 just says Internal Server Error.

 I've checked the nginx and supervisor logs and nothing shows up in either
 when the site produces the error.  Does gunicorn have a logfile and if so
 where is it?

 I also tried 64 bit Debian 7, and that also resulted in Internal Server
 Errors.

 Thanks!

 --
 You received this message because you are subscribed to the Google Groups
 Mezzanine Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to mezzanine-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 --
 Stephen McDonald
 http://jupo.org

 --
 You received this message because you are subscribed to the Google Groups
 Mezzanine Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to mezzanine-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.