Re: [mezzanine-users] fab all runs, but cannot access mezzanine admin page

[Stephen McDonald]

To be clear - I say "forget the ports", which sounds like it entirely
contradicts the rest of my "read the docs and understand what these things
do" advice.

What I mean to say is forget thinking in terms of running a development
server, using a custom port etc - with the vagrant setup, you're working as
though you're deploying to a production server, using the same workflow.


On Tue, Mar 4, 2014 at 5:40 PM, Stephen McDonald  wrote:

> You shouldn't need to do any of that. Here's my vagrantfile:
>
> Vagrant.configure("2") do |config|
>   config.vm.box = "precise64"
>   config.vm.network :private_network, ip: "10.10.10.10"
> end
>
> Forget the ports. Your vagrant vm is synonymous with a production server -
> you're deploying to it, and the various layers of nginx and gunicorn should
> deal with it. SSH onto this server. Look at the config files deployed
> there. Read each of the corresponding project's own documentation on these
> config files, and what they mean.
>
>
>
>
> On Tue, Mar 4, 2014 at 5:30 PM, Jesse Carrigan  > wrote:
>
>> I tried forwarding a port from my host machine and got the same result.
>> With localhost:8080 forwarded to 80 on the guest machine, I get the message
>> from ngnix. Forwarding localhost:8080 to 8000, I get no response.
>>
>> --
>> 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/groups/opt_out.
>>
>
>
>
> --
> Stephen McDonald
> http://jupo.org
>



-- 
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/groups/opt_out.

Re: [mezzanine-users] fab all runs, but cannot access mezzanine admin page

[Stephen McDonald]

You shouldn't need to do any of that. Here's my vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "precise64"
  config.vm.network :private_network, ip: "10.10.10.10"
end

Forget the ports. Your vagrant vm is synonymous with a production server -
you're deploying to it, and the various layers of nginx and gunicorn should
deal with it. SSH onto this server. Look at the config files deployed
there. Read each of the corresponding project's own documentation on these
config files, and what they mean.




On Tue, Mar 4, 2014 at 5:30 PM, Jesse Carrigan
wrote:

> I tried forwarding a port from my host machine and got the same result.
> With localhost:8080 forwarded to 80 on the guest machine, I get the message
> from ngnix. Forwarding localhost:8080 to 8000, I get no response.
>
> --
> 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/groups/opt_out.
>



-- 
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/groups/opt_out.

Re: [mezzanine-users] fab all runs, but cannot access mezzanine admin page

[Jesse Carrigan]

I tried forwarding a port from my host machine and got the same result. 
With localhost:8080 forwarded to 80 on the guest machine, I get the message 
from ngnix. Forwarding localhost:8080 to 8000, I get no response.

-- 
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/groups/opt_out.

Re: [mezzanine-users] jquery resize error

[Stephen McDonald]

Yep I found where it was originally introduced, and that was the intention.

But it doesn't even work for me - I'm going to nuke it, so consider it
fixed next release.


On Tue, Mar 4, 2014 at 1:40 PM, Josh Cartmell  wrote:

> Off the top of my head I think it has something to do with
> resizing/centering editable popups when the window is resized.
>
>
> On Mon, Mar 3, 2014 at 4:19 PM, Stephen McDonald  wrote:
>
>> I don't recall the intention around this library's introduction - I'd be
>> more than happy to remove it if someone can work out why it's there and
>> that it's safe to remove.
>>
>>
>> On Tue, Mar 4, 2014 at 11:16 AM, Ross Laird  wrote:
>>
>>> I have finally got round to testing this out, and the fix does not
>>> actually work for me. The popups still do their thing, but the error
>>> persists.
>>>
>>>
>>>  On Wed, Feb 19, 2014 at 9:36 AM, Josh Cartmell wrote:
>>>
  No problem Ross, did you give it a try and if so did it work for you
 as well?


 On Tue, Feb 18, 2014 at 7:32 PM, Ross Laird  wrote:

> Thanks for your work on this, Josh. Much appreciated.
>
> On Tuesday, 18 February 2014 09:37:57 UTC-8, Josh Cartmell wrote:
>
>> I never worried about it too much since it only affected admins.  In
>> the past I've played around with popping up the editable form in a
>> bootstrap modal, but that requires the site to use Bootstrap, which
>> probably isn't a good assumption.
>>
>> I was just thinking (and tried it out which seemed to work) that we
>> could change ba-resize to define a baresize event, instead of overriding
>> jquery's default resize event.  Getting this working required two 
>> changes.
>> First change the beginning of https://github.com/stephenmcd/
>> mezzanine/blob/faa736a0b42a6d6a92db13b46b9d32
>> 2e2d5ffedc/mezzanine/core/static/mezzanine/js/jquery.ba-resize.min.jsfrom
>>
>> e=$.resize=$.extend($.resize,{})
>>
>> to
>>
>> e=$.baresize=$.extend($.baresize,{})
>>
>> Then change https://github.com/stephenmcd/mezzanine/blob/
>> faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
>> static/mezzanine/js/editable.js#L68 to:
>>
>> $('.editable-original').on('baresize', function(e) {
>>
>> I did this and although I didn't test things super thoroughly the
>> inline editing popups still pop up.
>>
>> There may be a better approach, but what do you guys think?
>>
>>
>>
>> On Mon, Feb 17, 2014 at 9:15 PM, Stephen McDonald wrote:
>>
>>> I can tell you one thing at least, it only occurring when logged in
>>> as an admin user is no mystery - the file only gets used for the live
>>> editing:
>>>
>>> https://github.com/stephenmcd/mezzanine/blob/master/
>>> mezzanine/core/templates/includes/editable_loader.html
>>>
>>> I can't speak for the rest of it, its introduction was 2 years ago:
>>>
>>> https://github.com/stephenmcd/mezzanine/commit/
>>> faa736a0b42a6d6a92db13b46b9d322e2d5ffedc
>>>
>>> Seems to be related to managing the position of the live editing
>>> overlay - would welcome throwing out the lib in question if there's a
>>> better approach.
>>>
>>>
>>>
>>> On Tue, Feb 18, 2014 at 4:11 PM, Ross Laird wrote:
>>>
 That's interesting -- yes, I see this error only when I am logged
 in as admin.
 I have installed some extra javascript (such as headroom.js and the
 prettify jQuery plugin), so one of those could be interacting with
 ba-resize. But it's tough for me to know how to debug this further. 
 It's
 not a huge issue, as no regular user to the site will experience this 
 error.


 On Monday, 17 February 2014 17:54:30 UTC-8, Josh Cartmell wrote:

> Hey Ross, I've seen this before.
>
> Tell me if I'm wrong but do you only see it when you log in as an
> admin?  In my experience, it had something to do with a jquery script
> trying to use the normal jquery resize functionality (
> https://api.jquery.com/resize/) and not working because ba-resize
> changes the way .resize works.
>
> Steve, I can't find/think of a concrete example off the top of my
> head, but if I do I'll definitely post it up.
>
>
> On Mon, Feb 17, 2014 at 5:36 PM, Stephen McDonald 
> wrote:
>
>> Any hints on how to reproduce?
>>
>>
>>  On Tue, Feb 18, 2014 at 11:59 AM, Ross Laird <
>> ro...@rosslaird.com> wrote:
>>
>>> I'm getting a javascript error ("Uncaught TypeError: cannot set
>>> property of 'w' undefined") with jquery.ba-resize.js, which is 
>>> included in
>>> the default Mezzanine setup. There is an open 
>>> issue 

[mezzanine-users] Re: fab all runs, but cannot access mezzanine admin page

[Jesse Carrigan]

Hi Ken,

Thank you for your help. I didn't get any different results from deploying. 
Here's a link to the gist:

https://gist.github.com/feanorancalime/9340725

I should point out that I'm using a local vm. I set this up using a private 
network which has the IP address listed as host in the gist. I wonder if 
that's contributing to the problem? Should I be forwarding a port to the 
vagrant instead? I see that in the Vagrant "Getting Started" section, but I 
thought I needed the static IP for Fabric to be able to deploy.

Jesse

On Sunday, March 2, 2014 5:47:24 PM UTC-8, Jesse Carrigan wrote:
>
> I'm hoping someone can help me. I've been trying for months to get 
> Mezzanine running on anything other than local (I gave up on it a while ago 
> and finally decided to try again recently). I've been following Ken 
> Bolton's excellent instructions, which introduced me to Vagrant (and for 
> which I'm very grateful - it's a fantastic tool).
>
> The story so far is that I've stripped back to the simplest thing I can 
> think of to attempt to get Mezzanine deploying, per Ken's post, and then go 
> from there. To that end, I downloaded the latest version and started a new, 
> empty project. That project, with the basics and nothing else, is running 
> locally using the built-in dev server.
>
> I then ran fab all to install to vagrant, which finished. However, when 
> trying to get to the admin page via 192.168.x.x:8000/admin, I get no 
> response. If I just access the browser via the vagrant's IP address, I get 
> the "Welcome to ngnix!" message. Looking at the running processes on 
> vagrant, it appears that all the pieces are running (ngnix, memcached, 
> gunicorn, etc). I'm guessing this means that something has gone wrong that 
> is preventing ngnix from passing requests on to Mezzanine, but I'm not sure 
> what.
>
> I really like Mezzanine, and I'd like to get it working. I'm struggling to 
> understand how the project, with no custom development at all, would fail 
> to deploy. If anyone could give me some pointers about how I might 
> troubleshoot this, such as what to look for and where, I would be grateful. 
>
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Stephen McDonald]

As for the original issue, there's a clear note early on in Mezzanine's
README covering the very steps necessary to avoid the problem you've hit:
https://github.com/stephenmcd/mezzanine/#dependencies

Ken's point was that if you spend the time up front understanding vagrant
and fabric, you'll find that these very steps are automatically handled for
you.

As for the introductory questions asked just now around how these tools
work, any reply given here would do an injustice to the excellent
documentation these projects have, as well as the tutorials that exist -
seek them out! Ken has posted references to this topic countless times on
the list before.





On Tue, Mar 4, 2014 at 3:06 PM, Tom Brander  wrote:

> So.. Are you suggesting using Fabric instead of Pip for an initial
> development install?? (seems to be at variance with the doc) but I'm trying
> too understand...
>
>
> On Monday, March 3, 2014 9:57:56 PM UTC-6, Kenneth Bolton wrote:
>
>> One great thing about the fabfile.py that ships with Mezzanine is that it
>> contains the best practices of a bunch of developers across a half-dozen
>> technologies – with no cruft – that can immediately go into version control
>> and grow with your application. If you opt not to use Fabric to manage your
>> deploy, use the default fabfile to guide whatever deployment or
>> provisioning solution you choose.
>>
>> The lines from the fabfile that should help Tabs:
>> https://github.com/stephenmcd/mezzanine/blob/master/
>> mezzanine/project_template/fabfile.py#L351-L352
>>
>>
>>
>>
>> On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald  wrote:
>>
>>> Mezzanine's fabric recipe was entirely developed using vagrant - it's
>>> actually a perfect match.
>>>
>>>
>>> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander  wrote:
>>>
 Ken, he is just trying to install on a vagrant instance, presumably to
 give him a Linux VM on Windows?? Fabric doe not apply (yet)
 I was going to recommend Anaconda on Windows (to eliminate vagrant )
 but it seems from a quick check, Anaconda has some issues with Pillows as
 well (surprise..) I'm a bit out of touch with the PIL/Pillows state of the
 art on Windows...

 On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:

> "Use Fabric for repeatable installations", I repeat.
>
>
> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote:
>
>> Looks like you are missing the C compiler and perhaps the associated
>> dev tools library...
>>
>>
>> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>>
>>> Hi Mezzanine community,
>>>
>>> I am new to the Framework and I am trying to Setup a simple site
>>> using it.
>>> I am following the instructions posted here () and Setting up
>>> everything
>>> using Vagrant as virtualization Environment.  Everything was going
>>> fine
>>> until I tried to install Mezzanine.
>>>
>>> When running (sudo) pip install Mezzanine, I get an error on Pillow.
>>>  This
>>> is the last part of the log where the error appears.  Any ideas on
>>> how to
>>> fix it?
>>>
>>> Requirement already satisfied (use --upgrade to upgrade):
>>> future==0.9.0
>>> in /home
>>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
>>> mezzanine)
>>> Downloading/unpacking pillow (from mezzanine)
>>>   Running setup.py egg_info for package pillow
>>>
>>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
>>>   Running setup.py egg_info for package pytz
>>>
>>> warning: no files found matching '*.pot' under directory 'pytz'
>>> warning: no previously-included files found matching
>>> 'test_zdump.py'
>>> Requirement already satisfied (use --upgrade to upgrade): six
>>> in /home/vagrant/.
>>> virtualenvs/blog/lib/python2.7/site-packages (from
>>> bleach>=1.4->mezzanine)
>>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
>>>   Running setup.py egg_info for package html5lib
>>>
>>> Downloading/unpacking oauthlib>=0.4.2 (from requests-
>>> oauthlib>=0.4->mezzanine)
>>>   Running setup.py egg_info for package oauthlib
>>>
>>> Installing collected packages: pillow, pytz, html5lib, oauthlib
>>>   Running setup.py install for pillow
>>>
>>> building 'PIL._imaging' extension
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
>>> -Wstrict-pro
>>> totypes -fPIC -DHAVE_LIBZ
>>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
>>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>>> -I/usr/includ
>>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
>>> i686-2.7/_imaging.o
>>>
>>> _imaging.c:76:20: fatal error: Python.h: No such file or
>>> directory
>>> compilation terminated.
>>> error: command 'gcc' failed with exit status 1
>>>  

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Tom Brander]

So.. Are you suggesting using Fabric instead of Pip for an initial 
development install?? (seems to be at variance with the doc) but I'm trying 
too understand...

On Monday, March 3, 2014 9:57:56 PM UTC-6, Kenneth Bolton wrote:
>
> One great thing about the fabfile.py that ships with Mezzanine is that it 
> contains the best practices of a bunch of developers across a half-dozen 
> technologies – with no cruft – that can immediately go into version control 
> and grow with your application. If you opt not to use Fabric to manage your 
> deploy, use the default fabfile to guide whatever deployment or 
> provisioning solution you choose.
>
> The lines from the fabfile that should help Tabs:
>
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L351-L352
>
>
>
>
> On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald 
> > wrote:
>
>> Mezzanine's fabric recipe was entirely developed using vagrant - it's 
>> actually a perfect match.
>>
>>
>> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander 
>> > wrote:
>>
>>> Ken, he is just trying to install on a vagrant instance, presumably to 
>>> give him a Linux VM on Windows?? Fabric doe not apply (yet)
>>> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but 
>>> it seems from a quick check, Anaconda has some issues with Pillows as well 
>>> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art 
>>> on Windows...
>>>
>>> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>>>
 "Use Fabric for repeatable installations", I repeat.


 On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander  wrote:

> Looks like you are missing the C compiler and perhaps the associated 
> dev tools library...
>  
>
> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>
>> Hi Mezzanine community, 
>>
>> I am new to the Framework and I am trying to Setup a simple site 
>> using it. 
>> I am following the instructions posted here () and Setting up 
>> everything 
>> using Vagrant as virtualization Environment.  Everything was going 
>> fine 
>> until I tried to install Mezzanine.   
>>
>> When running (sudo) pip install Mezzanine, I get an error on Pillow. 
>>  This 
>> is the last part of the log where the error appears.  Any ideas on 
>> how to 
>> fix it? 
>>
>> Requirement already satisfied (use --upgrade to upgrade): 
>> future==0.9.0 
>> in /home 
>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from 
>> mezzanine) 
>> Downloading/unpacking pillow (from mezzanine) 
>>   Running setup.py egg_info for package pillow 
>>
>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine) 
>>   Running setup.py egg_info for package pytz 
>>
>> warning: no files found matching '*.pot' under directory 'pytz' 
>> warning: no previously-included files found matching 
>> 'test_zdump.py' 
>> Requirement already satisfied (use --upgrade to upgrade): six 
>> in /home/vagrant/. 
>> virtualenvs/blog/lib/python2.7/site-packages (from 
>> bleach>=1.4->mezzanine) 
>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine) 
>>   Running setup.py egg_info for package html5lib 
>>
>> Downloading/unpacking oauthlib>=0.4.2 (from requests- 
>> oauthlib>=0.4->mezzanine) 
>>   Running setup.py egg_info for package oauthlib 
>>
>> Installing collected packages: pillow, pytz, html5lib, oauthlib 
>>   Running setup.py install for pillow 
>>
>> building 'PIL._imaging' extension 
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
>> -Wstrict-pro 
>> totypes -fPIC -DHAVE_LIBZ 
>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag 
>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
>> -I/usr/includ 
>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux- 
>> i686-2.7/_imaging.o 
>>
>> _imaging.c:76:20: fatal error: Python.h: No such file or 
>> directory 
>> compilation terminated. 
>> error: command 'gcc' failed with exit status 1 
>> Complete output from command 
>> /home/vagrant/.virtualenvs/blog/bin/python 
>>
>> -c " 
>> import 
>> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>>  
>>
>> y';exec(compile(open(__file__).read().replace('\r\n', '\n'), 
>> __file__, 'exec'))" 
>>  install --single-version-externally-managed --record 
>> /tmp/pip-gXn3KB- 
>> record/ins 
>> tall-record.txt --install- 
>> headers /home/vagrant/.virtualenvs/blog/include/site/p 
>> ython2.7: 
>> running install 
>>
>> running build 
>>
>> running build_py 
>>
>> running egg_info 
>>
>> writing Pillow.egg-info/PKG-INFO 
>>
>> writing top-level names to Pillow.eg

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Ken Bolton]

One great thing about the fabfile.py that ships with Mezzanine is that it
contains the best practices of a bunch of developers across a half-dozen
technologies – with no cruft – that can immediately go into version control
and grow with your application. If you opt not to use Fabric to manage your
deploy, use the default fabfile to guide whatever deployment or
provisioning solution you choose.

The lines from the fabfile that should help Tabs:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L351-L352




On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald  wrote:

> Mezzanine's fabric recipe was entirely developed using vagrant - it's
> actually a perfect match.
>
>
> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander  wrote:
>
>> Ken, he is just trying to install on a vagrant instance, presumably to
>> give him a Linux VM on Windows?? Fabric doe not apply (yet)
>> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but
>> it seems from a quick check, Anaconda has some issues with Pillows as well
>> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
>> on Windows...
>>
>> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>>
>>> "Use Fabric for repeatable installations", I repeat.
>>>
>>>
>>> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander  wrote:
>>>
 Looks like you are missing the C compiler and perhaps the associated
 dev tools library...


 On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>
> Hi Mezzanine community,
>
> I am new to the Framework and I am trying to Setup a simple site using
> it.
> I am following the instructions posted here () and Setting up
> everything
> using Vagrant as virtualization Environment.  Everything was going
> fine
> until I tried to install Mezzanine.
>
> When running (sudo) pip install Mezzanine, I get an error on Pillow.
>  This
> is the last part of the log where the error appears.  Any ideas on how
> to
> fix it?
>
> Requirement already satisfied (use --upgrade to upgrade):
> future==0.9.0
> in /home
> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
> mezzanine)
> Downloading/unpacking pillow (from mezzanine)
>   Running setup.py egg_info for package pillow
>
> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
>   Running setup.py egg_info for package pytz
>
> warning: no files found matching '*.pot' under directory 'pytz'
> warning: no previously-included files found matching
> 'test_zdump.py'
> Requirement already satisfied (use --upgrade to upgrade): six
> in /home/vagrant/.
> virtualenvs/blog/lib/python2.7/site-packages (from
> bleach>=1.4->mezzanine)
> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
>   Running setup.py egg_info for package html5lib
>
> Downloading/unpacking oauthlib>=0.4.2 (from requests-
> oauthlib>=0.4->mezzanine)
>   Running setup.py egg_info for package oauthlib
>
> Installing collected packages: pillow, pytz, html5lib, oauthlib
>   Running setup.py install for pillow
>
> building 'PIL._imaging' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-pro
> totypes -fPIC -DHAVE_LIBZ
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
> -I/usr/includ
> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
> i686-2.7/_imaging.o
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory
> compilation terminated.
> error: command 'gcc' failed with exit status 1
> Complete output from command 
> /home/vagrant/.virtualenvs/blog/bin/python
>
> -c "
> import
> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>
> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
> __file__, 'exec'))"
>  install --single-version-externally-managed --record
> /tmp/pip-gXn3KB-
> record/ins
> tall-record.txt --install-
> headers /home/vagrant/.virtualenvs/blog/include/site/p
> ython2.7:
> running install
>
> running build
>
> running build_py
>
> running egg_info
>
> writing Pillow.egg-info/PKG-INFO
>
> writing top-level names to Pillow.egg-info/top_level.txt
>
> writing dependency_links to Pillow.egg-info/dependency_links.txt
>
> warning: manifest_maker: standard file '-c' not found
>
>
>
> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>
> reading manifest template 'MANIFEST.in'
>
> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>
> running build_ext
>
> building 'PIL._imaging' extension
>
> gcc -pthread -fno-strict-al

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Tom Brander]

But doesn't he have to 1st get a PIP install somewhere?

On Monday, March 3, 2014 9:31:17 PM UTC-6, Stephen McDonald wrote:
>
> Mezzanine's fabric recipe was entirely developed using vagrant - it's 
> actually a perfect match.
>
>
> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander 
> > wrote:
>
>> Ken, he is just trying to install on a vagrant instance, presumably to 
>> give him a Linux VM on Windows?? Fabric doe not apply (yet)
>> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but 
>> it seems from a quick check, Anaconda has some issues with Pillows as well 
>> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art 
>> on Windows...
>>
>> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>>
>>> "Use Fabric for repeatable installations", I repeat.
>>>
>>>
>>> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander  wrote:
>>>
 Looks like you are missing the C compiler and perhaps the associated 
 dev tools library...
  

 On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>
> Hi Mezzanine community, 
>
> I am new to the Framework and I am trying to Setup a simple site using 
> it. 
> I am following the instructions posted here () and Setting up 
> everything 
> using Vagrant as virtualization Environment.  Everything was going 
> fine 
> until I tried to install Mezzanine.   
>
> When running (sudo) pip install Mezzanine, I get an error on Pillow. 
>  This 
> is the last part of the log where the error appears.  Any ideas on how 
> to 
> fix it? 
>
> Requirement already satisfied (use --upgrade to upgrade): 
> future==0.9.0 
> in /home 
> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from 
> mezzanine) 
> Downloading/unpacking pillow (from mezzanine) 
>   Running setup.py egg_info for package pillow 
>
> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine) 
>   Running setup.py egg_info for package pytz 
>
> warning: no files found matching '*.pot' under directory 'pytz' 
> warning: no previously-included files found matching 
> 'test_zdump.py' 
> Requirement already satisfied (use --upgrade to upgrade): six 
> in /home/vagrant/. 
> virtualenvs/blog/lib/python2.7/site-packages (from 
> bleach>=1.4->mezzanine) 
> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine) 
>   Running setup.py egg_info for package html5lib 
>
> Downloading/unpacking oauthlib>=0.4.2 (from requests- 
> oauthlib>=0.4->mezzanine) 
>   Running setup.py egg_info for package oauthlib 
>
> Installing collected packages: pillow, pytz, html5lib, oauthlib 
>   Running setup.py install for pillow 
>
> building 'PIL._imaging' extension 
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-pro 
> totypes -fPIC -DHAVE_LIBZ 
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag 
> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
> -I/usr/includ 
> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux- 
> i686-2.7/_imaging.o 
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory 
> compilation terminated. 
> error: command 'gcc' failed with exit status 1 
> Complete output from command 
> /home/vagrant/.virtualenvs/blog/bin/python 
>
> -c " 
> import 
> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p 
>
> y';exec(compile(open(__file__).read().replace('\r\n', '\n'), 
> __file__, 'exec'))" 
>  install --single-version-externally-managed --record 
> /tmp/pip-gXn3KB- 
> record/ins 
> tall-record.txt --install- 
> headers /home/vagrant/.virtualenvs/blog/include/site/p 
> ython2.7: 
> running install 
>
> running build 
>
> running build_py 
>
> running egg_info 
>
> writing Pillow.egg-info/PKG-INFO 
>
> writing top-level names to Pillow.egg-info/top_level.txt 
>
> writing dependency_links to Pillow.egg-info/dependency_links.txt 
>
> warning: manifest_maker: standard file '-c' not found 
>
>
>
> reading manifest file 'Pillow.egg-info/SOURCES.txt' 
>
> reading manifest template 'MANIFEST.in' 
>
> writing manifest file 'Pillow.egg-info/SOURCES.txt' 
>
> running build_ext 
>
> building 'PIL._imaging' extension 
>
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict- 
> prototy 
> pes -fPIC -DHAVE_LIBZ 
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging 
> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
> -I/usr/include -I 
> /usr/include/python2.7 -c _imaging.c -o 
> build/temp.linux-i686-2.7/_imaging.o 
>
>
> _imaging.c:76:20: fatal error:

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Stephen McDonald]

Mezzanine's fabric recipe was entirely developed using vagrant - it's
actually a perfect match.


On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander  wrote:

> Ken, he is just trying to install on a vagrant instance, presumably to
> give him a Linux VM on Windows?? Fabric doe not apply (yet)
> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but
> it seems from a quick check, Anaconda has some issues with Pillows as well
> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
> on Windows...
>
> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>
>> "Use Fabric for repeatable installations", I repeat.
>>
>>
>> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander  wrote:
>>
>>> Looks like you are missing the C compiler and perhaps the associated dev
>>> tools library...
>>>
>>>
>>> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:

 Hi Mezzanine community,

 I am new to the Framework and I am trying to Setup a simple site using
 it.
 I am following the instructions posted here () and Setting up
 everything
 using Vagrant as virtualization Environment.  Everything was going fine
 until I tried to install Mezzanine.

 When running (sudo) pip install Mezzanine, I get an error on Pillow.
  This
 is the last part of the log where the error appears.  Any ideas on how
 to
 fix it?

 Requirement already satisfied (use --upgrade to upgrade): future==0.9.0
 in /home
 /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
 mezzanine)
 Downloading/unpacking pillow (from mezzanine)
   Running setup.py egg_info for package pillow

 Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
   Running setup.py egg_info for package pytz

 warning: no files found matching '*.pot' under directory 'pytz'
 warning: no previously-included files found matching
 'test_zdump.py'
 Requirement already satisfied (use --upgrade to upgrade): six
 in /home/vagrant/.
 virtualenvs/blog/lib/python2.7/site-packages (from
 bleach>=1.4->mezzanine)
 Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
   Running setup.py egg_info for package html5lib

 Downloading/unpacking oauthlib>=0.4.2 (from requests-
 oauthlib>=0.4->mezzanine)
   Running setup.py egg_info for package oauthlib

 Installing collected packages: pillow, pytz, html5lib, oauthlib
   Running setup.py install for pillow

 building 'PIL._imaging' extension
 gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
 -Wstrict-pro
 totypes -fPIC -DHAVE_LIBZ
 -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
 ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
 -I/usr/includ
 e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
 i686-2.7/_imaging.o

 _imaging.c:76:20: fatal error: Python.h: No such file or directory
 compilation terminated.
 error: command 'gcc' failed with exit status 1
 Complete output from command /home/vagrant/.virtualenvs/blog/bin/python

 -c "
 import
 setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p

 y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
 __file__, 'exec'))"
  install --single-version-externally-managed --record /tmp/pip-gXn3KB-
 record/ins
 tall-record.txt --install-
 headers /home/vagrant/.virtualenvs/blog/include/site/p
 ython2.7:
 running install

 running build

 running build_py

 running egg_info

 writing Pillow.egg-info/PKG-INFO

 writing top-level names to Pillow.egg-info/top_level.txt

 writing dependency_links to Pillow.egg-info/dependency_links.txt

 warning: manifest_maker: standard file '-c' not found



 reading manifest file 'Pillow.egg-info/SOURCES.txt'

 reading manifest template 'MANIFEST.in'

 writing manifest file 'Pillow.egg-info/SOURCES.txt'

 running build_ext

 building 'PIL._imaging' extension

 gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
 -Wstrict-
 prototy
 pes -fPIC -DHAVE_LIBZ
 -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
 -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
 -I/usr/include -I
 /usr/include/python2.7 -c _imaging.c -o 
 build/temp.linux-i686-2.7/_imaging.o


 _imaging.c:76:20: fatal error: Python.h: No such file or directory

 compilation terminated.

 error: command 'gcc' failed with exit status 1

 
 Command /home/vagrant/.virtualenvs/blog/bin/python -c "import
 setuptools;__file_
 _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open

 (__fi
 le__).read(

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Tom Brander]

Ken, he is just trying to install on a vagrant instance, presumably to give 
him a Linux VM on Windows?? Fabric doe not apply (yet)
I was going to recommend Anaconda on Windows (to eliminate vagrant ) but it 
seems from a quick check, Anaconda has some issues with Pillows as well 
(surprise..) I'm a bit out of touch with the PIL/Pillows state of the art 
on Windows...

On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>
> "Use Fabric for repeatable installations", I repeat.
>
>
> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander 
> > wrote:
>
>> Looks like you are missing the C compiler and perhaps the associated dev 
>> tools library...
>>
>>
>> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>>
>>> Hi Mezzanine community, 
>>>
>>> I am new to the Framework and I am trying to Setup a simple site using 
>>> it. 
>>> I am following the instructions posted here () and Setting up everything 
>>> using Vagrant as virtualization Environment.  Everything was going fine 
>>> until I tried to install Mezzanine.   
>>>
>>> When running (sudo) pip install Mezzanine, I get an error on Pillow. 
>>>  This 
>>> is the last part of the log where the error appears.  Any ideas on how 
>>> to 
>>> fix it? 
>>>
>>> Requirement already satisfied (use --upgrade to upgrade): future==0.9.0 
>>> in /home 
>>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine) 
>>> Downloading/unpacking pillow (from mezzanine) 
>>>   Running setup.py egg_info for package pillow 
>>>
>>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine) 
>>>   Running setup.py egg_info for package pytz 
>>>
>>> warning: no files found matching '*.pot' under directory 'pytz' 
>>> warning: no previously-included files found matching 'test_zdump.py' 
>>> Requirement already satisfied (use --upgrade to upgrade): six 
>>> in /home/vagrant/. 
>>> virtualenvs/blog/lib/python2.7/site-packages (from 
>>> bleach>=1.4->mezzanine) 
>>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine) 
>>>   Running setup.py egg_info for package html5lib 
>>>
>>> Downloading/unpacking oauthlib>=0.4.2 (from requests- 
>>> oauthlib>=0.4->mezzanine) 
>>>   Running setup.py egg_info for package oauthlib 
>>>
>>> Installing collected packages: pillow, pytz, html5lib, oauthlib 
>>>   Running setup.py install for pillow 
>>>
>>> building 'PIL._imaging' extension 
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
>>> -Wstrict-pro 
>>> totypes -fPIC -DHAVE_LIBZ 
>>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag 
>>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
>>> -I/usr/includ 
>>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux- 
>>> i686-2.7/_imaging.o 
>>>
>>> _imaging.c:76:20: fatal error: Python.h: No such file or directory 
>>> compilation terminated. 
>>> error: command 'gcc' failed with exit status 1 
>>> Complete output from command /home/vagrant/.virtualenvs/blog/bin/python 
>>>
>>> -c " 
>>> import 
>>> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p 
>>>
>>> y';exec(compile(open(__file__).read().replace('\r\n', '\n'), 
>>> __file__, 'exec'))" 
>>>  install --single-version-externally-managed --record /tmp/pip-gXn3KB- 
>>> record/ins 
>>> tall-record.txt --install- 
>>> headers /home/vagrant/.virtualenvs/blog/include/site/p 
>>> ython2.7: 
>>> running install 
>>>
>>> running build 
>>>
>>> running build_py 
>>>
>>> running egg_info 
>>>
>>> writing Pillow.egg-info/PKG-INFO 
>>>
>>> writing top-level names to Pillow.egg-info/top_level.txt 
>>>
>>> writing dependency_links to Pillow.egg-info/dependency_links.txt 
>>>
>>> warning: manifest_maker: standard file '-c' not found 
>>>
>>>
>>>
>>> reading manifest file 'Pillow.egg-info/SOURCES.txt' 
>>>
>>> reading manifest template 'MANIFEST.in' 
>>>
>>> writing manifest file 'Pillow.egg-info/SOURCES.txt' 
>>>
>>> running build_ext 
>>>
>>> building 'PIL._imaging' extension 
>>>
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
>>> -Wstrict- 
>>> prototy 
>>> pes -fPIC -DHAVE_LIBZ 
>>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging 
>>> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
>>> -I/usr/include -I 
>>> /usr/include/python2.7 -c _imaging.c -o 
>>> build/temp.linux-i686-2.7/_imaging.o 
>>>
>>>
>>> _imaging.c:76:20: fatal error: Python.h: No such file or directory 
>>>
>>> compilation terminated. 
>>>
>>> error: command 'gcc' failed with exit status 1 
>>>
>>>  
>>> Command /home/vagrant/.virtualenvs/blog/bin/python -c "import 
>>> setuptools;__file_ 
>>> _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open 
>>>
>>> (__fi 
>>> le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install 
>>> --single- 
>>> version 
>>> -externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt 
>>> --install 
>>> -headers /home/vagrant/.virtualenvs/bl

Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant

[Ken Bolton]

"Use Fabric for repeatable installations", I repeat.


On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander  wrote:

> Looks like you are missing the C compiler and perhaps the associated dev
> tools library...
>
>
> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>
>> Hi Mezzanine community,
>>
>> I am new to the Framework and I am trying to Setup a simple site using
>> it.
>> I am following the instructions posted here () and Setting up everything
>> using Vagrant as virtualization Environment.  Everything was going fine
>> until I tried to install Mezzanine.
>>
>> When running (sudo) pip install Mezzanine, I get an error on Pillow.
>>  This
>> is the last part of the log where the error appears.  Any ideas on how to
>> fix it?
>>
>> Requirement already satisfied (use --upgrade to upgrade): future==0.9.0
>> in /home
>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine)
>> Downloading/unpacking pillow (from mezzanine)
>>   Running setup.py egg_info for package pillow
>>
>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
>>   Running setup.py egg_info for package pytz
>>
>> warning: no files found matching '*.pot' under directory 'pytz'
>> warning: no previously-included files found matching 'test_zdump.py'
>> Requirement already satisfied (use --upgrade to upgrade): six
>> in /home/vagrant/.
>> virtualenvs/blog/lib/python2.7/site-packages (from
>> bleach>=1.4->mezzanine)
>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
>>   Running setup.py egg_info for package html5lib
>>
>> Downloading/unpacking oauthlib>=0.4.2 (from requests-
>> oauthlib>=0.4->mezzanine)
>>   Running setup.py egg_info for package oauthlib
>>
>> Installing collected packages: pillow, pytz, html5lib, oauthlib
>>   Running setup.py install for pillow
>>
>> building 'PIL._imaging' extension
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
>> -Wstrict-pro
>> totypes -fPIC -DHAVE_LIBZ
>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>> -I/usr/includ
>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
>> i686-2.7/_imaging.o
>>
>> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>> compilation terminated.
>> error: command 'gcc' failed with exit status 1
>> Complete output from command /home/vagrant/.virtualenvs/blog/bin/python
>>
>> -c "
>> import
>> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>>
>> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
>> __file__, 'exec'))"
>>  install --single-version-externally-managed --record /tmp/pip-gXn3KB-
>> record/ins
>> tall-record.txt --install-
>> headers /home/vagrant/.virtualenvs/blog/include/site/p
>> ython2.7:
>> running install
>>
>> running build
>>
>> running build_py
>>
>> running egg_info
>>
>> writing Pillow.egg-info/PKG-INFO
>>
>> writing top-level names to Pillow.egg-info/top_level.txt
>>
>> writing dependency_links to Pillow.egg-info/dependency_links.txt
>>
>> warning: manifest_maker: standard file '-c' not found
>>
>>
>>
>> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>>
>> reading manifest template 'MANIFEST.in'
>>
>> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>>
>> running build_ext
>>
>> building 'PIL._imaging' extension
>>
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
>> prototy
>> pes -fPIC -DHAVE_LIBZ
>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
>> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>> -I/usr/include -I
>> /usr/include/python2.7 -c _imaging.c -o build/temp.linux-i686-2.7/_imaging.o
>>
>>
>> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>>
>> compilation terminated.
>>
>> error: command 'gcc' failed with exit status 1
>>
>> 
>> Command /home/vagrant/.virtualenvs/blog/bin/python -c "import
>> setuptools;__file_
>> _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open
>>
>> (__fi
>> le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-
>> version
>> -externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt
>> --install
>> -headers /home/vagrant/.virtualenvs/blog/include/site/python2.7 failed
>> with
>> erro
>> r code 1 in /home/vagrant/.virtualenvs/blog/build/pillow
>> Storing complete log in /home/vagrant/.pip/pip.log
>> (blog)vagrant@precise32:~/.virtualenvs/blog/bin$ dpkg-query -l *python*
>> Desired=Unknown/Install/Remove/Purge/Hold
>> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
>>
>> pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name   VersionDescription
>> +++-==-==-
>> 
>> ii  python 2.7.3-0ubuntu2 interactive high-level object-oriented
>> langu
>> (blog)vagrant@precise32:~

[mezzanine-users] Re: Installing Mezzanine on Vagrant

[Tom Brander]

Looks like you are missing the C compiler and perhaps the associated dev 
tools library...

On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>
> Hi Mezzanine community, 
>
> I am new to the Framework and I am trying to Setup a simple site using it. 
> I am following the instructions posted here () and Setting up everything 
> using Vagrant as virtualization Environment.  Everything was going fine 
> until I tried to install Mezzanine.   
>
> When running (sudo) pip install Mezzanine, I get an error on Pillow.  This 
> is the last part of the log where the error appears.  Any ideas on how to 
> fix it? 
>
> Requirement already satisfied (use --upgrade to upgrade): future==0.9.0 
> in /home 
> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine) 
> Downloading/unpacking pillow (from mezzanine) 
>   Running setup.py egg_info for package pillow 
>
> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine) 
>   Running setup.py egg_info for package pytz 
>
> warning: no files found matching '*.pot' under directory 'pytz' 
> warning: no previously-included files found matching 'test_zdump.py' 
> Requirement already satisfied (use --upgrade to upgrade): six 
> in /home/vagrant/. 
> virtualenvs/blog/lib/python2.7/site-packages (from bleach>=1.4->mezzanine) 
> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine) 
>   Running setup.py egg_info for package html5lib 
>
> Downloading/unpacking oauthlib>=0.4.2 (from requests- 
> oauthlib>=0.4->mezzanine) 
>   Running setup.py egg_info for package oauthlib 
>
> Installing collected packages: pillow, pytz, html5lib, oauthlib 
>   Running setup.py install for pillow 
>
> building 'PIL._imaging' extension 
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-pro 
> totypes -fPIC -DHAVE_LIBZ 
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag 
> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
> -I/usr/includ 
> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux- 
> i686-2.7/_imaging.o 
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory 
> compilation terminated. 
> error: command 'gcc' failed with exit status 1 
> Complete output from command 
> /home/vagrant/.virtualenvs/blog/bin/python 
> -c " 
> import 
> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p 
> y';exec(compile(open(__file__).read().replace('\r\n', '\n'), 
> __file__, 'exec'))" 
>  install --single-version-externally-managed --record /tmp/pip-gXn3KB- 
> record/ins 
> tall-record.txt --install- 
> headers /home/vagrant/.virtualenvs/blog/include/site/p 
> ython2.7: 
> running install 
>
> running build 
>
> running build_py 
>
> running egg_info 
>
> writing Pillow.egg-info/PKG-INFO 
>
> writing top-level names to Pillow.egg-info/top_level.txt 
>
> writing dependency_links to Pillow.egg-info/dependency_links.txt 
>
> warning: manifest_maker: standard file '-c' not found 
>
>
>
> reading manifest file 'Pillow.egg-info/SOURCES.txt' 
>
> reading manifest template 'MANIFEST.in' 
>
> writing manifest file 'Pillow.egg-info/SOURCES.txt' 
>
> running build_ext 
>
> building 'PIL._imaging' extension 
>
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict- 
> prototy 
> pes -fPIC -DHAVE_LIBZ 
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging 
> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
> -I/usr/include -I 
> /usr/include/python2.7 -c _imaging.c -o 
> build/temp.linux-i686-2.7/_imaging.o 
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory 
>
> compilation terminated. 
>
> error: command 'gcc' failed with exit status 1 
>
>  
> Command /home/vagrant/.virtualenvs/blog/bin/python -c "import 
> setuptools;__file_ 
> _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open 
>
> (__fi 
> le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single- 
> version 
> -externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt 
> --install 
> -headers /home/vagrant/.virtualenvs/blog/include/site/python2.7 failed 
> with 
> erro 
> r code 1 in /home/vagrant/.virtualenvs/blog/build/pillow 
> Storing complete log in /home/vagrant/.pip/pip.log 
> (blog)vagrant@precise32:~/.virtualenvs/blog/bin$ dpkg-query -l *python* 
> Desired=Unknown/Install/Remove/Purge/Hold 
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- 
> pend 
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) 
> ||/ Name   VersionDescription 
> +++-==-==- 
>  
> ii  python 2.7.3-0ubuntu2 interactive high-level object-oriented 
> langu 
> (blog)vagrant@precise32:~/.virtualenvs/blog/bin$ 
>
> By any case, is there any other site that instructs how to Setup the whole 
> Thing using Windows?  I think it would be faster for 

Re: [mezzanine-users] jquery resize error

[Josh Cartmell]

Off the top of my head I think it has something to do with
resizing/centering editable popups when the window is resized.


On Mon, Mar 3, 2014 at 4:19 PM, Stephen McDonald  wrote:

> I don't recall the intention around this library's introduction - I'd be
> more than happy to remove it if someone can work out why it's there and
> that it's safe to remove.
>
>
> On Tue, Mar 4, 2014 at 11:16 AM, Ross Laird  wrote:
>
>> I have finally got round to testing this out, and the fix does not
>> actually work for me. The popups still do their thing, but the error
>> persists.
>>
>>
>>  On Wed, Feb 19, 2014 at 9:36 AM, Josh Cartmell wrote:
>>
>>>  No problem Ross, did you give it a try and if so did it work for you
>>> as well?
>>>
>>>
>>> On Tue, Feb 18, 2014 at 7:32 PM, Ross Laird  wrote:
>>>
 Thanks for your work on this, Josh. Much appreciated.

 On Tuesday, 18 February 2014 09:37:57 UTC-8, Josh Cartmell wrote:

> I never worried about it too much since it only affected admins.  In
> the past I've played around with popping up the editable form in a
> bootstrap modal, but that requires the site to use Bootstrap, which
> probably isn't a good assumption.
>
> I was just thinking (and tried it out which seemed to work) that we
> could change ba-resize to define a baresize event, instead of overriding
> jquery's default resize event.  Getting this working required two changes.
> First change the beginning of https://github.com/stephenmcd/
> mezzanine/blob/faa736a0b42a6d6a92db13b46b9d32
> 2e2d5ffedc/mezzanine/core/static/mezzanine/js/jquery.ba-resize.min.jsfrom
>
> e=$.resize=$.extend($.resize,{})
>
> to
>
> e=$.baresize=$.extend($.baresize,{})
>
> Then change https://github.com/stephenmcd/mezzanine/blob/
> faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
> static/mezzanine/js/editable.js#L68 to:
>
> $('.editable-original').on('baresize', function(e) {
>
> I did this and although I didn't test things super thoroughly the
> inline editing popups still pop up.
>
> There may be a better approach, but what do you guys think?
>
>
>
> On Mon, Feb 17, 2014 at 9:15 PM, Stephen McDonald wrote:
>
>> I can tell you one thing at least, it only occurring when logged in
>> as an admin user is no mystery - the file only gets used for the live
>> editing:
>>
>> https://github.com/stephenmcd/mezzanine/blob/master/
>> mezzanine/core/templates/includes/editable_loader.html
>>
>> I can't speak for the rest of it, its introduction was 2 years ago:
>>
>> https://github.com/stephenmcd/mezzanine/commit/
>> faa736a0b42a6d6a92db13b46b9d322e2d5ffedc
>>
>> Seems to be related to managing the position of the live editing
>> overlay - would welcome throwing out the lib in question if there's a
>> better approach.
>>
>>
>>
>> On Tue, Feb 18, 2014 at 4:11 PM, Ross Laird wrote:
>>
>>> That's interesting -- yes, I see this error only when I am logged in
>>> as admin.
>>> I have installed some extra javascript (such as headroom.js and the
>>> prettify jQuery plugin), so one of those could be interacting with
>>> ba-resize. But it's tough for me to know how to debug this further. It's
>>> not a huge issue, as no regular user to the site will experience this 
>>> error.
>>>
>>>
>>> On Monday, 17 February 2014 17:54:30 UTC-8, Josh Cartmell wrote:
>>>
 Hey Ross, I've seen this before.

 Tell me if I'm wrong but do you only see it when you log in as an
 admin?  In my experience, it had something to do with a jquery script
 trying to use the normal jquery resize functionality (
 https://api.jquery.com/resize/) and not working because ba-resize
 changes the way .resize works.

 Steve, I can't find/think of a concrete example off the top of my
 head, but if I do I'll definitely post it up.


 On Mon, Feb 17, 2014 at 5:36 PM, Stephen McDonald 
 wrote:

> Any hints on how to reproduce?
>
>
>  On Tue, Feb 18, 2014 at 11:59 AM, Ross Laird  > wrote:
>
>> I'm getting a javascript error ("Uncaught TypeError: cannot set
>> property of 'w' undefined") with jquery.ba-resize.js, which is 
>> included in
>> the default Mezzanine setup. There is an open 
>> issue about
>> this at the jquery-resize repo, but it seems that the repo has not 
>> been
>> updated in four years. Anybody else have this issue, or any thoughts 
>> about
>> updating this add-on for Mezzanine?
>>
>> --
>> You received this message because you are subscribed to the
>> Google Groups "Mezzanine Users" gro

Re: [mezzanine-users] jquery resize error

[Stephen McDonald]

I don't recall the intention around this library's introduction - I'd be
more than happy to remove it if someone can work out why it's there and
that it's safe to remove.


On Tue, Mar 4, 2014 at 11:16 AM, Ross Laird  wrote:

> I have finally got round to testing this out, and the fix does not
> actually work for me. The popups still do their thing, but the error
> persists.
>
>
>  On Wed, Feb 19, 2014 at 9:36 AM, Josh Cartmell wrote:
>
>>  No problem Ross, did you give it a try and if so did it work for you as
>> well?
>>
>>
>> On Tue, Feb 18, 2014 at 7:32 PM, Ross Laird  wrote:
>>
>>> Thanks for your work on this, Josh. Much appreciated.
>>>
>>> On Tuesday, 18 February 2014 09:37:57 UTC-8, Josh Cartmell wrote:
>>>
 I never worried about it too much since it only affected admins.  In
 the past I've played around with popping up the editable form in a
 bootstrap modal, but that requires the site to use Bootstrap, which
 probably isn't a good assumption.

 I was just thinking (and tried it out which seemed to work) that we
 could change ba-resize to define a baresize event, instead of overriding
 jquery's default resize event.  Getting this working required two changes.
 First change the beginning of https://github.com/stephenmcd/
 mezzanine/blob/faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
 static/mezzanine/js/jquery.ba-resize.min.js from

 e=$.resize=$.extend($.resize,{})

 to

 e=$.baresize=$.extend($.baresize,{})

 Then change https://github.com/stephenmcd/mezzanine/blob/
 faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
 static/mezzanine/js/editable.js#L68 to:

 $('.editable-original').on('baresize', function(e) {

 I did this and although I didn't test things super thoroughly the
 inline editing popups still pop up.

 There may be a better approach, but what do you guys think?



 On Mon, Feb 17, 2014 at 9:15 PM, Stephen McDonald wrote:

> I can tell you one thing at least, it only occurring when logged in as
> an admin user is no mystery - the file only gets used for the live 
> editing:
>
> https://github.com/stephenmcd/mezzanine/blob/master/
> mezzanine/core/templates/includes/editable_loader.html
>
> I can't speak for the rest of it, its introduction was 2 years ago:
>
> https://github.com/stephenmcd/mezzanine/commit/
> faa736a0b42a6d6a92db13b46b9d322e2d5ffedc
>
> Seems to be related to managing the position of the live editing
> overlay - would welcome throwing out the lib in question if there's a
> better approach.
>
>
>
> On Tue, Feb 18, 2014 at 4:11 PM, Ross Laird wrote:
>
>> That's interesting -- yes, I see this error only when I am logged in
>> as admin.
>> I have installed some extra javascript (such as headroom.js and the
>> prettify jQuery plugin), so one of those could be interacting with
>> ba-resize. But it's tough for me to know how to debug this further. It's
>> not a huge issue, as no regular user to the site will experience this 
>> error.
>>
>>
>> On Monday, 17 February 2014 17:54:30 UTC-8, Josh Cartmell wrote:
>>
>>> Hey Ross, I've seen this before.
>>>
>>> Tell me if I'm wrong but do you only see it when you log in as an
>>> admin?  In my experience, it had something to do with a jquery script
>>> trying to use the normal jquery resize functionality (
>>> https://api.jquery.com/resize/) and not working because ba-resize
>>> changes the way .resize works.
>>>
>>> Steve, I can't find/think of a concrete example off the top of my
>>> head, but if I do I'll definitely post it up.
>>>
>>>
>>> On Mon, Feb 17, 2014 at 5:36 PM, Stephen McDonald wrote:
>>>
 Any hints on how to reproduce?


  On Tue, Feb 18, 2014 at 11:59 AM, Ross Laird 
 wrote:

> I'm getting a javascript error ("Uncaught TypeError: cannot set
> property of 'w' undefined") with jquery.ba-resize.js, which is 
> included in
> the default Mezzanine setup. There is an open 
> issue about
> this at the jquery-resize repo, but it seems that the repo has not 
> been
> updated in four years. Anybody else have this issue, or any thoughts 
> about
> updating this add-on for Mezzanine?
>
> --
> 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.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>



 --
 Stephen McDonald
 http

Re: [mezzanine-users] jquery resize error

[Ross Laird]

I have finally got round to testing this out, and the fix does not actually
work for me. The popups still do their thing, but the error persists.


On Wed, Feb 19, 2014 at 9:36 AM, Josh Cartmell  wrote:

> No problem Ross, did you give it a try and if so did it work for you as
> well?
>
>
> On Tue, Feb 18, 2014 at 7:32 PM, Ross Laird  wrote:
>
>> Thanks for your work on this, Josh. Much appreciated.
>>
>> On Tuesday, 18 February 2014 09:37:57 UTC-8, Josh Cartmell wrote:
>>
>>> I never worried about it too much since it only affected admins.  In the
>>> past I've played around with popping up the editable form in a bootstrap
>>> modal, but that requires the site to use Bootstrap, which probably isn't a
>>> good assumption.
>>>
>>> I was just thinking (and tried it out which seemed to work) that we
>>> could change ba-resize to define a baresize event, instead of overriding
>>> jquery's default resize event.  Getting this working required two changes.
>>> First change the beginning of https://github.com/stephenmcd/
>>> mezzanine/blob/faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
>>> static/mezzanine/js/jquery.ba-resize.min.js from
>>>
>>> e=$.resize=$.extend($.resize,{})
>>>
>>> to
>>>
>>> e=$.baresize=$.extend($.baresize,{})
>>>
>>> Then change https://github.com/stephenmcd/mezzanine/blob/
>>> faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
>>> static/mezzanine/js/editable.js#L68 to:
>>>
>>> $('.editable-original').on('baresize', function(e) {
>>>
>>> I did this and although I didn't test things super thoroughly the inline
>>> editing popups still pop up.
>>>
>>> There may be a better approach, but what do you guys think?
>>>
>>>
>>>
>>> On Mon, Feb 17, 2014 at 9:15 PM, Stephen McDonald wrote:
>>>
 I can tell you one thing at least, it only occurring when logged in as
 an admin user is no mystery - the file only gets used for the live editing:

 https://github.com/stephenmcd/mezzanine/blob/master/
 mezzanine/core/templates/includes/editable_loader.html

 I can't speak for the rest of it, its introduction was 2 years ago:

 https://github.com/stephenmcd/mezzanine/commit/
 faa736a0b42a6d6a92db13b46b9d322e2d5ffedc

 Seems to be related to managing the position of the live editing
 overlay - would welcome throwing out the lib in question if there's a
 better approach.



 On Tue, Feb 18, 2014 at 4:11 PM, Ross Laird wrote:

> That's interesting -- yes, I see this error only when I am logged in
> as admin.
> I have installed some extra javascript (such as headroom.js and the
> prettify jQuery plugin), so one of those could be interacting with
> ba-resize. But it's tough for me to know how to debug this further. It's
> not a huge issue, as no regular user to the site will experience this 
> error.
>
>
> On Monday, 17 February 2014 17:54:30 UTC-8, Josh Cartmell wrote:
>
>> Hey Ross, I've seen this before.
>>
>> Tell me if I'm wrong but do you only see it when you log in as an
>> admin?  In my experience, it had something to do with a jquery script
>> trying to use the normal jquery resize functionality (
>> https://api.jquery.com/resize/) and not working because ba-resize
>> changes the way .resize works.
>>
>> Steve, I can't find/think of a concrete example off the top of my
>> head, but if I do I'll definitely post it up.
>>
>>
>> On Mon, Feb 17, 2014 at 5:36 PM, Stephen McDonald wrote:
>>
>>> Any hints on how to reproduce?
>>>
>>>
>>>  On Tue, Feb 18, 2014 at 11:59 AM, Ross Laird 
>>> wrote:
>>>
 I'm getting a javascript error ("Uncaught TypeError: cannot set
 property of 'w' undefined") with jquery.ba-resize.js, which is 
 included in
 the default Mezzanine setup. There is an open 
 issue about
 this at the jquery-resize repo, but it seems that the repo has not been
 updated in four years. Anybody else have this issue, or any thoughts 
 about
 updating this add-on for Mezzanine?

 --
 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.

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

>>>
>>>
>>>
>>> --
>>> 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-use...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>

[mezzanine-users] Re: Restricting shop to active users only

[Eduardo Rivas]

Excellent! I think that's what Steve meant from the beginning. Regarding 
the sitemap, I was overriding Mezzanine's sitemap and returning a 
Product-free list, but signals seem like the right way to go here. Thanks a 
lot.

-- 
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/groups/opt_out.

Re: [mezzanine-users] Re: Restricting shop to active users only

[Josh Cartmell]

Hey Ed, you can also do something like
http://stackoverflow.com/a/5771286/593283, I'm not sure if that would be a
workable solution for you.

If you wanted to hide products across the board you could connect to the
product pre save signal and uncheck the box programatically.


On Mon, Mar 3, 2014 at 2:34 PM, Eduardo Rivas wrote:

> I investigated a little and apparently the login decorator is for views,
> not url patterns. I ended up using this little 
> middlewarethat lets me conveniently 
> define a list of url patterns for which login is
> required.
>
> Related question: is it possible to hide products from the sitemap without
> needing to manually uncheck the "Show in sitemap" box in every existing and
> new product?
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[mezzanine-users] SearchableManager.search returns only list?

[Lucian Corduneanu]

Hi, I've been reading the docs from 
http://mezzanine.jupo.org/docs/search-engine.html
There is a note saying: "search method returns a Django queryset", thus I 
should chain a filter() or order_by().

Product.objects.search(query).filter(vendor__id=66).order_by("-publish_date").

I'm using mezzanine 3.0.9 and cartridge 0.9.2, and to me it looks like 
SearchableManager.search is returning every time a sorted "all_results" 
list.

This line of code:

all_results.extend(queryset.search(*args, **kwargs)) 

is transforming the queryset into a list.

Is there something I'm missing? How can I apply filter and order on a 
queryset coming from search manager?

-- 
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/groups/opt_out.

[mezzanine-users] Re: Restricting shop to active users only

[Eduardo Rivas]

I investigated a little and apparently the login decorator is for views, 
not url patterns. I ended up using this little 
middlewarethat lets me conveniently 
define a list of url patterns for which login is 
required.

Related question: is it possible to hide products from the sitemap without 
needing to manually uncheck the "Show in sitemap" box in every existing and 
new product?

-- 
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/groups/opt_out.

[mezzanine-users] Re: step by step mezzanine deployment

[Ross Laird]

Postgresql authentication can be tricky.
You may need to make changes to your pg_hba.conf file. Like so:

# Database administrative login by Unix domain socket
local   all postgrespeer
# TYPE  DATABASEUSERADDRESS METHOD
# "local" is for Unix domain socket connections only
local   all all peer
# IPv4 local connections:
hostall all 127.0.0.1/32md5
# IPv6 local connections:
hostall all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication postgrespeer
#hostreplication postgres127.0.0.1/32md5

Also, this tutorial might help:

http://rosslaird.com/blog/building-a-project-with-mezzanine/



On Monday, 3 March 2014 04:01:46 UTC-8, Federico Bruni wrote:
>
> I'm opening a new thread and try to make the deploy of a simple test. 
> Let's see if I understand the basics...
>
> First of all, the DATABASES options are divided in 3 files:
>
> - local_settings.py: the setting for local development. By default, sqlite 
> is used. I wonder what's the best approach if I know that I want to deploy 
> on PostgreSQL on the server. Should I work on PostgreSQL locally as well?
> - live_settings.py: this also is pretty clear, it contains the server 
> settings (I found out that it can be left untouched, as long as settings.py 
> is complete)
> - settings.py: IIUC, any settings here will be overridden by the two 
> settings above, so I can ignore the DATABASE section. Is it correct?
>
> Now, I assume that Fabric will handle the migration from sqlite to 
> postgresql.
> So all I have to do to deploy is defining the FABRIC={} variables in 
> settings.py
>
> I've learned that I'd better split 'fab all' in three steps. I'm trying to 
> understand which options/settings are required for each step (it would be 
> nice to organize them this way, sequentially, in default settings.py):
>
> 1. fab install
> This is the easier part. It just installs the required packages on the 
> server.
> Options to be defined on FABRIC section of settings.py are: SSH_USER, 
> SSH_KEYPATH, HOSTS, LOCALE, SECRET_KEY, NEVERCACHE_KEY.
>
> 2. fab create
> Another note to add in the documentation is that a remote git/mercurial 
> server is needed.
> In this step I have to fill: VIRTUALENV_HOME, PROJECT_NAME, 
> REQUIREMENTS_PATH, REPO_URL, DB_PASS.
> I see that DB_PASS is shadowed so it's safe putting the password in the 
> file (repository is private, of course). Or there's a better method?
>
> 3. fab deploy
> I had nothing more to configure.
> This test just worked smoothly. No error.
>
> Now I should find out why my real project is failing. Maybe I could start 
> it from scratch step by step and see what happens.
> Anyway, I'd love to hear comments on above.. I may try writing a patch for 
> the documentation to help other users, even if my understanding of 
> mezzanine is still poor.
>

-- 
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/groups/opt_out.

[mezzanine-users] Installing Mezzanine on Vagrant

[Tabs]

Hi Mezzanine community,

I am new to the Framework and I am trying to Setup a simple site using it. 
I am following the instructions posted here () and Setting up everything 
using Vagrant as virtualization Environment.  Everything was going fine 
until I tried to install Mezzanine.  

When running (sudo) pip install Mezzanine, I get an error on Pillow.  This 
is the last part of the log where the error appears.  Any ideas on how to 
fix it?

Requirement already satisfied (use --upgrade to upgrade): future==0.9.0 
in /home
/vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine)
Downloading/unpacking pillow (from mezzanine)
  Running setup.py egg_info for package pillow

Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
  Running setup.py egg_info for package pytz

warning: no files found matching '*.pot' under directory 'pytz'
warning: no previously-included files found matching 'test_zdump.py'
Requirement already satisfied (use --upgrade to upgrade): six 
in /home/vagrant/.
virtualenvs/blog/lib/python2.7/site-packages (from bleach>=1.4->mezzanine)
Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
  Running setup.py egg_info for package html5lib

Downloading/unpacking oauthlib>=0.4.2 (from requests-
oauthlib>=0.4->mezzanine)
  Running setup.py egg_info for package oauthlib

Installing collected packages: pillow, pytz, html5lib, oauthlib
  Running setup.py install for pillow

building 'PIL._imaging' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-pro
totypes -fPIC -DHAVE_LIBZ 
-I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
-I/usr/includ
e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
i686-2.7/_imaging.o

_imaging.c:76:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
Complete output from command /home/vagrant/.virtualenvs/blog/bin/python 
-c "
import 
setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
y';exec(compile(open(__file__).read().replace('\r\n', '\n'), 
__file__, 'exec'))"
 install --single-version-externally-managed --record /tmp/pip-gXn3KB-
record/ins
tall-record.txt --install-
headers /home/vagrant/.virtualenvs/blog/include/site/p
ython2.7:
running install

running build

running build_py

running egg_info

writing Pillow.egg-info/PKG-INFO

writing top-level names to Pillow.egg-info/top_level.txt

writing dependency_links to Pillow.egg-info/dependency_links.txt

warning: manifest_maker: standard file '-c' not found



reading manifest file 'Pillow.egg-info/SOURCES.txt'

reading manifest template 'MANIFEST.in'

writing manifest file 'Pillow.egg-info/SOURCES.txt'

running build_ext

building 'PIL._imaging' extension

gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
prototy
pes -fPIC -DHAVE_LIBZ 
-I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
-I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include 
-I/usr/include -I
/usr/include/python2.7 -c _imaging.c -o build/temp.linux-i686-2.7/_imaging.o

_imaging.c:76:20: fatal error: Python.h: No such file or directory

compilation terminated.

error: command 'gcc' failed with exit status 1


Command /home/vagrant/.virtualenvs/blog/bin/python -c "import 
setuptools;__file_
_='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open
(__fi
le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-
version
-externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt 
--install
-headers /home/vagrant/.virtualenvs/blog/include/site/python2.7 failed with 
erro
r code 1 in /home/vagrant/.virtualenvs/blog/build/pillow
Storing complete log in /home/vagrant/.pip/pip.log
(blog)vagrant@precise32:~/.virtualenvs/blog/bin$ dpkg-query -l *python*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-

ii  python 2.7.3-0ubuntu2 interactive high-level object-oriented 
langu
(blog)vagrant@precise32:~/.virtualenvs/blog/bin$

By any case, is there any other site that instructs how to Setup the whole 
Thing using Windows?  I think it would be faster for me.

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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [mezzanine-users] can anyone suggest me some host which is Australia based and also mezzanine&django friendly?

[Danny]

On 3/03/2014 10:13 PM, lu zou wrote:

As above ,can anyone suggest me some host which is Australia based and
also mezzanine&django friendly? :)



Not sure about Django friendliness, or even how good these hosting 
providers are, but these are places I found in Australia which had 
reasonably priced VPS solutions.


http://www.vpsblocks.com.au
http://www.networkpresence.com.au
http://www.web24.com.au
https://www.echoman.com.au
http://www.ransomit.com.au/vps
http://www.crazydomains.com.au/virtual-servers/

However, most of them are still more expensive than, say, DigitalOcean 
and Webfaction. But if local hosting (and local support) is important to 
you, perhaps have a look and check for online reviews and their reputation.


Seeya. Danny.
--
Email: molo...@gmail.com

--
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/groups/opt_out.

Re: [mezzanine-users] step by step mezzanine deployment

[Federico Bruni]

Ah! Here's what I was missing!
Now I'm trying to manually sync the databases:

pg_dump -C -h localhost -U localuser dbname | psql -h remotehost -U
remoteuser dbname

But I have problem with the port 5432. I already tried to add ip_private to
listen_addresses in postgresql.conf, as suggested here:
http://stackoverflow.com/questions/19916720/psql-cant-connect-to-postgresql-server-postmaster-on-ip-and-port-5432

But it doesn't help:

psql: could not connect to server: Connection refused
Is the server running on host "xx.xx.xx.xx" and accepting
TCP/IP connections on port 5432?

pg_dump: [archiver (db)] connection to database "xx" failed:
fe_sendauth: no password supplied



2014-03-03 16:26 GMT+01:00 Ken Bolton :

> Fabric does not sync the content of the databases.
>
> Fabric does sync the database schemas!
>
>
> On Mon, Mar 3, 2014 at 8:03 AM, Federico Bruni  wrote:
>
>> 2014-03-03 13:01 GMT+01:00 Federico Bruni :
>>
>> Now I should find out why my real project is failing. Maybe I could start
>>> it from scratch step by step and see what happens.
>>>
>>
>> I've just one more test: added a page in my local project and then
>> launched 'fab deploy' to send the changes to the server database.
>> But nothing happens (I'm sure I've forced the reload of the page).
>>
>> So I've managed to reproduce my original problem. Local and deployment
>> databases are not synced when I launch 'fab deploy'.
>> No error if I manually launch 'python manage.py runserver' from the
>> virtualenv in the server (after 'sudo supervisorctl stop all').
>>
>>  --
>> 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/groups/opt_out.
>>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/FSCD3RAdLww/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] step by step mezzanine deployment

[Ken Bolton]

Fabric does not sync the content of the databases.

Fabric does sync the database schemas!


On Mon, Mar 3, 2014 at 8:03 AM, Federico Bruni  wrote:

> 2014-03-03 13:01 GMT+01:00 Federico Bruni :
>
> Now I should find out why my real project is failing. Maybe I could start
>> it from scratch step by step and see what happens.
>>
>
> I've just one more test: added a page in my local project and then
> launched 'fab deploy' to send the changes to the server database.
> But nothing happens (I'm sure I've forced the reload of the page).
>
> So I've managed to reproduce my original problem. Local and deployment
> databases are not synced when I launch 'fab deploy'.
> No error if I manually launch 'python manage.py runserver' from the
> virtualenv in the server (after 'sudo supervisorctl stop all').
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] first steps with fabric deployment

[Federico Bruni]

no error found


2014-03-03 13:22 GMT+01:00 :

> Did you try to run "python manage.py runserver" directly in your virtual
> env directory? And is there an error? I the port is in use you can try to
> stop the server by running supervisorctl stop all.
>
> ++
>
> On Friday, February 28, 2014 1:08:44 AM UTC+1, Federico Bruni wrote:
>>
>> 2014-02-26 13:18 GMT+01:00 :
>>
>> Yes, I think fab create has to restart from the beginning. One more
>>> advice, be sure that all Fabric settings in settings.py are completed
>>> (or as much as you can). I tried to leave the field REPO_URL empty and fab
>>> deploy didn't work until I set a real git repository.
>>
>>
>> Yes, I see that each time you run 'fab deploy' the git repository is
>> checked and pulled to get the updates.
>> I've followed your advice, added as many settings as possible and solved
>> an issue with the gunicorn file, see:
>> https://github.com/stephenmcd/mezzanine/issues/870
>>
>> Now the server is serving the contents, but... the database is still
>> wrong. All the static and theme files are correct (favicon, homepage), but
>> all the rest (other pages and access to admin) is wrong.
>> Something went wrong with manage.py migrate. How can I find the problem?
>> In the output I see many "Nothing to migrate".
>>
>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/KFgqkys6rUM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] step by step mezzanine deployment

[Federico Bruni]

2014-03-03 13:01 GMT+01:00 Federico Bruni :

> Now I should find out why my real project is failing. Maybe I could start
> it from scratch step by step and see what happens.
>

I've just one more test: added a page in my local project and then launched
'fab deploy' to send the changes to the server database.
But nothing happens (I'm sure I've forced the reload of the page).

So I've managed to reproduce my original problem. Local and deployment
databases are not synced when I launch 'fab deploy'.
No error if I manually launch 'python manage.py runserver' from the
virtualenv in the server (after 'sudo supervisorctl stop all').

-- 
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/groups/opt_out.

Re: [mezzanine-users] first steps with fabric deployment

[ourycl]

Did you try to run "python manage.py runserver" directly in your virtual 
env directory? And is there an error? I the port is in use you can try to 
stop the server by running supervisorctl stop all.

++ 

On Friday, February 28, 2014 1:08:44 AM UTC+1, Federico Bruni wrote:
>
> 2014-02-26 13:18 GMT+01:00 >:
>
>> Yes, I think fab create has to restart from the beginning. One more 
>> advice, be sure that all Fabric settings in settings.py are completed 
>> (or as much as you can). I tried to leave the field REPO_URL empty and fab 
>> deploy didn't work until I set a real git repository.
>
>
> Yes, I see that each time you run 'fab deploy' the git repository is 
> checked and pulled to get the updates.
> I've followed your advice, added as many settings as possible and solved 
> an issue with the gunicorn file, see:
> https://github.com/stephenmcd/mezzanine/issues/870
>
> Now the server is serving the contents, but... the database is still 
> wrong. All the static and theme files are correct (favicon, homepage), but 
> all the rest (other pages and access to admin) is wrong.
> Something went wrong with manage.py migrate. How can I find the problem? 
> In the output I see many "Nothing to migrate".
>
>

-- 
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/groups/opt_out.

[mezzanine-users] step by step mezzanine deployment

[Federico Bruni]

I'm opening a new thread and try to make the deploy of a simple test. Let's 
see if I understand the basics...

First of all, the DATABASES options are divided in 3 files:

- local_settings.py: the setting for local development. By default, sqlite 
is used. I wonder what's the best approach if I know that I want to deploy 
on PostgreSQL on the server. Should I work on PostgreSQL locally as well?
- live_settings.py: this also is pretty clear, it contains the server 
settings (I found out that it can be left untouched, as long as settings.py 
is complete)
- settings.py: IIUC, any settings here will be overridden by the two 
settings above, so I can ignore the DATABASE section. Is it correct?

Now, I assume that Fabric will handle the migration from sqlite to 
postgresql.
So all I have to do to deploy is defining the FABRIC={} variables in 
settings.py

I've learned that I'd better split 'fab all' in three steps. I'm trying to 
understand which options/settings are required for each step (it would be 
nice to organize them this way, sequentially, in default settings.py):

1. fab install
This is the easier part. It just installs the required packages on the 
server.
Options to be defined on FABRIC section of settings.py are: SSH_USER, 
SSH_KEYPATH, HOSTS, LOCALE, SECRET_KEY, NEVERCACHE_KEY.

2. fab create
Another note to add in the documentation is that a remote git/mercurial 
server is needed.
In this step I have to fill: VIRTUALENV_HOME, PROJECT_NAME, 
REQUIREMENTS_PATH, REPO_URL, DB_PASS.
I see that DB_PASS is shadowed so it's safe putting the password in the 
file (repository is private, of course). Or there's a better method?

3. fab deploy
I had nothing more to configure.
This test just worked smoothly. No error.

Now I should find out why my real project is failing. Maybe I could start 
it from scratch step by step and see what happens.
Anyway, I'd love to hear comments on above.. I may try writing a patch for 
the documentation to help other users, even if my understanding of 
mezzanine is still poor.

-- 
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/groups/opt_out.

[mezzanine-users] can anyone suggest me some host which is Australia based and also mezzanine&django friendly?

[lu zou]

As above ,can anyone suggest me some host which is Australia based and also 
mezzanine&django friendly? :)

-- 
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/groups/opt_out.