Re: [mezzanine-users] Re: Where are Mezzanine's files?
Ah thank you! Forgot all about "view" - worked! sometimes I just like to be able to click to see all the files instead of having to type commands in the Terminal On Saturday, May 9, 2015 at 8:53:59 PM UTC-4, Mark Phillips wrote: > > There is a setting under view to display hidden files and folders. Just > select that, and you will see the .virtualenv folder. If it isn't under > view, try the other menus...Sorry not at a Ubuntu terminal. What you are > looking for is "hidden files". > > Mark > On May 9, 2015 12:15 PM, > wrote: > >> Ok I was able to get to them via Terminal, however... >> /.virtualenvs/somedir/local/lib/python2.7/site-packages/mezzanine$ >> >> Is there a way to navigate to them in Ubuntu 14.04 GUI for for folders >> and files? Finding that rather difficult because of the virtualenv :( >> >> On Saturday, May 9, 2015 at 2:37:39 PM UTC-4, automo...@gmail.com wrote: >>> >>> When installed via pip in a virtualenv on Ubuntu 14.04 ? >>> >> -- >> 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/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.
Re: [mezzanine-users] Re: SSL problem
Hi Paullo, I'm not sure if anyone here is going to have answers for you.
It's very likely an nginx issue. AFAIK by the time a request makes it to
Mezzanine it's already been decrypted and the SSL handshake has already
occurred.
Did you deploy directly with the included fabfile? if so did you deploy to
a completely fresh system?
If you aren't too far in I would recommend trying a fresh deploy.
Django 1.8 isn't officially supported yet (that's coming soon) so it is
possible you have uncovered a bug in the fabfile, but I think that's
unlikely because nginx shouldn't care what version of Django you are using.
On Sat, May 9, 2015 at 10:29 AM, Paullo wrote:
> And my settings.py:
>
> SSL_ENABLED = True
> SSL_FORCE_URL_PREFIXES = ("/admin", "/account")
> SSL_FORCE_HOST = "www.mrphunt.net"
> # SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTOCOL', 'https')
>
> I've tried with and without SECURE_PROXY_SSL_HEADER using
> 'HTTP_X_FORWARDED_PROTOCOL' and 'HTTP_X_FORWARDED_PROT' (Seen both in
> different web pages/forums...) head hurts now.
>
>
>
>
> On Saturday, 9 May 2015 15:16:50 UTC+1, Paullo wrote:
>
>> Hi,
>>
>> I'm in the process of testing Mezzanine with Django 1.8/Python 3.4. I've
>> been trying to get SSL working for the admin section. I'm fairly new to
>> nginx/supervisor so I guess it's a config problem, hopefully someone here
>> can tell me how I'm being stoopid :) Apologies if this isn't mezzanine
>> specific.
>>
>> I can't find any errors in logs except for this nginx error which occurs
>> when the browser eventually gives up trying to load the /admin page:-
>>
>> 2015/05/09 14:31:03 [info] 9769#0: *60 peer closed connection in SSL
>> handshake while SSL handshaking to upstream, client: 80.192.66.17, server:
>> www.mrphunt.net, request: "GET /admin/ HTTP/1.1", upstream:
>> "https://unix:/home/paul/webapps/mrphunt/mrphunt/gunicorn.sock:/admin/";,
>> host: "www.mrphunt.net"
>>
>>
>> My nginx.conf is pretty much the default fabfile configuration except i'm
>> redirecting to the www version from the non-www version.
>>
>> upstream mrphunt {
>> server unix:/home/paul/webapps/mrphunt/mrphunt/gunicorn.sock
>> fail_timeout=0;
>> }
>>
>> server {
>> server_name mrphunt.net;
>> return 301 $scheme://www.mrphunt.net$request_uri;
>> }
>>
>> server {
>>
>> listen 80;
>> listen 443 ssl;
>> server_name www.mrphunt.net;
>> client_max_body_size 10M;
>> keepalive_timeout15;
>> error_log /home/paul/logs/mrphunt_error_nginx.log info;
>> access_log /home/paul/logs/mrphunt_access_nginx.log;
>>
>> ssl on;
>> ssl_certificate conf/mrphunt.crt;
>> ssl_certificate_key conf/mrphunt.key;
>> ssl_session_cacheshared:SSL:10m;
>> ssl_session_timeout 10m;
>> ssl_ciphers
>> ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;
>> ssl_prefer_server_ciphers on;
>>
>> # Deny illegal Host headers
>> #if ($host !~* ^(mrphunt|mrphunt.net|www.mrphunt.net)$) {
>> if ($host !~* ^(www.mrphunt.net)$) {
>> return 444;
>> }
>>
>> location / {
>> proxy_redirect off;
>> proxy_set_headerHost$host;
>> proxy_set_headerX-Real-IP $remote_addr;
>> proxy_set_headerX-Forwarded-For
>> $proxy_add_x_forwarded_for;
>> proxy_set_headerX-Forwarded-Protocol$scheme;
>> proxy_pass http://mrphunt;
>> }
>>
>> location /static/ {
>> root/home/paul/webapps/mrphunt/mrphunt;
>> access_log off;
>> log_not_found off;
>> expires 30d;
>> }
>>
>> location /robots.txt {
>> root/home/paul/webapps/mrphunt/mrphunt/static;
>> access_log off;
>> log_not_found off;
>> }
>>
>> location /favicon.ico {
>> root/home/paul/webapps/mrphunt/mrphunt/static/img;
>> access_log off;
>> log_not_found off;
>> }
>> }
>>
>> gunicorn config:
>>
>> from __future__ import unicode_literals
>> import multiprocessing
>>
>> bind = "unix:/home/paul/webapps/mrphunt/mrphunt/gunicorn.sock"
>> workers = 2
>> errorlog = "/home/paul/logs/mrphunt_error.log"
>> loglevel = "error"
>> proc_name = "mrphunt"
>>
>>
>>
>>
>> My /etc/supervisor/conf.d/mrphunt.conf:
>>
>>
>> [pr
Re: [mezzanine-users] How i can add Adwords conversion code to a page and Remarketing code to whole site??
Hi Abid, you could potentially add the conversion code to the content section of a page. To add re-marketing code to the entire site you would need access to the server so that you could modify the templates. On Mon, May 11, 2015 at 1:19 AM, Abid Ali wrote: > Hi Guys, > > I am new to this platform and need your expert opinion or suggestions. > > I want to add Adwords conversion code to a page and Remarketing code to > whole site. So how can I accomplish this. I've only Mezzanine admin user > password. > > 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/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.
Re: [mezzanine-users] Re: Where are Mezzanine's files?
Hey automativeace, before you go to far I want to point out that directly editing Mezzanine's files will cause you pain later when you want or need to upgrade. If you are just looking at the files great, but if you are working on developing a Mezzanine site I would recommend learning more about how to customize Mezzanine without touching it's codebase. Good luck! On Mon, May 11, 2015 at 11:22 AM, wrote: > Ah thank you! Forgot all about "view" - worked! > > sometimes I just like to be able to click to see all the files instead of > having to type commands in the Terminal > > On Saturday, May 9, 2015 at 8:53:59 PM UTC-4, Mark Phillips wrote: >> >> There is a setting under view to display hidden files and folders. Just >> select that, and you will see the .virtualenv folder. If it isn't under >> view, try the other menus...Sorry not at a Ubuntu terminal. What you are >> looking for is "hidden files". >> >> Mark >> On May 9, 2015 12:15 PM, wrote: >> >>> Ok I was able to get to them via Terminal, however... >>> /.virtualenvs/somedir/local/lib/python2.7/site-packages/mezzanine$ >>> >>> Is there a way to navigate to them in Ubuntu 14.04 GUI for for folders >>> and files? Finding that rather difficult because of the virtualenv :( >>> >>> On Saturday, May 9, 2015 at 2:37:39 PM UTC-4, automo...@gmail.com wrote: When installed via pip in a virtualenv on Ubuntu 14.04 ? >>> -- >>> 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/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. > -- 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] Introducing Mezzanine's Core Development Team
Hi all, Today I'm thrilled to announce the introduction of a core development team for Mezzanine. I've written a detailed post about it, please heave a read: http://blog.jupo.org/2015/05/11/introducing-mezzanines-core-development-team/ TLDR: The new team consists of myself, Josh Cartmell, Ken Bolton, Alex Hill, Ed Rivas, Mathias Ettinger, who have each made huge contributions to the project over several years. Please join me in welcoming them! -- 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.
[mezzanine-users] Re: Introducing Mezzanine's Core Development Team
So awesome! In New Zealand there is a Māori proverb that asks... He aha te mea nui (What is the most important thing?) the answer being... He tāngata, he tāngata, he tāngata (It is people, it is people, it is people!) Glad to be part of this community, with this group of core developers :-) g On Tuesday, 12 May 2015 09:20:44 UTC+12, Stephen McDonald wrote: > > Hi all, > > Today I'm thrilled to announce the introduction of a core development team > for Mezzanine. I've written a detailed post about it, please heave a read: > > > http://blog.jupo.org/2015/05/11/introducing-mezzanines-core-development-team/ > > TLDR: The new team consists of myself, Josh Cartmell, Ken Bolton, Alex > Hill, Ed Rivas, Mathias Ettinger, who have each made huge contributions to > the project over several years. > > Please join me in welcoming them! > > > -- > 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] Introducing Mezzanine's Core Development Team
Funny, I'd always thought there was a core team ;-) Well done folks and Steve, congrats on the new job! -- Regards, Iain. -- 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] Introducing Mezzanine's Core Development Team
I have always admired the professionalism of exactly these people - the team. Thanks for your great work. Well done. Looking forward to see more from you guys. -- 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.
