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

[Kyle Pennell]

I sadly couldn't figure it out and asked too many questions which
understandably frustrated people.  So I switched to Angular and Javascript
in general (better suited for my task anyway).

I highly recommend reading the docs as much as possible.

On Thu, Oct 2, 2014 at 4:47 AM, Guillermo Valle  wrote:

> I am also getting this same error. And Ben's tutorial hasn't solved it for
> me (I haven't followed it fully because I'm serving statics with Heroku not
> S3, but have followed everything that I thought would apply). The location
> of LOCAL and DYNAMIC SETTINGS doesn't seem to fix it for me :( Any other
> ideas?
>
>
> On Tuesday, March 25, 2014 7:36:26 PM UTC+1, Kyle Pennell wrote:
>>
>> Hey all,
>> Would love to get some help here if you could.  Hit the wall on what I
>> can do/try.
>>
>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've tried
>> Josh's tutorial <https://gist.github.com/joshfinnie/4046138>, Ben's
>> Tutorial
>> <http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/>,
>> searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique
>> and interesting bugs on each one.
>>
>> So I'm trying Steven Elliot's tutorial
>> <http://stevenelliottjr.github.io/>.  I reasoned that it was the newest
>> (15 days ago) and might work better.  He's been extremely helpful on
>> Twitter.
>>
>> Hit this roadblock here:
>>
>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py
>>>> collectstatic
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/
>>>> site-packages/mezzanine/utils/conf.py:51: UserWarning: You
>>>> haven't defined the ALLOWED_HOSTS settings, which Django 1.5 requires
>>>> . Will fall back to the domains configured as sites.
>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/
>>>> site-packages/mezzanine/utils/conf.py:59: UserWarning: TIME_
>>>> ZONE setting is not set, using closest match: Etc/UTC
>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>>> Traceback (most recent call last):
>>>>   File "manage.py", line 29, in 
>>>> execute_from_command_line(sys.argv)
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/core/management/__init_
>>>> _.py", line 399, in execute_from_command_line
>>>> utility.execute()
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/core/management/__init_
>>>> _.py", line 392, in execute
>>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/core/management/__init_
>>>> _.py", line 261, in fetch_command
>>>> commands = get_commands()
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/core/management/__init_
>>>> _.py", line 107, in get_commands
>>>> apps = settings.INSTALLED_APPS
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/conf/__init__.py",
>>>> line 54, in __getattr__
>>>> self._setup(name)
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/conf/__init__.py", line 49, in _setup
>>>> self._wrapped = Settings(settings_module)
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/conf/__init__.py", line 128, in __init__
>>>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/django/utils/importlib.py",
>>>> line 40, in import_module
>>>> __import__(name)
>>>>   File "/home/kpennell/mezz-site/settings.py", line 442, in 
>>>> set_dynamic_settings(globals())
>>>>   File "/home/kpennell/mezz-site/mezzenv/local/lib/
>>>> python2.7/site-packages/mezzanine/utils/conf.py",
>>>> line 184, in set_dynamic_settings
>>>> shortname = db["ENGINE"].split(".")[-1]
>>>> KeyError:

Re: [mezzanine-users] Fabric Settings Path, PROJECT_NAME trouble, Repository not found

[Kyle Pennell]

Good advice.  Thanks, Stephen.

Made the mistake of thinking I could just follow some tutorials and get 
something up working when I should have read more background info to start 
with.

On Thursday, April 10, 2014 4:31:26 PM UTC-5, Stephen McDonald wrote:
>
> I can't stress enough how different your experience would be if you took a 
> step back and read all the fabric documentation, then walked through 
> Mezzanine's fabfile step by step until you understand each of the steps it 
> takes to set up a server with your site deployed on it. 
>
> It's really just one big sequence of remote commands on your server - 
> install and configure all the things needed, then set up your project from 
> version control, and use it to run the site. Once you empower yourself by 
> understanding each of the steps it takes, you can *easily* debug these 
> problems on your own. 
>
> This approach requires the most effort from *you* up front, but will 
> ultimately be the most efficient in the long run. What you're doing now, 
> requires almost zero effort from you up front, calls on the effort of 
> *others*, and ultimately does you the greatest injustice in the long run, 
> by not learning how all these things actually work.
>
> Sorry if this advice is too blunt, but I think drip feeding you each step 
> is doing you a disservice.
>
>
> On Fri, Apr 11, 2014 at 7:09 AM, Kyle Pennell 
> > wrote:
>
>> You get this when you do so:
>>
>> [ahalearning.co] out: You must provide a DEST_DIR
>> [ahalearning.co] out: Usage: virtualenv [OPTIONS] DEST_DIR
>>
>>
>> Sorry for pestering you, Josh.  Perhaps someone else in this group has 
>> ideas so you don't have to keep trying.
>>
>> On Thursday, April 10, 2014 3:55:45 PM UTC-5, Josh Cartmell wrote:
>>
>>> As far as I know the project name can be arbitrary, it can also be left 
>>> blank and it will be inferred from the repo.  Maybe try leaving it blank
>>>
>>>
>>> On Thu, Apr 10, 2014 at 1:51 PM, Kyle Pennell  wrote:
>>>
>>>>  $ git clone g...@github.com:kpennell/mezz-digitalocean.git 
>>>>> /mezzanine_app/project ->
>>>>> [ahalearning.co] out: fatal: could not create leading directories of 
>>>>> '/mezzanine_app/project': Permission denied
>>>>> Fatal error: run() encountered an error (return code 128) while 
>>>>> executing 'git clone g...@github.com:kpennell/mezz-digitalocean.git 
>>>>> /mezzanine_app/project'
>>>>
>>>>
>>>> will have to dig into the permission error.
>>>>
>>>> On Thursday, April 10, 2014 3:29:18 PM UTC-5, Kyle Pennell wrote:
>>>>>
>>>>> I do get the space (I think). 
>>>>>
>>>>> It's trying to clone from one to another.
>>>>>
>>>>>>
>>>>>>>  -- 
>>>> 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-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Stephen McDonald
> http://jupo.org 
>

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

Re: [mezzanine-users] Fabric Settings Path, PROJECT_NAME trouble, Repository not found

[Kyle Pennell]

You get this when you do so:

[ahalearning.co] out: You must provide a DEST_DIR
[ahalearning.co] out: Usage: virtualenv [OPTIONS] DEST_DIR


Sorry for pestering you, Josh.  Perhaps someone else in this group has 
ideas so you don't have to keep trying.

On Thursday, April 10, 2014 3:55:45 PM UTC-5, Josh Cartmell wrote:
>
> As far as I know the project name can be arbitrary, it can also be left 
> blank and it will be inferred from the repo.  Maybe try leaving it blank
>
>
> On Thu, Apr 10, 2014 at 1:51 PM, Kyle Pennell 
> > wrote:
>
>> $ git clone g...@github.com:kpennell/mezz-digitalocean.git 
>>> /mezzanine_app/project ->
>>> [ahalearning.co] out: fatal: could not create leading directories of 
>>> '/mezzanine_app/project': Permission denied
>>> Fatal error: run() encountered an error (return code 128) while 
>>> executing 'git clone g...@github.com:kpennell/mezz-digitalocean.git 
>>> /mezzanine_app/project'
>>
>>
>> will have to dig into the permission error.
>>
>> On Thursday, April 10, 2014 3:29:18 PM UTC-5, Kyle Pennell wrote:
>>>
>>> I do get the space (I think). 
>>>
>>> It's trying to clone from one to another.
>>>
>>>>
>>>>>  -- 
>> 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] Fabric Settings Path, PROJECT_NAME trouble, Repository not found

[Kyle Pennell]

>
> $ git clone g...@github.com:kpennell/mezz-digitalocean.git 
> /mezzanine_app/project ->
> [ahalearning.co] out: fatal: could not create leading directories of 
> '/mezzanine_app/project': Permission denied
> Fatal error: run() encountered an error (return code 128) while executing 
> 'git clone g...@github.com:kpennell/mezz-digitalocean.git 
> /mezzanine_app/project'


will have to dig into the permission error.

On Thursday, April 10, 2014 3:29:18 PM UTC-5, Kyle Pennell wrote:
>
> I do get the space (I think). 
>
> It's trying to clone from one to another.
>
>>
>>>

-- 
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] Fabric Settings Path, PROJECT_NAME trouble, Repository not found

[Kyle Pennell]

I do get the space (I think). 

It's trying to clone from one to another.

>
>>

-- 
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] Fabric Settings Path, PROJECT_NAME trouble, Repository not found

[Kyle Pennell]

Ah, ok, thanks Josh.

In your example

the project name of "do_test" is located at 
https://joshcar...@bitbucket.org/joshcartme/vanilla_mezz?

https://joshcar...@bitbucket.org/joshcartme/vanilla_mezz/do_test  ?

how does that structure work?

I don't get it yet.  Getting a similar but different error now:

Fatal error: run() encountered an error (return code 255) while executing 
> 'hg clone https://github.com/kpennell/mezz-digitalocean 
> /mezzanine_app/project'


1. I don't understand why it adds "project"
2. Can see why there is a space.




On Thursday, April 10, 2014 1:27:22 PM UTC-5, Josh Cartmell wrote:
>
> I think you need to set the REPO_URL, otherwise it has no way to get the 
> project onto the remote server.
>
>
> On Thu, Apr 10, 2014 at 11:22 AM, Kyle Pennell 
> > wrote:
>
>> Getting closer with deploying by using Fabric.  I think my problem is the 
>> PROJECT_NAME.
>>
>> Getting this error after putting Fab All (other things seem to work now):
>>
>>
>> $ hg clone  /mezzanine_app/project ->
>>
>> [107.170.215.138] out: abort: repository /mezzanine_app/project not found!
>>
>> Fatal error: run() encountered an error (return code 255) while executing 
>>> 'hg clone  /mezzanine_app/project'
>>
>>
>> Repository not found...hm
>>
>> I guess I don't understand why it keeps tacking on my PROJECT_NAME + 
>> Project to the file path.
>>
>> Printing the working directory (where manage.py and local_settings are) 
>> gives me : /opt/mezzanine_env/mezzanine_app
>>
>> What should I be putting in PROJECT_NAME instead?  How can I let FABRIC 
>> find the repository?  Any clues where I might be going wrong?
>>
>>
>> My FABRIC Settings:
>>  
>>
>> *FABRIC = {*
>>
>> * "SSH_USER": "kpennell", # SSH username*
>>
>> * "SSH_PASS":  "pass", # SSH password (consider key-based auth$*
>>
>> * "SSH_KEY_PATH":  "/root/.ssh/id_rsa.pub", # Local path to SSH ke$*
>>
>> * "HOSTS": ["107.170.215.138"], # List of hosts to deploy to*
>>
>> * "VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs 
>>>  (I assumed I could leave this blank)*
>>
>> * "PROJECT_NAME": "mezzanine_app", # Unique identifier for project   
>>>   (this is the folder where my mezzanine stuff is)*
>>
>> * "REQUIREMENTS_PATH": "requirements.txt", # Path to pip requireme$*
>>
>> * "GUNICORN_PORT": 8000, # Port gunicorn will listen on*
>>
>> * "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"*
>>
>> * "LIVE_HOSTNAME": "www.ahalearning.co <http://www.ahalearning.co>", 
>>> # Host for public site.*
>>
>> * "REPO_URL": "", # Git or Mercurial remote repo URL for the proje$   
>>> Can this be blank?*
>>
>> * "DB_PASS": "pass", # Live database password*
>>
>> * "ADMIN_PASS": "pass", # Live admin user password*
>>
>> * }*
>>
>>
>>  -- 
>> 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.

[mezzanine-users] Fabric Settings Path, PROJECT_NAME trouble, Repository not found

[Kyle Pennell]

Getting closer with deploying by using Fabric.  I think my problem is the 
PROJECT_NAME.

Getting this error after putting Fab All (other things seem to work now):


$ hg clone  /mezzanine_app/project ->

[107.170.215.138] out: abort: repository /mezzanine_app/project not found!

Fatal error: run() encountered an error (return code 255) while executing 
> 'hg clone  /mezzanine_app/project'


Repository not found...hm

I guess I don't understand why it keeps tacking on my PROJECT_NAME + 
Project to the file path.

Printing the working directory (where manage.py and local_settings are) 
gives me : /opt/mezzanine_env/mezzanine_app

What should I be putting in PROJECT_NAME instead?  How can I let FABRIC 
find the repository?  Any clues where I might be going wrong?


My FABRIC Settings:
 

*FABRIC = {*

* "SSH_USER": "kpennell", # SSH username*

* "SSH_PASS":  "pass", # SSH password (consider key-based auth$*

* "SSH_KEY_PATH":  "/root/.ssh/id_rsa.pub", # Local path to SSH ke$*

* "HOSTS": ["107.170.215.138"], # List of hosts to deploy to*

* "VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs   
>(I assumed I could leave this blank)*

* "PROJECT_NAME": "mezzanine_app", # Unique identifier for project 
> (this is the folder where my mezzanine stuff is)*

* "REQUIREMENTS_PATH": "requirements.txt", # Path to pip requireme$*

* "GUNICORN_PORT": 8000, # Port gunicorn will listen on*

* "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"*

* "LIVE_HOSTNAME": "www.ahalearning.co", # Host for public site.*

* "REPO_URL": "", # Git or Mercurial remote repo URL for the proje$ 
>   Can this be blank?*

* "DB_PASS": "pass", # Live database password*

* "ADMIN_PASS": "pass", # Live admin user password*

* }*


-- 
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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

This thread is turning into a monster.  I'll start a new one for this 
specific FABRIC question if that's ok.

On Wednesday, April 9, 2014 7:45:26 PM UTC-5, Kyle Pennell wrote:
>
> Basically hitting this:
>
> out: abort: repository /opt/vanilla_mezz/project not found!
>
> Can't figure out why it can't find it.  Can't figure out the right path to 
> set in the PROJECT_NAME
>
> At least, that's what I think is throwing it off.
>
> On Wednesday, April 9, 2014 6:27:57 PM UTC-5, Kyle Pennell wrote:
>>
>> Sorry for being vague:
>>
>> Was thinking something like this:
>> ├── deploy
>> │   ├── crontab
>> │   ├── gunicorn.conf.py
>> │   ├── live_settings.py
>> │   ├── nginx.conf
>> │   └── supervisor.conf
>> ├── dev.db
>> ├── fabfile.py
>> ├── __init__.py
>> ├── __init__.pyc
>> ├── local_settings.py
>> ├── local_settings.pyc
>> ├── manage.py
>> ├── requirements.txt
>> ├── settings.py
>> ├── settings.pyc
>> ├── static
>> │   ├── admin
>> │   ├── css
>> │   ├── filebrowser
>> │   ├── fonts
>> │   ├── grappelli
>> │   ├── img
>> │   ├── js
>> │   ├── media
>> │   ├── mezzanine
>> │   ├── robots.txt
>> │   └── test
>> ├── urls.py
>> ├── urls.pyc
>> └── wsgi.py
>>
>>
>> Could make the fabric settings even easier.  Make sure I have the app in 
>> the right place.
>>
>> On Wednesday, April 9, 2014 6:21:56 PM UTC-5, Josh Cartmell wrote:
>>>
>>> I'm not sure I understand your question, this is the repo I deployed:
>>>
>>> https://bitbucket.org/joshcartme/vanilla_mezz/src/89e8ec26735fa6dade72af9a2cc936052d08fd3f?at=default
>>>
>>> Is that what you were looking for?
>>>
>>>
>>> On Wed, Apr 9, 2014 at 4:16 PM, Kyle Pennell  wrote:
>>>
>>>> Hey Josh,
>>>> Would it be possible for you to send me the Tree Document Structure 
>>>> where Vanilla_mezz is?  I could then double check I have things in the 
>>>> right place.
>>>>
>>>>
>>>> On Friday, April 4, 2014 2:18:42 PM UTC-6, Josh Cartmell wrote:
>>>>
>>>>> what if you run:
>>>>>
>>>>> sudo cat /etc/default/locale
>>>>>
>>>>> I'm at a bit of a loss, never seen that error before =/
>>>>>
>>>>>
>>>>> On Fri, Apr 4, 2014 at 11:41 AM, Kyle Pennell wrote:
>>>>>
>>>>>> fab settings seems to be right there as well:
>>>>>>>
>>>>>>>
>>>>>>>  "REQUIREMENTS_PATH": "requirements.txt", # Path to pip 
>>>>>>> requirements, relativ$
>>>>>>>  "GUNICORN_PORT": 8000, # Port gunicorn will listen on
>>>>>>>  "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
>>>>>>>  "LIVE_HOSTNAME": "www.ahalearning.co", # Host for public site.
>>>>>>
>>>>>>
>>>>>> On Friday, April 4, 2014 12:09:35 PM UTC-6, Kyle Pennell wrote:
>>>>>>>
>>>>>>> root@kpennell:/opt/myenv/mezzanine_app# fab all
>>>>>>> [107.170.215.138] Executing task 'all'
>>>>>>>
>>>>>>> ---
>>>>>>> all
>>>>>>> ---
>>>>>>>
>>>>>>>
>>>>>>> ---
>>>>>>> install
>>>>>>> ---
>>>>>>>
>>>>>>>
>>>>>>> $ cat /etc/default/locale ->
>>>>>>>
>>>>>>>
>>>>>>> Fatal error: sudo() encountered an error (return code 1) while 
>>>>>>> executing 'cat /etc/default/locale'
>>>>>>>
>>>>>>> Aborting.
>>>>>>> Disconnecting from 107.170.215.138... done.
>>>>>>> root@kpennell:/opt/myenv/mezzanine_app# nano /etc/default/locale
>>>>>>>
>>>>>>>   GNU nano 2.2.6File: /etc/default/locale   
>>>>>>> 
>>>>>>>
>>>>>>> LANG="en_US.UTF-8"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Here's what I'm seeing.  The file seems to exist.
>>>>>>>
>>>>>>> On Thursday, April 3, 2014 11:34:24 AM UTC-6, Matthew Summers wrote:
>>>>>>>>
>>>>>>>> Does that file exist? 
>>>>>>>>
>>>>>>>  -- 
>>>>>> 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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Basically hitting this:

out: abort: repository /opt/vanilla_mezz/project not found!

Can't figure out why it can't find it.  Can't figure out the right path to 
set in the PROJECT_NAME

At least, that's what I think is throwing it off.

On Wednesday, April 9, 2014 6:27:57 PM UTC-5, Kyle Pennell wrote:
>
> Sorry for being vague:
>
> Was thinking something like this:
> ├── deploy
> │   ├── crontab
> │   ├── gunicorn.conf.py
> │   ├── live_settings.py
> │   ├── nginx.conf
> │   └── supervisor.conf
> ├── dev.db
> ├── fabfile.py
> ├── __init__.py
> ├── __init__.pyc
> ├── local_settings.py
> ├── local_settings.pyc
> ├── manage.py
> ├── requirements.txt
> ├── settings.py
> ├── settings.pyc
> ├── static
> │   ├── admin
> │   ├── css
> │   ├── filebrowser
> │   ├── fonts
> │   ├── grappelli
> │   ├── img
> │   ├── js
> │   ├── media
> │   ├── mezzanine
> │   ├── robots.txt
> │   └── test
> ├── urls.py
> ├── urls.pyc
> └── wsgi.py
>
>
> Could make the fabric settings even easier.  Make sure I have the app in 
> the right place.
>
> On Wednesday, April 9, 2014 6:21:56 PM UTC-5, Josh Cartmell wrote:
>>
>> I'm not sure I understand your question, this is the repo I deployed:
>>
>> https://bitbucket.org/joshcartme/vanilla_mezz/src/89e8ec26735fa6dade72af9a2cc936052d08fd3f?at=default
>>
>> Is that what you were looking for?
>>
>>
>> On Wed, Apr 9, 2014 at 4:16 PM, Kyle Pennell  wrote:
>>
>>> Hey Josh,
>>> Would it be possible for you to send me the Tree Document Structure 
>>> where Vanilla_mezz is?  I could then double check I have things in the 
>>> right place.
>>>
>>>
>>> On Friday, April 4, 2014 2:18:42 PM UTC-6, Josh Cartmell wrote:
>>>
>>>> what if you run:
>>>>
>>>> sudo cat /etc/default/locale
>>>>
>>>> I'm at a bit of a loss, never seen that error before =/
>>>>
>>>>
>>>> On Fri, Apr 4, 2014 at 11:41 AM, Kyle Pennell wrote:
>>>>
>>>>> fab settings seems to be right there as well:
>>>>>>
>>>>>>
>>>>>>  "REQUIREMENTS_PATH": "requirements.txt", # Path to pip 
>>>>>> requirements, relativ$
>>>>>>  "GUNICORN_PORT": 8000, # Port gunicorn will listen on
>>>>>>  "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
>>>>>>  "LIVE_HOSTNAME": "www.ahalearning.co", # Host for public site.
>>>>>
>>>>>
>>>>> On Friday, April 4, 2014 12:09:35 PM UTC-6, Kyle Pennell wrote:
>>>>>>
>>>>>> root@kpennell:/opt/myenv/mezzanine_app# fab all
>>>>>> [107.170.215.138] Executing task 'all'
>>>>>>
>>>>>> ---
>>>>>> all
>>>>>> ---
>>>>>>
>>>>>>
>>>>>> ---
>>>>>> install
>>>>>> ---
>>>>>>
>>>>>>
>>>>>> $ cat /etc/default/locale ->
>>>>>>
>>>>>>
>>>>>> Fatal error: sudo() encountered an error (return code 1) while 
>>>>>> executing 'cat /etc/default/locale'
>>>>>>
>>>>>> Aborting.
>>>>>> Disconnecting from 107.170.215.138... done.
>>>>>> root@kpennell:/opt/myenv/mezzanine_app# nano /etc/default/locale
>>>>>>
>>>>>>   GNU nano 2.2.6File: /etc/default/locale 
>>>>>>   
>>>>>>
>>>>>> LANG="en_US.UTF-8"
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Here's what I'm seeing.  The file seems to exist.
>>>>>>
>>>>>> On Thursday, April 3, 2014 11:34:24 AM UTC-6, Matthew Summers wrote:
>>>>>>>
>>>>>>> Does that file exist? 
>>>>>>>
>>>>>>  -- 
>>>>> 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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Sorry for being vague:

Was thinking something like this:
├── deploy
│   ├── crontab
│   ├── gunicorn.conf.py
│   ├── live_settings.py
│   ├── nginx.conf
│   └── supervisor.conf
├── dev.db
├── fabfile.py
├── __init__.py
├── __init__.pyc
├── local_settings.py
├── local_settings.pyc
├── manage.py
├── requirements.txt
├── settings.py
├── settings.pyc
├── static
│   ├── admin
│   ├── css
│   ├── filebrowser
│   ├── fonts
│   ├── grappelli
│   ├── img
│   ├── js
│   ├── media
│   ├── mezzanine
│   ├── robots.txt
│   └── test
├── urls.py
├── urls.pyc
└── wsgi.py


Could make the fabric settings even easier.  Make sure I have the app in 
the right place.

On Wednesday, April 9, 2014 6:21:56 PM UTC-5, Josh Cartmell wrote:
>
> I'm not sure I understand your question, this is the repo I deployed:
>
> https://bitbucket.org/joshcartme/vanilla_mezz/src/89e8ec26735fa6dade72af9a2cc936052d08fd3f?at=default
>
> Is that what you were looking for?
>
>
> On Wed, Apr 9, 2014 at 4:16 PM, Kyle Pennell 
> > wrote:
>
>> Hey Josh,
>> Would it be possible for you to send me the Tree Document Structure where 
>> Vanilla_mezz is?  I could then double check I have things in the right 
>> place.
>>
>>
>> On Friday, April 4, 2014 2:18:42 PM UTC-6, Josh Cartmell wrote:
>>
>>> what if you run:
>>>
>>> sudo cat /etc/default/locale
>>>
>>> I'm at a bit of a loss, never seen that error before =/
>>>
>>>
>>> On Fri, Apr 4, 2014 at 11:41 AM, Kyle Pennell  wrote:
>>>
>>>> fab settings seems to be right there as well:
>>>>>
>>>>>
>>>>>  "REQUIREMENTS_PATH": "requirements.txt", # Path to pip 
>>>>> requirements, relativ$
>>>>>  "GUNICORN_PORT": 8000, # Port gunicorn will listen on
>>>>>  "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
>>>>>  "LIVE_HOSTNAME": "www.ahalearning.co", # Host for public site.
>>>>
>>>>
>>>> On Friday, April 4, 2014 12:09:35 PM UTC-6, Kyle Pennell wrote:
>>>>>
>>>>> root@kpennell:/opt/myenv/mezzanine_app# fab all
>>>>> [107.170.215.138] Executing task 'all'
>>>>>
>>>>> ---
>>>>> all
>>>>> ---
>>>>>
>>>>>
>>>>> ---
>>>>> install
>>>>> ---
>>>>>
>>>>>
>>>>> $ cat /etc/default/locale ->
>>>>>
>>>>>
>>>>> Fatal error: sudo() encountered an error (return code 1) while 
>>>>> executing 'cat /etc/default/locale'
>>>>>
>>>>> Aborting.
>>>>> Disconnecting from 107.170.215.138... done.
>>>>> root@kpennell:/opt/myenv/mezzanine_app# nano /etc/default/locale
>>>>>
>>>>>   GNU nano 2.2.6File: /etc/default/locale 
>>>>>   
>>>>>
>>>>> LANG="en_US.UTF-8"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Here's what I'm seeing.  The file seems to exist.
>>>>>
>>>>> On Thursday, April 3, 2014 11:34:24 AM UTC-6, Matthew Summers wrote:
>>>>>>
>>>>>> Does that file exist? 
>>>>>>
>>>>>  -- 
>>>> 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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Matthew*

On Wednesday, April 9, 2014 6:15:01 PM UTC-5, Kyle Pennell wrote:
>
> Mathew, thank you.  That was totally my bad.  Didn't follow the 
> instructions well enough that Josh laid out.  I needed to change root in 
> visudo to the user I created.
>
> On Saturday, April 5, 2014 8:54:35 AM UTC-6, Matthew Summers wrote:
>>
>> You might also check that the user you connect with via ssh is in the 
>> sudoers group and/or file. 
>>
>>
>> -- 
>> M. Summers 
>>
>> "...there are no rules here -- we're trying to accomplish something." 
>>   - Thomas A. Edison 
>>
>

-- 
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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Hey Josh,
Would it be possible for you to send me the Tree Document Structure where 
Vanilla_mezz is?  I could then double check I have things in the right 
place.

On Friday, April 4, 2014 2:18:42 PM UTC-6, Josh Cartmell wrote:
>
> what if you run:
>
> sudo cat /etc/default/locale
>
> I'm at a bit of a loss, never seen that error before =/
>
>
> On Fri, Apr 4, 2014 at 11:41 AM, Kyle Pennell 
> > wrote:
>
>> fab settings seems to be right there as well:
>>>
>>>
>>>  "REQUIREMENTS_PATH": "requirements.txt", # Path to pip 
>>> requirements, relativ$
>>>  "GUNICORN_PORT": 8000, # Port gunicorn will listen on
>>>  "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
>>>  "LIVE_HOSTNAME": "www.ahalearning.co", # Host for public site.
>>
>>
>> On Friday, April 4, 2014 12:09:35 PM UTC-6, Kyle Pennell wrote:
>>>
>>> root@kpennell:/opt/myenv/mezzanine_app# fab all
>>> [107.170.215.138] Executing task 'all'
>>>
>>> ---
>>> all
>>> ---
>>>
>>>
>>> ---
>>> install
>>> ---
>>>
>>>
>>> $ cat /etc/default/locale ->
>>>
>>>
>>> Fatal error: sudo() encountered an error (return code 1) while executing 
>>> 'cat /etc/default/locale'
>>>
>>> Aborting.
>>> Disconnecting from 107.170.215.138... done.
>>> root@kpennell:/opt/myenv/mezzanine_app# nano /etc/default/locale
>>>
>>>   GNU nano 2.2.6File: /etc/default/locale   
>>> 
>>>
>>> LANG="en_US.UTF-8"
>>>
>>>
>>>
>>>
>>>
>>> Here's what I'm seeing.  The file seems to exist.
>>>
>>> On Thursday, April 3, 2014 11:34:24 AM UTC-6, Matthew Summers wrote:
>>>>
>>>> Does that file exist? 
>>>>
>>>  -- 
>> 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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Mathew, thank you.  That was totally my bad.  Didn't follow the 
instructions well enough that Josh laid out.  I needed to change root in 
visudo to the user I created.

On Saturday, April 5, 2014 8:54:35 AM UTC-6, Matthew Summers wrote:
>
> You might also check that the user you connect with via ssh is in the 
> sudoers group and/or file. 
>
>
> -- 
> M. Summers 
>
> "...there are no rules here -- we're trying to accomplish something." 
>   - Thomas A. Edison 
>

-- 
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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

fab settings seems to be right there as well:
>
>
>  "REQUIREMENTS_PATH": "requirements.txt", # Path to pip requirements, 
> relativ$
>  "GUNICORN_PORT": 8000, # Port gunicorn will listen on
>  "LOCALE": "en_US.UTF-8", # Should end with ".UTF-8"
>  "LIVE_HOSTNAME": "www.ahalearning.co", # Host for public site.


On Friday, April 4, 2014 12:09:35 PM UTC-6, Kyle Pennell wrote:
>
> root@kpennell:/opt/myenv/mezzanine_app# fab all
> [107.170.215.138] Executing task 'all'
>
> ---
> all
> ---
>
>
> ---
> install
> ---
>
>
> $ cat /etc/default/locale ->
>
>
> Fatal error: sudo() encountered an error (return code 1) while executing 
> 'cat /etc/default/locale'
>
> Aborting.
> Disconnecting from 107.170.215.138... done.
> root@kpennell:/opt/myenv/mezzanine_app# nano /etc/default/locale
>
>   GNU nano 2.2.6File: /etc/default/locale 
>   
>
> LANG="en_US.UTF-8"
>
>
>
>
>
> Here's what I'm seeing.  The file seems to exist.
>
> On Thursday, April 3, 2014 11:34:24 AM UTC-6, Matthew Summers wrote:
>>
>> Does that file exist? 
>>
>

-- 
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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

root@kpennell:/opt/myenv/mezzanine_app# fab all
[107.170.215.138] Executing task 'all'

---
all
---


---
install
---


$ cat /etc/default/locale ->


Fatal error: sudo() encountered an error (return code 1) while executing 
'cat /etc/default/locale'

Aborting.
Disconnecting from 107.170.215.138... done.
root@kpennell:/opt/myenv/mezzanine_app# nano /etc/default/locale

  GNU nano 2.2.6File: /etc/default/locale   


LANG="en_US.UTF-8"





Here's what I'm seeing.  The file seems to exist.

On Thursday, April 3, 2014 11:34:24 AM UTC-6, Matthew Summers wrote:
>
> Does that file exist? 
>

-- 
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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Hey Josh,
The file is there and it seems to be right.

On Thursday, April 3, 2014 10:27:53 AM UTC-6, Josh Cartmell wrote:
>
> Hmm, I'm not sure about that one, what happens if you manually execute 
> that command on the server?
>
>
> On Thu, Apr 3, 2014 at 6:34 AM, Kyle Pennell 
> > wrote:
>
>> Thanks, Josh. That cleared that.  I'm surprised Googling didn't yield the 
>> same advice (pip install future).  Oh well.
>>
>> Last problem is this pesky:
>>
>> [107.170.215.138] Executing task 'all'
>>
>> ---
>>
>> all
>>
>> ---
>>
>> ---
>>
>> install
>>
>> ---
>>
>> $ cat /etc/default/locale ->
>>
>> Fatal error: sudo() encountered an error (return code 1) while executing 
>> 'cat /etc/default/locale'
>>
>>
>>
>> any ideas why it would have problems with locale?
>>
>> On Wednesday, April 2, 2014 3:44:27 PM UTC-6, Josh Cartmell wrote:
>>
>>> No worries, I would just try reinstalling it and also trying explicitly 
>>> installing future, so:
>>> pip install future
>>> pip install fabric
>>>
>>>
>>> On Wed, Apr 2, 2014 at 2:29 PM, Kyle Pennell  wrote:
>>>
>>>> Also checked outside of my virtualenv:
>>>>
>>>> root@kpennell:/opt/myenv/mezzanine_app# python
>>>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
>>>> [GCC 4.6.3] on linux2
>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>> >>> 
>>>>
>>>> 2.7.3
>>>>
>>>>
>>>> Sorry for the non-stop assault of questions, Josh.
>>>>
>>>> On Wednesday, April 2, 2014 3:18:58 PM UTC-6, Kyle Pennell wrote:
>>>>>
>>>>> Removed the discus comment so as to not make more work.
>>>>>
>>>>> On Wednesday, April 2, 2014 3:14:55 PM UTC-6, Kyle Pennell wrote:
>>>>>>
>>>>>> I'm using 2.7
>>>>>>>
>>>>>>>
>>>>>>> (myenv)root@kpennell:/opt/myenv# python
>>>>>>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
>>>>>>> [GCC 4.6.3] on linux2
>>>>>>> Type "help", "copyright", "credits" or "license" for more 
>>>>>>> information.
>>>>>>> >>> 
>>>>>>
>>>>>>
>>>>>> hmm..
>>>>>>
>>>>>>
>>>>>> On Wednesday, April 2, 2014 2:12:13 PM UTC-6, Josh Cartmell wrote:
>>>>>>>
>>>>>>> Are you using Python 3?  If so you can't use it with fabric and need 
>>>>>>> to use 2.  If you are using python 2 try reinstalling fabric, 
>>>>>>> deactivating 
>>>>>>> and reactivating your virtualenv.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 2, 2014 at 11:37 AM, Kyle Pennell wrote:
>>>>>>>
>>>>>>>> Hey Josh,
>>>>>>>> I just hit this after running that tutorial.  Any idea what I might 
>>>>>>>> need to change?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Friday, March 21, 2014 3:05:23 PM UTC-6, Josh Cartmell wrote:
>>>>>>>>
>>>>>>>>> Hey Ziwei, you are correct, fabric doesn't currently support 
>>>>>>>>> python 3.  Per http://docs.fabfile.org/en/1.8/ is works with 
>>>>>>>>> 2.5-2.7.
>>>>>>>>>  
>>>>>>>>>
>>>>>>>>> On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou wrote:
>>>>>>>>>
>>>>>>>>>>  Hi
>>>>>>>>>>
>>>>>>>>>> Is the current fabfile.py working in python 3 environment? I 
>>>>>>>>>> tried to run fab under python 2.7 and got the error about 
>>>>>>>>>>
>>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>>
>>>>>>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", 
>>>>>>>>>> line 632, in main
>>>>>>>>>

Re: [mezzanine-users] What should/would example Fab file settings look like?

[Kyle Pennell]

Thanks again, everyone.

On Wednesday, April 2, 2014 12:15:20 PM UTC-6, Josh Cartmell wrote:
>
> That we did Ken ;)
>
> Kyle, now that you bring it up, those two settings are actually 
> unnecessary and I should probably just remove them.
>
> Take a look at 
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L43
> .
>
> If they aren't present it sets them to sensible defaults (the user's home 
> directory and the name of the project from version control).
>
>
> On Wed, Apr 2, 2014 at 11:06 AM, Kyle Pennell 
> > wrote:
>
>> Kenneth,
>> In that example
>>
>> "VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs
>>
>> # "PROJECT_NAME": "", # Unique identifier for project
>>
>>
>> These are left blank.  Why?
>>
>>>
>>>  -- 
>> 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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Thanks, Josh. That cleared that.  I'm surprised Googling didn't yield the 
same advice (pip install future).  Oh well.

Last problem is this pesky:

[107.170.215.138] Executing task 'all'

---

all

---

---

install

---

$ cat /etc/default/locale ->

Fatal error: sudo() encountered an error (return code 1) while executing 
'cat /etc/default/locale'



any ideas why it would have problems with locale?

On Wednesday, April 2, 2014 3:44:27 PM UTC-6, Josh Cartmell wrote:
>
> No worries, I would just try reinstalling it and also trying explicitly 
> installing future, so:
> pip install future
> pip install fabric
>
>
> On Wed, Apr 2, 2014 at 2:29 PM, Kyle Pennell 
> > wrote:
>
>> Also checked outside of my virtualenv:
>>
>> root@kpennell:/opt/myenv/mezzanine_app# python
>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
>> [GCC 4.6.3] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> 
>>
>> 2.7.3
>>
>>
>> Sorry for the non-stop assault of questions, Josh.
>>
>> On Wednesday, April 2, 2014 3:18:58 PM UTC-6, Kyle Pennell wrote:
>>>
>>> Removed the discus comment so as to not make more work.
>>>
>>> On Wednesday, April 2, 2014 3:14:55 PM UTC-6, Kyle Pennell wrote:
>>>>
>>>> I'm using 2.7
>>>>>
>>>>>
>>>>> (myenv)root@kpennell:/opt/myenv# python
>>>>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
>>>>> [GCC 4.6.3] on linux2
>>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>>> >>> 
>>>>
>>>>
>>>> hmm..
>>>>
>>>>
>>>> On Wednesday, April 2, 2014 2:12:13 PM UTC-6, Josh Cartmell wrote:
>>>>>
>>>>> Are you using Python 3?  If so you can't use it with fabric and need 
>>>>> to use 2.  If you are using python 2 try reinstalling fabric, 
>>>>> deactivating 
>>>>> and reactivating your virtualenv.
>>>>>
>>>>>
>>>>> On Wed, Apr 2, 2014 at 11:37 AM, Kyle Pennell wrote:
>>>>>
>>>>>> Hey Josh,
>>>>>> I just hit this after running that tutorial.  Any idea what I might 
>>>>>> need to change?
>>>>>>
>>>>>>
>>>>>> On Friday, March 21, 2014 3:05:23 PM UTC-6, Josh Cartmell wrote:
>>>>>>
>>>>>>> Hey Ziwei, you are correct, fabric doesn't currently support python 
>>>>>>> 3.  Per http://docs.fabfile.org/en/1.8/ is works with 2.5-2.7.
>>>>>>>  
>>>>>>>
>>>>>>> On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou wrote:
>>>>>>>
>>>>>>>>  Hi
>>>>>>>>
>>>>>>>> Is the current fabfile.py working in python 3 environment? I tried 
>>>>>>>> to run fab under python 2.7 and got the error about 
>>>>>>>>
>>>>>>>> Traceback (most recent call last):
>>>>>>>>
>>>>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", 
>>>>>>>> line 632, in main
>>>>>>>>
>>>>>>>> docstring, callables, default = load_fabfile(fabfile)
>>>>>>>>
>>>>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", 
>>>>>>>> line 164, in load_fabfile
>>>>>>>>
>>>>>>>> imported = importer(os.path.splitext(fabfile)[0])
>>>>>>>>
>>>>>>>>   File "/sites/trip/code/tour/fabfile.py", line 3, in 
>>>>>>>>
>>>>>>>> from future.builtins import input, open
>>>>>>>>
>>>>>>>> *ImportError: No module named future.builtins*
>>>>>>>>
>>>>>>>> After I upgrade to python 3.3, fab through out the same error 
>>>>>>>> message.  It seems fabric is still not python 3.3 compatible. 
>>>>>>>>
>>>>>>>> Anyone has the same issue? 
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>>  -- 
>>>>>>>> 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-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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Also checked outside of my virtualenv:

root@kpennell:/opt/myenv/mezzanine_app# python
Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> 

2.7.3


Sorry for the non-stop assault of questions, Josh.

On Wednesday, April 2, 2014 3:18:58 PM UTC-6, Kyle Pennell wrote:
>
> Removed the discus comment so as to not make more work.
>
> On Wednesday, April 2, 2014 3:14:55 PM UTC-6, Kyle Pennell wrote:
>>
>> I'm using 2.7
>>>
>>>
>>> (myenv)root@kpennell:/opt/myenv# python
>>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
>>> [GCC 4.6.3] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> 
>>
>>
>> hmm..
>>
>>
>> On Wednesday, April 2, 2014 2:12:13 PM UTC-6, Josh Cartmell wrote:
>>>
>>> Are you using Python 3?  If so you can't use it with fabric and need to 
>>> use 2.  If you are using python 2 try reinstalling fabric, deactivating and 
>>> reactivating your virtualenv.
>>>
>>>
>>> On Wed, Apr 2, 2014 at 11:37 AM, Kyle Pennell  wrote:
>>>
>>>> Hey Josh,
>>>> I just hit this after running that tutorial.  Any idea what I might 
>>>> need to change?
>>>>
>>>>
>>>> On Friday, March 21, 2014 3:05:23 PM UTC-6, Josh Cartmell wrote:
>>>>
>>>>> Hey Ziwei, you are correct, fabric doesn't currently support python 
>>>>> 3.  Per http://docs.fabfile.org/en/1.8/ is works with 2.5-2.7.
>>>>>  
>>>>>
>>>>> On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou wrote:
>>>>>
>>>>>>  Hi
>>>>>>
>>>>>> Is the current fabfile.py working in python 3 environment? I tried to 
>>>>>> run fab under python 2.7 and got the error about 
>>>>>>
>>>>>> Traceback (most recent call last):
>>>>>>
>>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 
>>>>>> 632, in main
>>>>>>
>>>>>> docstring, callables, default = load_fabfile(fabfile)
>>>>>>
>>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 
>>>>>> 164, in load_fabfile
>>>>>>
>>>>>> imported = importer(os.path.splitext(fabfile)[0])
>>>>>>
>>>>>>   File "/sites/trip/code/tour/fabfile.py", line 3, in 
>>>>>>
>>>>>> from future.builtins import input, open
>>>>>>
>>>>>> *ImportError: No module named future.builtins*
>>>>>>
>>>>>> After I upgrade to python 3.3, fab through out the same error 
>>>>>> message.  It seems fabric is still not python 3.3 compatible. 
>>>>>>
>>>>>> Anyone has the same issue? 
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>  -- 
>>>>>> 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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Removed the discus comment so as to not make more work.

On Wednesday, April 2, 2014 3:14:55 PM UTC-6, Kyle Pennell wrote:
>
> I'm using 2.7
>>
>>
>> (myenv)root@kpennell:/opt/myenv# python
>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
>> [GCC 4.6.3] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> 
>
>
> hmm..
>
>
> On Wednesday, April 2, 2014 2:12:13 PM UTC-6, Josh Cartmell wrote:
>>
>> Are you using Python 3?  If so you can't use it with fabric and need to 
>> use 2.  If you are using python 2 try reinstalling fabric, deactivating and 
>> reactivating your virtualenv.
>>
>>
>> On Wed, Apr 2, 2014 at 11:37 AM, Kyle Pennell  wrote:
>>
>>> Hey Josh,
>>> I just hit this after running that tutorial.  Any idea what I might need 
>>> to change?
>>>
>>>
>>> On Friday, March 21, 2014 3:05:23 PM UTC-6, Josh Cartmell wrote:
>>>
>>>> Hey Ziwei, you are correct, fabric doesn't currently support python 3.  
>>>> Per http://docs.fabfile.org/en/1.8/ is works with 2.5-2.7.
>>>>  
>>>>
>>>> On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou  wrote:
>>>>
>>>>>  Hi
>>>>>
>>>>> Is the current fabfile.py working in python 3 environment? I tried to 
>>>>> run fab under python 2.7 and got the error about 
>>>>>
>>>>> Traceback (most recent call last):
>>>>>
>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 
>>>>> 632, in main
>>>>>
>>>>> docstring, callables, default = load_fabfile(fabfile)
>>>>>
>>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 
>>>>> 164, in load_fabfile
>>>>>
>>>>> imported = importer(os.path.splitext(fabfile)[0])
>>>>>
>>>>>   File "/sites/trip/code/tour/fabfile.py", line 3, in 
>>>>>
>>>>> from future.builtins import input, open
>>>>>
>>>>> *ImportError: No module named future.builtins*
>>>>>
>>>>> After I upgrade to python 3.3, fab through out the same error message. 
>>>>>  It seems fabric is still not python 3.3 compatible. 
>>>>>
>>>>> Anyone has the same issue? 
>>>>>
>>>>> Regards,
>>>>>
>>>>>  -- 
>>>>> 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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

I'm using 2.7
>
>
> (myenv)root@kpennell:/opt/myenv# python
> Python 2.7.3 (default, Feb 27 2014, 19:58:35) 
> [GCC 4.6.3] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> 


hmm..


On Wednesday, April 2, 2014 2:12:13 PM UTC-6, Josh Cartmell wrote:
>
> Are you using Python 3?  If so you can't use it with fabric and need to 
> use 2.  If you are using python 2 try reinstalling fabric, deactivating and 
> reactivating your virtualenv.
>
>
> On Wed, Apr 2, 2014 at 11:37 AM, Kyle Pennell 
> > wrote:
>
>> Hey Josh,
>> I just hit this after running that tutorial.  Any idea what I might need 
>> to change?
>>
>>
>> On Friday, March 21, 2014 3:05:23 PM UTC-6, Josh Cartmell wrote:
>>
>>> Hey Ziwei, you are correct, fabric doesn't currently support python 3.  
>>> Per http://docs.fabfile.org/en/1.8/ is works with 2.5-2.7.
>>>  
>>>
>>> On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou  wrote:
>>>
>>>>  Hi
>>>>
>>>> Is the current fabfile.py working in python 3 environment? I tried to 
>>>> run fab under python 2.7 and got the error about 
>>>>
>>>> Traceback (most recent call last):
>>>>
>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 
>>>> 632, in main
>>>>
>>>> docstring, callables, default = load_fabfile(fabfile)
>>>>
>>>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 
>>>> 164, in load_fabfile
>>>>
>>>> imported = importer(os.path.splitext(fabfile)[0])
>>>>
>>>>   File "/sites/trip/code/tour/fabfile.py", line 3, in 
>>>>
>>>> from future.builtins import input, open
>>>>
>>>> *ImportError: No module named future.builtins*
>>>>
>>>> After I upgrade to python 3.3, fab through out the same error message. 
>>>>  It seems fabric is still not python 3.3 compatible. 
>>>>
>>>> Anyone has the same issue? 
>>>>
>>>> Regards,
>>>>
>>>>  -- 
>>>> 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-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] Fab Script ImportError: No module named future.builtins

[Kyle Pennell]

Hey Josh,
I just hit this after running that tutorial.  Any idea what I might need to 
change?

On Friday, March 21, 2014 3:05:23 PM UTC-6, Josh Cartmell wrote:
>
> Hey Ziwei, you are correct, fabric doesn't currently support python 3.  
> Per http://docs.fabfile.org/en/1.8/ is works with 2.5-2.7.
>
>
> On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou 
> > wrote:
>
>> Hi
>>
>> Is the current fabfile.py working in python 3 environment? I tried to run 
>> fab under python 2.7 and got the error about 
>>
>> Traceback (most recent call last):
>>
>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 632, 
>> in main
>>
>> docstring, callables, default = load_fabfile(fabfile)
>>
>>   File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 164, 
>> in load_fabfile
>>
>> imported = importer(os.path.splitext(fabfile)[0])
>>
>>   File "/sites/trip/code/tour/fabfile.py", line 3, in 
>>
>> from future.builtins import input, open
>>
>> *ImportError: No module named future.builtins*
>>
>> After I upgrade to python 3.3, fab through out the same error message. 
>>  It seems fabric is still not python 3.3 compatible. 
>>
>> Anyone has the same issue? 
>>
>> Regards,
>>
>>  -- 
>> 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] What should/would example Fab file settings look like?

[Kyle Pennell]

Kenneth,
In that example

"VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs
# "PROJECT_NAME": "", # Unique identifier for project


These are left blank.  Why?

>
>

-- 
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: What should/would example Fab file settings look like?

[Kyle Pennell]

Wow, fast replies. Thanks.

Ok, so "VIRTUALENV_HOME" has nothing to do with "source bin/activate"?  

VIRTUALENV_HOME is where the project will live on the server's filesystem


Silly question, but how does one know where it will live?

On Wednesday, April 2, 2014 11:38:05 AM UTC-6, Kyle Pennell wrote:
>
> Asking a question for myself and hope it helps other beginners out there.
>
> I'm trying to deploy using Fab File and Josh's 
> Tutorial<http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/>
> .
>
> I was trying to fill in the Fabfile settings and simply don't understand 
> what most of them refer to.  I can't tell what goes where.  
>
> I didn't see Fabric in Stephen's example 
> project<https://github.com/stephenmcd/mezzanine.jupo.org>
> .
>
> Perhaps we could write an example that others could use?  Sort of plug and 
> play?  (If this already exists, you could point me there)
>
> Here's the settings:
>
> FABRIC = {
> "SSH_USER": "", # SSH username
> "SSH_PASS":  "", # SSH password (consider key-based authentication)
> "SSH_KEY_PATH":  "", # Local path to SSH key file, for key-based auth
> "HOSTS": [], # List of hosts to deploy to
> "VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs
> "PROJECT_NAME": "", # Unique identifier for project
> "REQUIREMENTS_PATH": "requirements/project.txt", # Path to pip 
> requirements, relative to project
> "GUNICORN_PORT": 8000, # Port gunicorn will listen on
> "LOCALE": "en_US.utf8", # Should end with ".utf8"
> "LIVE_HOSTNAME": "www.example.com", # Host for public site.
> "REPO_URL": "", # Git or Mercurial remote repo URL for the project
> "DB_PASS": "", # Live database password
> "ADMIN_PASS": "", # Live admin user password}
>
>
>
> Here's my project tree structure, verbatim from Digital Ocean's tutorials 
> on Mezzanine, Django, Nginx, and Gunicorn. Mezzanine_app is the mezzanine 
> app.
>
> ├── bin
> │   ├── activate
> │   ├── activate.csh
> │   ├── activate.fish
> │   ├── activate_this.py
> │   ├── django-admin.py
> │   ├── easy_install
> │   ├── easy_install-2.7
> │   ├── futurize
> │   ├── gunicorn
> │   ├── gunicorn_django
> │   ├── gunicorn_paster
> │   ├── mezzanine-project
> │   ├── pilconvert.py
> │   ├── pildriver.py
> │   ├── pilfile.py
> │   ├── pilfont.py
> │   ├── pilprint.py
> │   ├── pip
> │   ├── pip-2.7
> │   └── python
> ├── gunicorn_config.py
> ├── include
> │   └── python2.7 -> /usr/include/python2.7
> ├── lib
> │   └── python2.7
> │   ├── _abcoll.py -> /usr/lib/python2.7/_abcoll.py
> │   ├── _abcoll.pyc
> │   ├── abc.py -> /usr/lib/python2.7/abc.py
> │   ├── abc.pyc
> │   ├── codecs.py -> /usr/lib/python2.7/codecs.py
> │   ├── codecs.pyc
> │   ├── config -> /usr/lib/python2.7/config
> │   ├── copy_reg.py -> /usr/lib/python2.7/copy_reg.py
> │   ├── copy_reg.pyc
> │   ├── distutils
> │   ├── encodings -> /usr/lib/python2.7/encodings
> │   ├── fnmatch.py -> /usr/lib/python2.7/fnmatch.py
> │   ├── fnmatch.pyc
> │   ├── genericpath.py -> /usr/lib/python2.7/genericpath.py
> │   ├── genericpath.pyc
> │   ├── lib-dynload -> /usr/lib/python2.7/lib-dynload
> │   ├── linecache.py -> /usr/lib/python2.7/linecache.py
> │   ├── linecache.pyc
> │   ├── locale.py -> /usr/lib/python2.7/locale.py
> │   ├── locale.pyc
> │   ├── no-global-site-packages.txt
> │   ├── ntpath.py -> /usr/lib/python2.7/ntpath.py
> │   ├── orig-prefix.txt
> │   ├── os.py -> /usr/lib/python2.7/os.py
> │   ├── os.pyc
> │   ├── posixpath.py -> /usr/lib/python2.7/posixpath.py
> │   ├── posixpath.pyc
> │   ├── re.py -> /usr/lib/python2.7/re.py
> │   ├── re.pyc
> │   ├── site-packages
> │   ├── site.py
> │   ├── site.pyc
> │   ├── sre_compile.py -> /usr/lib/python2.7/sre_compile.py
> │   ├── sre_compile.pyc
> │   ├── sre_constants.py -> /usr/lib/python2.7/sre_constants.py
> │   ├── sre_constants.pyc
> │   ├── sre_parse.py -> /usr/lib/python2.7/sre_parse.py
> │   ├── sre_parse.pyc
> │   ├── sre.py -> /usr/lib/python2.7/sre.py
> │   ├── stat.py -> /usr/lib/python2.7/stat.py
> │   ├── stat.pyc
> │   ├── types.py ->

[mezzanine-users] What should/would example Fab file settings look like?

[Kyle Pennell]

Asking a question for myself and hope it helps other beginners out there.

I'm trying to deploy using Fab File and Josh's 
Tutorial
.

I was trying to fill in the Fabfile settings and simply don't understand 
what most of them refer to.  I can't tell what goes where.  

I didn't see Fabric in Stephen's example 
project
.

Perhaps we could write an example that others could use?  Sort of plug and 
play?  (If this already exists, you could point me there)

Here's the settings:

FABRIC = {
"SSH_USER": "", # SSH username
"SSH_PASS":  "", # SSH password (consider key-based authentication)
"SSH_KEY_PATH":  "", # Local path to SSH key file, for key-based auth
"HOSTS": [], # List of hosts to deploy to
"VIRTUALENV_HOME":  "", # Absolute remote path for virtualenvs
"PROJECT_NAME": "", # Unique identifier for project
"REQUIREMENTS_PATH": "requirements/project.txt", # Path to pip 
requirements, relative to project
"GUNICORN_PORT": 8000, # Port gunicorn will listen on
"LOCALE": "en_US.utf8", # Should end with ".utf8"
"LIVE_HOSTNAME": "www.example.com", # Host for public site.
"REPO_URL": "", # Git or Mercurial remote repo URL for the project
"DB_PASS": "", # Live database password
"ADMIN_PASS": "", # Live admin user password}



Here's my project tree structure, verbatim from Digital Ocean's tutorials 
on Mezzanine, Django, Nginx, and Gunicorn. Mezzanine_app is the mezzanine 
app.

├── bin
│   ├── activate
│   ├── activate.csh
│   ├── activate.fish
│   ├── activate_this.py
│   ├── django-admin.py
│   ├── easy_install
│   ├── easy_install-2.7
│   ├── futurize
│   ├── gunicorn
│   ├── gunicorn_django
│   ├── gunicorn_paster
│   ├── mezzanine-project
│   ├── pilconvert.py
│   ├── pildriver.py
│   ├── pilfile.py
│   ├── pilfont.py
│   ├── pilprint.py
│   ├── pip
│   ├── pip-2.7
│   └── python
├── gunicorn_config.py
├── include
│   └── python2.7 -> /usr/include/python2.7
├── lib
│   └── python2.7
│   ├── _abcoll.py -> /usr/lib/python2.7/_abcoll.py
│   ├── _abcoll.pyc
│   ├── abc.py -> /usr/lib/python2.7/abc.py
│   ├── abc.pyc
│   ├── codecs.py -> /usr/lib/python2.7/codecs.py
│   ├── codecs.pyc
│   ├── config -> /usr/lib/python2.7/config
│   ├── copy_reg.py -> /usr/lib/python2.7/copy_reg.py
│   ├── copy_reg.pyc
│   ├── distutils
│   ├── encodings -> /usr/lib/python2.7/encodings
│   ├── fnmatch.py -> /usr/lib/python2.7/fnmatch.py
│   ├── fnmatch.pyc
│   ├── genericpath.py -> /usr/lib/python2.7/genericpath.py
│   ├── genericpath.pyc
│   ├── lib-dynload -> /usr/lib/python2.7/lib-dynload
│   ├── linecache.py -> /usr/lib/python2.7/linecache.py
│   ├── linecache.pyc
│   ├── locale.py -> /usr/lib/python2.7/locale.py
│   ├── locale.pyc
│   ├── no-global-site-packages.txt
│   ├── ntpath.py -> /usr/lib/python2.7/ntpath.py
│   ├── orig-prefix.txt
│   ├── os.py -> /usr/lib/python2.7/os.py
│   ├── os.pyc
│   ├── posixpath.py -> /usr/lib/python2.7/posixpath.py
│   ├── posixpath.pyc
│   ├── re.py -> /usr/lib/python2.7/re.py
│   ├── re.pyc
│   ├── site-packages
│   ├── site.py
│   ├── site.pyc
│   ├── sre_compile.py -> /usr/lib/python2.7/sre_compile.py
│   ├── sre_compile.pyc
│   ├── sre_constants.py -> /usr/lib/python2.7/sre_constants.py
│   ├── sre_constants.pyc
│   ├── sre_parse.py -> /usr/lib/python2.7/sre_parse.py
│   ├── sre_parse.pyc
│   ├── sre.py -> /usr/lib/python2.7/sre.py
│   ├── stat.py -> /usr/lib/python2.7/stat.py
│   ├── stat.pyc
│   ├── types.py -> /usr/lib/python2.7/types.py
│   ├── types.pyc
│   ├── UserDict.py -> /usr/lib/python2.7/UserDict.py
│   ├── UserDict.pyc
│   ├── warnings.py -> /usr/lib/python2.7/warnings.py
│   ├── warnings.pyc
│   ├── _weakrefset.py -> /usr/lib/python2.7/_weakrefset.py
│   └── _weakrefset.pyc
├── local
│   ├── bin -> /opt/myenv/bin
│   ├── include -> /opt/myenv/include
│   └── lib -> /opt/myenv/lib
├── mezzanine_app
│   ├── deploy
│   │   ├── crontab
│   │   ├── gunicorn.conf.py
│   │   ├── live_settings.py
│   │   ├── nginx.conf
│   │   └── supervisor.conf
│   ├── dev.db
│   ├── fabfile.py
│   ├── __init__.py
│   ├── __init__.pyc
│   ├── local_settings.py
│   ├── local_settings.pyc
│   ├── manage.py
│   ├── requirements.txt
│   ├── settings.py
│   ├── settings.pyc
│   ├── static
│   │   └── media
│   ├── urls.py
│   ├── urls.pyc
│   └── wsgi.py
└── myproject
├── manage.py
└── myproject
├── __init__.py
├── __init__.pyc
├── settings.py
├── settings.pyc
├── urls.py
├── urls.pyc
├── wsgi.py
└── wsgi.pyc



-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group an

Re: [mezzanine-users] Can't figure out why my Static Files won't load

[Kyle Pennell]

Thanks, Jesse.  Much appreciated.


On Tue, Apr 1, 2014 at 1:55 PM, Jesse Carrigan
wrote:

> As a piece of encouragement, it took me about the same amount of time
> struggling with it to make it work, but after getting things set up
> correctly it's really easy to successfully deploy with Fabric. I'd
> recommend it; it's a much more repeatable process.
>
> --
> 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/CrUlR8jjUw0/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/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] Can't figure out why my Static Files won't load

[Kyle Pennell]

I'm going to try Fabric next. I was trying to the Digital Ocean Tuts to try
to get this but no dice.


On Tue, Apr 1, 2014 at 1:38 PM, Jesse Carrigan
wrote:

> Just out of curiosity, are you using fabric to deploy your site or are you
> editing the config by hand?
>
> Also, a couple of things I found helpful in trying to get the static files
> going:
>
> http://blog.doismellburning.co.uk/2012/06/25/django-and-static-files/
>
> https://docs.djangoproject.com/en/dev/howto/static-files/
>
> --
> 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/CrUlR8jjUw0/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/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] Can't figure out why my Static Files won't load

[Kyle Pennell]

Yes, no domain associated.  Was just hoping to work with the ip address.
Thanks for the response.  Any chance you have your working file on github?
 I've been stuck for 2 weeks now and would love to see it.


On Tue, Apr 1, 2014 at 11:43 AM, Jesse Carrigan
wrote:

> Correct, my DNS records on Digital Ocean are set up as follows (I'm faking
> some of the information here):
>
> example.com
> A record: @ 192.168.123.123
> NS: NS1.DIGITALOCEAN.COM
> NS: NS2.DIGITALOCEAN.COM
> NS: NS3.DIGITALOCEAN.COM
>
> example.com is in the ALLOWED_HOSTS list.
>
> It sounds like you may not have a domain associated with the droplet,
> though? Is that the case?
>
> --
> 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/CrUlR8jjUw0/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/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] Can't figure out why my Static Files won't load

[Kyle Pennell]

Hey Jesse,
Thanks for looking over this.

Ok, so you had to change it to an actual domain then?  Did you do the whole 
DNS redirect and everything to setup that domain with your digital ocean IP?

On Monday, March 31, 2014 11:58:43 PM UTC-6, Jesse Carrigan wrote:
>
> Rather than the IP address of the host, have you tried your live hostname 
> (e.g. "www.example.com" or "example.com")? My sites are hosted on Digital 
> Ocean and that's what needed to be in the ALLOWED_HOSTS list. Same for the 
> server_name in the ngnix configs.
>

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

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

[Kyle Pennell]

Nice of you to come post here, Ben. Thanks.

I've been trying with Digital Ocean now but am stuck in new and different 
interesting ways.

Never thought deploying Mezzanine would take me 25+ hours.  This is 
probably more my fault than the tutorials I've been using.  But wow.  Ouch.

On Sunday, March 30, 2014 1:32:30 PM UTC-6, Ben Havilland wrote:
>
> Hi all,
> I just joined the group.  Kyle, it appears you have moved on but if 
> anybody else is needs the current working Mezzanine/Heroku setup I've 
> updated my tutorial and it addresses/fixes KeyError: u'ENGINE' the error 
> you were getting.
>
> I just ran through it from scratch with the latest packages with success:
> http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/
>
> There was a problem in the settings.py with the placement of the local 
> settings and dynamic settings sections in the tutorial code.
>
> Ben
>
> On Tuesday, March 25, 2014 11:36:26 AM UTC-7, Kyle Pennell wrote:
>>
>> Hey all,
>> Would love to get some help here if you could.  Hit the wall on what I 
>> can do/try.
>>
>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
>> triedJosh's tutorial<https://gist.github.com/joshfinnie/4046138>, 
>> Ben's 
>> Tutorial<http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/>, 
>> searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
>> and interesting bugs on each one.
>>
>> So I'm trying Steven Elliot's tutorial<http://stevenelliottjr.github.io/>. 
>>  I reasoned that it was the newest (15 days ago) and might work better. 
>>  He's been extremely helpful on Twitter.
>>
>> Hit this roadblock here:
>>
>>
>>>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic 
>>>>
>>>>
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>>>>  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
>>>> 1.5 requires
>>>> . Will fall back to the domains configured as sites.
>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>>>>  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>>> Traceback (most recent call last):
>>>>   File "manage.py", line 29, in 
>>>> execute_from_command_line(sys.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 399, in execute_from_command_line
>>>> utility.execute()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 392, in execute
>>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 261, in fetch_command
>>>> commands = get_commands()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 107, in get_commands
>>>> apps = settings.INSTALLED_APPS
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 54, in __getattr__
>>>> self._setup(name)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 49, in _setup
>>>> self._wrapped = Settings(settings_module)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 128, in __init__
>>>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>>>
>>>>   File 
>>>> "/home/kpenne

Re: [mezzanine-users] Can't figure out why my Static Files won't load

[Kyle Pennell]

This is on Digital Ocean.  How would I check out firewall related issues?

On Saturday, March 29, 2014 2:00:08 AM UTC-6, Luc Milland wrote:
>
> could this be firewall related ? 
>
> Le vendredi 28 mars 2014 à 18:20 -0700, Kyle Pennell a écrit : 
> > First off, thanks so much for taking the time to respond to another 
> > beginner.  I'm on tutorial number 5 now of trying to figure this out. 
>  I'm 
> > amazed I haven't yet.  What a challenge. 
> > 
> > Changed that file: 
> > 
> > server { 
> > > server_name 107.170.215.138; 
> > > access_log off; 
> > > location /static/ { 
> > > alias /opt/myenv/mezzanine_app; 
> > > } 
> > > location / { 
> > > proxy_pass http://127.0.0.1:8001; 
> > > proxy_set_header X-Forwarded-Host $server_name; 
> > > proxy_set_header X-Real-IP $remote_addr; 
> > > add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL 
> UNI 
> > > COM NAV"'; 
> > > } 
> > > } 
> > > 
> > > 
> > My static ip was in the allowed hosts: 
> > 
> > ALLOWED_HOSTS = [ 
> > > '107.170.215.138', 
> > > '107.170.215.138.', 
> > > ] 
> > 
> > 
> > 
> > Error logs are the same. 
> > 
> > 
> > If you happen to have any random ideas, they'd be very much appreciated. 
> > 
> > Kyle 
> > 
> > On Friday, March 28, 2014 2:48:01 PM UTC-6, Matthew Summers wrote: 
> > > 
> > > On Fri, Mar 28, 2014 at 1:35 PM, Kyle Pennell 
> > > > 
>
> > > wrote: 
> > > > Thanks for responding. 
> > > > 
> > > > Double checking I understand: 
> > > > 
> > > >location /static/ { 
> > > > alias  /opt/myenv/mezzanine_app/static/; 
> > > > } 
> > > > 
> > > > Should be: 
> > > > 
> > > >location /static/ { 
> > > > alias  /opt/myenv/mezzanine_app/static; 
> > > > } 
> > > > 
> > > > Or? 
> > > > 
> > > >location /static/ { 
> > > > alias  /opt/myenv/mezzanine_app; 
> > > > } 
> > > > 
> > > > 
> > > 
> > > You'll want this one assuming the mezz project layout where your 
> > > static dir is directly under your messanine_app dir: 
> > > 
> > > location /static/ { 
> > >  alias  /opt/myenv/mezzanine_app; 
> > >  } 
> > > 
> > > 
> > > As far as your error log, it looks like you might need to add the 
> > > static ip of your server to ALLOWED_HOSTS in settings. Your app server 
> > > is refusing to respond to nginx. 
> > > 
> > > Cheers, 
> > > Matt 
> > > 
> > 
>
>
>

-- 
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] Can't figure out why my Static Files won't load

[Kyle Pennell]

First off, thanks so much for taking the time to respond to another 
beginner.  I'm on tutorial number 5 now of trying to figure this out.  I'm 
amazed I haven't yet.  What a challenge.

Changed that file:

server {
> server_name 107.170.215.138;
> access_log off;
> location /static/ {
> alias /opt/myenv/mezzanine_app;
> }
> location / {
> proxy_pass http://127.0.0.1:8001;
> proxy_set_header X-Forwarded-Host $server_name;
> proxy_set_header X-Real-IP $remote_addr;
> add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL UNI 
> COM NAV"';
> }
> }
>
>
My static ip was in the allowed hosts:

ALLOWED_HOSTS = [
> '107.170.215.138',
> '107.170.215.138.',
> ]



Error logs are the same.


If you happen to have any random ideas, they'd be very much appreciated.

Kyle

On Friday, March 28, 2014 2:48:01 PM UTC-6, Matthew Summers wrote:
>
> On Fri, Mar 28, 2014 at 1:35 PM, Kyle Pennell 
> > 
> wrote: 
> > Thanks for responding. 
> > 
> > Double checking I understand: 
> > 
> >location /static/ { 
> > alias  /opt/myenv/mezzanine_app/static/; 
> > } 
> > 
> > Should be: 
> > 
> >location /static/ { 
> > alias  /opt/myenv/mezzanine_app/static; 
> > } 
> > 
> > Or? 
> > 
> >location /static/ { 
> > alias  /opt/myenv/mezzanine_app; 
> > } 
> > 
> > 
>
> You'll want this one assuming the mezz project layout where your 
> static dir is directly under your messanine_app dir: 
>
> location /static/ { 
>  alias  /opt/myenv/mezzanine_app; 
>  } 
>
>
> As far as your error log, it looks like you might need to add the 
> static ip of your server to ALLOWED_HOSTS in settings. Your app server 
> is refusing to respond to nginx. 
>
> Cheers, 
> Matt 
>

-- 
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] Can't figure out why my Static Files won't load

[Kyle Pennell]

*Nginx Error Log:*

2014/03/28 12:16:12 [error] 13768#0: *27 connect() failed (111: Connection 
refused) while connecting to upstream, client: 61.135.190.70, server: 
107.170.215.138:8001, request: "GET

*Now to try to figure out what these are saying:*

2014/03/28 07:12:58 [error] 13768#0: *8 connect() failed (111: Connection 
refused) while connecting to upstream, client: 220.181.51.146, server: 
107.170.215.138:8001, request: "GET$

2014/03/28 07:28:45 [error] 13768#0: *10 connect() failed (111: Connection 
refused) while connecting to upstream, client: 220.181.51.147, server: 
107.170.215.138:8001, request: "GE$

2014/03/28 07:32:54 [error] 13768#0: *12 connect() failed (111: Connection 
refused) while connecting to upstream, client: 220.181.51.140, server: 
107.170.215.138:8001, request: "GE$

2014/03/28 07:45:33 [error] 13768#0: *14 connect() failed (111: Connection 
refused) while connecting to upstream, client: 220.181.51.147, server: 
107.170.215.138:8001, request: "GE$

2014/03/28 07:49:52 [error] 13768#0: *17 connect() failed (111: Connection 
refused) while connecting to upstream, client: 81.171.52.4, server: 
107.170.215.138:8001, request: "GET h$

2014/03/28 07:52:08 [error] 13768#0: *19 connect() failed (111: Connection 
refused) while connecting to upstream, client: 189.114.248.181, server: 
107.170.215.138:8001, request: "H$

2014/03/28 07:53:24 [error] 13768#0: *21 connect() failed (111: Connection 
refused) while connecting to upstream, client: 61.135.190.70, server: 
107.170.215.138:8001, request: "GET$

2014/03/28 08:11:36 [error] 13768#0: *23 connect() failed (111: Connection 
refused) while connecting to upstream, client: 61.135.190.198, server: 
107.170.215.138:8001, request: "GE$

2014/03/28 11:58:37 [error] 13768#0: *25 connect() failed (111: Connection 
refused) while connecting to upstream, client: 61.135.190.70, server: 
107.170.215.138:8001, request: "GET$

2014/03/28 12:16:12 [error] 13768#0: *27 connect() failed (111: Connection 
refused) while connecting to upstream, client: 61.135.190.70, server: 
107.170.215.138:8001, request: "GET$

$t: "GET / HTTP/1.0", upstream: "http://127.0.0.1:8001/";, host: 
"107.170.215.138", referrer: "http://www.baidu.com/s?wd=www";

2014/03/28 12:50:56 [error] 13768#0: *31 connect() failed (111: Connection 
refused) while connecting to upstream, client: 18.242.7.117, server: 
107.170.215.138:8001, request: "HEAD$

2014/03/28 14:06:02 [error] 13768#0: *33 connect() failed (111: Connection 
refused) while connecting to upstream, client: 202.53.8.82, server: 
107.170.215.138:8001, request: "GET 


$t: "GET / HTTP/1.0", upstream: "http://127.0.0.1:8001/";, host: 
"107.170.215.138", referrer: "http://www.baidu.com/s?wd=www";

On Friday, March 28, 2014 12:41:57 PM UTC-6, Kyle Pennell wrote:
>
> Tried each combo and none worked...hmmm...
>
> On Friday, March 28, 2014 12:35:39 PM UTC-6, Kyle Pennell wrote:
>>
>> Thanks for responding.
>>
>> Double checking I understand:
>>
>>location /static/ {
>> alias  /opt/myenv/mezzanine_app/static/;
>> }
>>
>> Should be:
>>
>>location /static/ {
>> alias  /opt/myenv/mezzanine_app/static;
>> }
>>
>> Or?
>>
>>location /static/ {
>> alias  /opt/myenv/mezzanine_app;
>> }
>>
>>
>> On Thursday, March 27, 2014 8:45:04 PM UTC-6, Matthew Summers wrote:
>>>
>>> Remove the trailing slash on your location alias directive. 
>>>
>>> On Thu, Mar 27, 2014 at 6:32 PM, Kyle Pennell  
>>> wrote: 
>>> > Ah!  Will try pulling that out.  Thanks for the help, Stephen. 
>>> > 
>>> > 
>>> > On Thu, Mar 27, 2014 at 5:28 PM, Stephen McDonald  
>>> wrote: 
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> On Fri, Mar 28, 2014 at 8:46 AM, Kyle Pennell  
>>> wrote: 
>>> >>> 
>>> >>> Triple checked my settings and can't find why my static files aren't 
>>> >>> loading. 
>>> >>> 
>>> >>> Nginx and Gunicorn are installed and working. 
>>> >>> Symbolic Link between sites-available and sites-enabled is made 
>>> >>> 
>>> >>> ── sites-available 
>>> >>> │   ├── mezzanine_app 
>>> >>> │   └── myproject 
>>> >>> ├── sites-enabled 
>>> >>> │   ├── ahalearning -> ../sites-available/ahalearning 
>>> >>> │   ├── mezzanine_app -> ../sites-available/mezzanine_app 

Re: [mezzanine-users] Can't figure out why my Static Files won't load

[Kyle Pennell]

Tried each combo and none worked...hmmm...

On Friday, March 28, 2014 12:35:39 PM UTC-6, Kyle Pennell wrote:
>
> Thanks for responding.
>
> Double checking I understand:
>
>location /static/ {
> alias  /opt/myenv/mezzanine_app/static/;
> }
>
> Should be:
>
>location /static/ {
> alias  /opt/myenv/mezzanine_app/static;
> }
>
> Or?
>
>location /static/ {
> alias  /opt/myenv/mezzanine_app;
> }
>
>
> On Thursday, March 27, 2014 8:45:04 PM UTC-6, Matthew Summers wrote:
>>
>> Remove the trailing slash on your location alias directive. 
>>
>> On Thu, Mar 27, 2014 at 6:32 PM, Kyle Pennell  wrote: 
>> > Ah!  Will try pulling that out.  Thanks for the help, Stephen. 
>> > 
>> > 
>> > On Thu, Mar 27, 2014 at 5:28 PM, Stephen McDonald  
>> wrote: 
>> >> 
>> >> 
>> >> 
>> >> 
>> >> On Fri, Mar 28, 2014 at 8:46 AM, Kyle Pennell  
>> wrote: 
>> >>> 
>> >>> Triple checked my settings and can't find why my static files aren't 
>> >>> loading. 
>> >>> 
>> >>> Nginx and Gunicorn are installed and working. 
>> >>> Symbolic Link between sites-available and sites-enabled is made 
>> >>> 
>> >>> ── sites-available 
>> >>> │   ├── mezzanine_app 
>> >>> │   └── myproject 
>> >>> ├── sites-enabled 
>> >>> │   ├── ahalearning -> ../sites-available/ahalearning 
>> >>> │   ├── mezzanine_app -> ../sites-available/mezzanine_app 
>> >>> │   └── myproject -> ../sites-available/myproject 
>> >>> 
>> >>> 
>> >>> Collectstatic has been run and static files are in place: 
>> >>> 
>> >>> ├── deploy 
>> >>> │   ├── crontab 
>> >>> │   ├── gunicorn.conf.py 
>> >>> │   ├── live_settings.py 
>> >>> │   ├── nginx.conf 
>> >>> │   └── supervisor.conf 
>> >>> ├── dev.db 
>> >>> ├── fabfile.py 
>> >>> ├── __init__.py 
>> >>> ├── __init__.pyc 
>> >>> ├── local_settings.py 
>> >>> ├── local_settings.pyc 
>> >>> ├── manage.py 
>> >>> ├── requirements.txt 
>> >>> ├── settings.py 
>> >>> ├── settings.pyc 
>> >>> ├── static 
>> >>> │   ├── admin 
>> >>> │   ├── css 
>> >>> │   ├── filebrowser 
>> >>> │   ├── fonts 
>> >>> │   ├── grappelli 
>> >>> │   ├── img 
>> >>> │   ├── js 
>> >>> │   ├── media 
>> >>> │   ├── mezzanine 
>> >>> │   ├── robots.txt 
>> >>> │   └── test 
>> >>> ├── urls.py 
>> >>> ├── urls.pyc 
>> >>> └── wsgi.py 
>> >>> 
>> >>> 
>> >>> STATIC_ROOT in settings.py points to the right folder 
>> >>> (opt/myenv/mezzanine_app/static/) 
>> >>> 
>> >>> 
>> >>> My nginx server settings point to the right files: 
>> >>> /etc/nginx/sites-available 
>> >>> 
>> >>> 
>> >>>  server { 
>> >>> server_name 107.170.215.138; 
>> >>> 
>> >>> access_log off; 
>> >>> 
>> >>> location /static/ { 
>> >>> alias  /opt/myenv/mezzanine_app/static/; 
>> >>> } 
>> >> 
>> >> 
>> >> I think this will look for the directory 
>> >> "/opt/myenv/mezzanine_app/static/static/" 
>> >> 
>> >> 
>> >>> 
>> >>> 
>> >>> location / { 
>> >>> proxy_pass http://127.0.0.1:8001; 
>> >>> proxy_set_header X-Forwarded-Host $server_name; 
>> >>> proxy_set_header X-Real-IP $remote_addr; 
>> >>> add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL 
>> UNI 
>> >>> COM NAV"'; 
>> >>> } 
>> >>> } 
>> >>> 
>> >>> Nginx and Gunicorn fire up without problems. 
>> >>> 
>> >>> 
>> >>> 
>> >>> Any idea what I might be missing? 
>> >>> 
>>

Re: [mezzanine-users] Can't figure out why my Static Files won't load

[Kyle Pennell]

Thanks for responding.

Double checking I understand:

   location /static/ {
alias  /opt/myenv/mezzanine_app/static/;
}

Should be:

   location /static/ {
alias  /opt/myenv/mezzanine_app/static;
}

Or?

   location /static/ {
alias  /opt/myenv/mezzanine_app;
}


On Thursday, March 27, 2014 8:45:04 PM UTC-6, Matthew Summers wrote:
>
> Remove the trailing slash on your location alias directive. 
>
> On Thu, Mar 27, 2014 at 6:32 PM, Kyle Pennell 
> > 
> wrote: 
> > Ah!  Will try pulling that out.  Thanks for the help, Stephen. 
> > 
> > 
> > On Thu, Mar 27, 2014 at 5:28 PM, Stephen McDonald 
> > > 
> wrote: 
> >> 
> >> 
> >> 
> >> 
> >> On Fri, Mar 28, 2014 at 8:46 AM, Kyle Pennell 
> >> > 
> wrote: 
> >>> 
> >>> Triple checked my settings and can't find why my static files aren't 
> >>> loading. 
> >>> 
> >>> Nginx and Gunicorn are installed and working. 
> >>> Symbolic Link between sites-available and sites-enabled is made 
> >>> 
> >>> ── sites-available 
> >>> │   ├── mezzanine_app 
> >>> │   └── myproject 
> >>> ├── sites-enabled 
> >>> │   ├── ahalearning -> ../sites-available/ahalearning 
> >>> │   ├── mezzanine_app -> ../sites-available/mezzanine_app 
> >>> │   └── myproject -> ../sites-available/myproject 
> >>> 
> >>> 
> >>> Collectstatic has been run and static files are in place: 
> >>> 
> >>> ├── deploy 
> >>> │   ├── crontab 
> >>> │   ├── gunicorn.conf.py 
> >>> │   ├── live_settings.py 
> >>> │   ├── nginx.conf 
> >>> │   └── supervisor.conf 
> >>> ├── dev.db 
> >>> ├── fabfile.py 
> >>> ├── __init__.py 
> >>> ├── __init__.pyc 
> >>> ├── local_settings.py 
> >>> ├── local_settings.pyc 
> >>> ├── manage.py 
> >>> ├── requirements.txt 
> >>> ├── settings.py 
> >>> ├── settings.pyc 
> >>> ├── static 
> >>> │   ├── admin 
> >>> │   ├── css 
> >>> │   ├── filebrowser 
> >>> │   ├── fonts 
> >>> │   ├── grappelli 
> >>> │   ├── img 
> >>> │   ├── js 
> >>> │   ├── media 
> >>> │   ├── mezzanine 
> >>> │   ├── robots.txt 
> >>> │   └── test 
> >>> ├── urls.py 
> >>> ├── urls.pyc 
> >>> └── wsgi.py 
> >>> 
> >>> 
> >>> STATIC_ROOT in settings.py points to the right folder 
> >>> (opt/myenv/mezzanine_app/static/) 
> >>> 
> >>> 
> >>> My nginx server settings point to the right files: 
> >>> /etc/nginx/sites-available 
> >>> 
> >>> 
> >>>  server { 
> >>> server_name 107.170.215.138; 
> >>> 
> >>> access_log off; 
> >>> 
> >>> location /static/ { 
> >>> alias  /opt/myenv/mezzanine_app/static/; 
> >>> } 
> >> 
> >> 
> >> I think this will look for the directory 
> >> "/opt/myenv/mezzanine_app/static/static/" 
> >> 
> >> 
> >>> 
> >>> 
> >>> location / { 
> >>> proxy_pass http://127.0.0.1:8001; 
> >>> proxy_set_header X-Forwarded-Host $server_name; 
> >>> proxy_set_header X-Real-IP $remote_addr; 
> >>> add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL 
> UNI 
> >>> COM NAV"'; 
> >>> } 
> >>> } 
> >>> 
> >>> Nginx and Gunicorn fire up without problems. 
> >>> 
> >>> 
> >>> 
> >>> Any idea what I might be missing? 
> >>> 
> >>> Why are my static files 404'ing? 
> >>> 
> >>> 
> >>> -- 
> >>> 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. 
> >> 
> >> 
> >> 
> >> 
> >> -- 
> >> Stephen McDonald 
> >> http://jupo.org 
> >> 
> >> -- 
> >> 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/CrUlR8jjUw0/unsubscribe. 
>
> >> To unsubscribe from this group and all its topics, 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-use...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> M. Summers 
>
> "...there are no rules here -- we're trying to accomplish something." 
>   - Thomas A. Edison 
>

-- 
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] Can't figure out why my Static Files won't load

[Kyle Pennell]

Ah!  Will try pulling that out.  Thanks for the help, Stephen.


On Thu, Mar 27, 2014 at 5:28 PM, Stephen McDonald  wrote:

>
>
>
> On Fri, Mar 28, 2014 at 8:46 AM, Kyle Pennell  wrote:
>
>> Triple checked my settings and can't find why my static files aren't
>> loading.
>>
>> Nginx and Gunicorn are installed and working.
>> Symbolic Link between sites-available and sites-enabled is made
>>
>> ── sites-available
>> │   ├── mezzanine_app
>> │   └── myproject
>> ├── sites-enabled
>> │   ├── ahalearning -> ../sites-available/ahalearning
>> │   ├── mezzanine_app -> ../sites-available/mezzanine_app
>> │   └── myproject -> ../sites-available/myproject
>>
>>
>> Collectstatic has been run and static files are in place:
>>
>> ├── deploy
>> │   ├── crontab
>> │   ├── gunicorn.conf.py
>> │   ├── live_settings.py
>> │   ├── nginx.conf
>> │   └── supervisor.conf
>> ├── dev.db
>> ├── fabfile.py
>> ├── __init__.py
>> ├── __init__.pyc
>> ├── local_settings.py
>> ├── local_settings.pyc
>> ├── manage.py
>> ├── requirements.txt
>> ├── settings.py
>> ├── settings.pyc
>> ├── static
>> │   ├── admin
>> │   ├── css
>> │   ├── filebrowser
>> │   ├── fonts
>> │   ├── grappelli
>> │   ├── img
>> │   ├── js
>> │   ├── media
>> │   ├── mezzanine
>> │   ├── robots.txt
>> │   └── test
>> ├── urls.py
>> ├── urls.pyc
>> └── wsgi.py
>>
>>
>> STATIC_ROOT in settings.py points to the right folder
>> (opt/myenv/mezzanine_app/static/)
>>
>>
>> My nginx server settings point to the right files:
>> /etc/nginx/sites-available
>>
>>  server {
>> server_name 107.170.215.138;
>>
>> access_log off;
>>
>> location /static/ {
>> alias  /opt/myenv/mezzanine_app/static/;
>> }
>>
>>
> I think this will look for the directory
> "/opt/myenv/mezzanine_app/static/static/"
>
>
>
>>
>>
>> location / {
>> proxy_pass http://127.0.0.1:8001;
>> proxy_set_header X-Forwarded-Host $server_name;
>> proxy_set_header X-Real-IP $remote_addr;
>> add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL UNI 
>> COM NAV"';
>> }
>> }
>>
>> Nginx and Gunicorn fire up without problems.
>>
>>
>>
>> Any idea what I might be missing?
>>
>> Why are my static files 404'ing?
>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to mezzanine-users+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Stephen McDonald
> http://jupo.org
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/CrUlR8jjUw0/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/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] Can't figure out why my Static Files won't load

[Kyle Pennell]

Triple checked my settings and can't find why my static files aren't 
loading.

Nginx and Gunicorn are installed and working.
Symbolic Link between sites-available and sites-enabled is made

── sites-available
│   ├── mezzanine_app
│   └── myproject
├── sites-enabled
│   ├── ahalearning -> ../sites-available/ahalearning
│   ├── mezzanine_app -> ../sites-available/mezzanine_app
│   └── myproject -> ../sites-available/myproject


Collectstatic has been run and static files are in place:

├── deploy
│   ├── crontab
│   ├── gunicorn.conf.py
│   ├── live_settings.py
│   ├── nginx.conf
│   └── supervisor.conf
├── dev.db
├── fabfile.py
├── __init__.py
├── __init__.pyc
├── local_settings.py
├── local_settings.pyc
├── manage.py
├── requirements.txt
├── settings.py
├── settings.pyc
├── static
│   ├── admin
│   ├── css
│   ├── filebrowser
│   ├── fonts
│   ├── grappelli
│   ├── img
│   ├── js
│   ├── media
│   ├── mezzanine
│   ├── robots.txt
│   └── test
├── urls.py
├── urls.pyc
└── wsgi.py


STATIC_ROOT in settings.py points to the right folder 
(opt/myenv/mezzanine_app/static/)


My nginx server settings point to the right files: 
/etc/nginx/sites-available

 server {
server_name 107.170.215.138;

access_log off;

location /static/ {
alias  /opt/myenv/mezzanine_app/static/;
}

location / {
proxy_pass http://127.0.0.1:8001;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Real-IP $remote_addr;
add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL UNI COM 
NAV"';
}
}

Nginx and Gunicorn fire up without problems.



Any idea what I might be missing?

Why are my static files 404'ing?


-- 
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] Is this what Mezzanine looks like with no static files?

[Kyle Pennell]

Aha, thanks.

python manage.py runserver 0.0.0.0:8000 (Static files load fine)

gunicorn_django --workers=3 --user=nobody --bind 107.170.215.138:8001  (No 
Static Files)


Hmm.will dig...

Thanks for the quick response.

I'm also writing this to hopefully help some other searching newbie like me.

keywords: nginx, gunicorn, static files, don't load,

On Thursday, March 27, 2014 1:52:21 PM UTC-6, Stephen McDonald wrote:
>
> Yes that's how it'd look.
>
> Make sure you've correctly configured nginx, and run Django's 
> collectstatic commend - you'll need to do the latter each time you deploy.
>
> Note that this is all handled for you automatically from setup to ongoing 
> deploys if you use the bundled fabric script.
>
> http://mezzanine.jupo.org/docs/deployment.html 
>
>
> On Fri, Mar 28, 2014 at 6:48 AM, Kyle Pennell 
> > wrote:
>
>> I'm trying to work out the Gunicorn and Mezzanine tutorials at Digital 
>> Ocean.
>>
>> I'm getting further and further.  I'm guessing my problem now is that my 
>> static files aren't loading.  Is the image below indeed what it looks like 
>> when you have something awry with Nginx and Gunicorn?
>>
>> Not trying to ask stupid questions...just checking that this in indeed 
>> some Nginx issue.
>>
>>
>> <https://lh5.googleusercontent.com/-d9NeGh49QzQ/UzSAZAaoE2I/GmA/PFUTdnC0BY4/s1600/mezz+no+static.png>
>>
>>  -- 
>> 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.
>>
>
>
>
> -- 
> 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] Is this what Mezzanine looks like with no static files?

[Kyle Pennell]

I'm trying to work out the Gunicorn and Mezzanine tutorials at Digital 
Ocean.

I'm getting further and further.  I'm guessing my problem now is that my 
static files aren't loading.  Is the image below indeed what it looks like 
when you have something awry with Nginx and Gunicorn?

Not trying to ask stupid questions...just checking that this in indeed some 
Nginx issue.



-- 
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] Tried 3-4 heroku deployment tutorials but stuck on each one.

[Kyle Pennell]

Decided to just go Digital Ocean.  It was an absolute waste of time trying 
to get Heroku to work.

On Tuesday, March 25, 2014 6:28:21 PM UTC-6, Kyle Pennell wrote:
>
> Pardon...any other good free options?
>
> On Tuesday, March 25, 2014 4:35:56 PM UTC-6, Josh Cartmell wrote:
>>
>> Hey Kyle, I've never used Heroku, are you set on using it?
>>
>> The fabfile that comes bundled with Mezzanine will deploy to a vanilla 
>> ubuntu VPS and is basically completely automated.
>>
>> I also have had good success hosting Mezzanine on Webfaction and can 
>> deploy there fairly easily.
>>
>>
>> On Tue, Mar 25, 2014 at 11:36 AM, Kyle Pennell  wrote:
>>
>>> Hey all,
>>> Would love to get some help here if you could.  Hit the wall on what I 
>>> can do/try.
>>>
>>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
>>> triedJosh's tutorial<https://gist.github.com/joshfinnie/4046138>, 
>>> Ben's 
>>> Tutorial<http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/>, 
>>> searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
>>> and interesting bugs on each one.
>>>
>>> So I'm trying Steven Elliot's tutorial<http://stevenelliottjr.github.io/>. 
>>>  I reasoned that it was the newest (15 days ago) and might work better. 
>>>  He's been extremely helpful on Twitter.
>>>
>>> Hit this roadblock here:
>>>
>>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic  
>>> 
>>>  
>>>>>
>>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>>>>>  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which 
>>>>> Django 1.5 requires
>>>>> . Will fall back to the domains configured as sites.
>>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>>>
>>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>>>>>  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
>>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>>>> Traceback (most recent call last):
>>>>>   File "manage.py", line 29, in 
>>>>> execute_from_command_line(sys.argv)
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>>  line 399, in execute_from_command_line
>>>>> utility.execute()
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>>  line 392, in execute
>>>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>>  line 261, in fetch_command
>>>>> commands = get_commands()
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>>  line 107, in get_commands
>>>>> apps = settings.INSTALLED_APPS
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>>  line 54, in __getattr__
>>>>> self._setup(name)
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>>  line 49, in _setup
>>>>> self._wrapped = Settings(settings_module)
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>>  line 128, in __init__
>>>>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>>>>
>>>>>   File 
>>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/djan

Re: [mezzanine-users] Re: Video of quickly deploying Mezzanine to Google App Engine with django-deployer

[Kyle Pennell]

Ok, yes.  True on the time costs.  I'm a new developer (3-4 months) and I 
swear (sometimes) I spend 55% deploying and 45% developing.

On Tuesday, March 25, 2014 6:49:11 PM UTC-6, Kenneth Bolton wrote:
>
> I run Mezzanine on variously sized EC2 instances as well as on a 
> RackSpace, nee Slicehost, VPS. A EC2 micro instance is free for the first 
> year, but generally costs less than $10 per month. Digital Ocean, at $5 per 
> month, also worked well for me the very first time. I have used the 
> included Fabric script to build and deploy to the aforementioned with no 
> modification.
>
> The real cost is not the monthly hosting cost, but the development, 
> deployment, and maintenance costs. If you have spent more than an hour 
> working on your deployment, you have cost yourself several months of 
> hosting expenses.
>
> ken
>
>
> On Tue, Mar 25, 2014 at 8:27 PM, Kyle Pennell 
> > wrote:
>
>> How much harder is it to use Heroku vs. GAE?
>>
>>
>> On Wednesday, April 10, 2013 4:05:07 PM UTC-5, Nate Aune wrote:
>>>
>>> I wanted to let folks on this list know about a new deployment tool that 
>>> I've been working on called django-deployer. 
>>> http://natea.github.io/django-deployer
>>>
>>> Here is a short 5 minute video showing how to deploy Mezzanine to Google 
>>> App Engine, with instructions on how to set up your Mezzanine-based project 
>>> on App Engine and Cloud SQL.
>>> http://appsembler.com/blog/deploy-django-apps-to-google-
>>> app-engine-with-django-deployer-in-5-minutes/
>>>
>>> django-deployer is essentially a fabric script that automates the 
>>> creation of all the configuration files necessary to deploy your Django app 
>>> to any of the PaaS providers. Currently there is support for Dotcloud, 
>>> Stackato and Google App Engine, but there are plans to add support for 
>>> Heroku, OpenShift and Gondor as well. 
>>>
>>> When you run the script, django-deployer asks you a series of questions 
>>> about your project and writes the answers out to a deploy.yml file. The 
>>> hope is that in the future, you could stick a deploy.yml file in your 
>>> Github repo, and any of the PaaS providers could consume this yaml file and 
>>> translate it into their specific way of deploying your app. Until then, 
>>> django-deployer is the babelfish that does that translation for you. :)
>>>
>>> While the script works mostly as advertised, it's very much still an 
>>> alpha quality piece of software, and I consider it a work-in-progress. If 
>>> you want to try it out, I'd love to get feedback on how it can be improved.
>>>
>>> Nate
>>>
>>>  -- 
>> 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] Tried 3-4 heroku deployment tutorials but stuck on each one.

[Kyle Pennell]

Pardon...any other good free options?

On Tuesday, March 25, 2014 4:35:56 PM UTC-6, Josh Cartmell wrote:
>
> Hey Kyle, I've never used Heroku, are you set on using it?
>
> The fabfile that comes bundled with Mezzanine will deploy to a vanilla 
> ubuntu VPS and is basically completely automated.
>
> I also have had good success hosting Mezzanine on Webfaction and can 
> deploy there fairly easily.
>
>
> On Tue, Mar 25, 2014 at 11:36 AM, Kyle Pennell 
> > wrote:
>
>> Hey all,
>> Would love to get some help here if you could.  Hit the wall on what I 
>> can do/try.
>>
>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
>> triedJosh's tutorial<https://gist.github.com/joshfinnie/4046138>, 
>> Ben's 
>> Tutorial<http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/>, 
>> searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
>> and interesting bugs on each one.
>>
>> So I'm trying Steven Elliot's tutorial<http://stevenelliottjr.github.io/>. 
>>  I reasoned that it was the newest (15 days ago) and might work better. 
>>  He's been extremely helpful on Twitter.
>>
>> Hit this roadblock here:
>>
>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic   
>>  
>>
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>>>>  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
>>>> 1.5 requires
>>>> . Will fall back to the domains configured as sites.
>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>>>>  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>>> Traceback (most recent call last):
>>>>   File "manage.py", line 29, in 
>>>> execute_from_command_line(sys.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 399, in execute_from_command_line
>>>> utility.execute()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 392, in execute
>>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 261, in fetch_command
>>>> commands = get_commands()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 107, in get_commands
>>>> apps = settings.INSTALLED_APPS
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 54, in __getattr__
>>>> self._setup(name)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 49, in _setup
>>>> self._wrapped = Settings(settings_module)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 128, in __init__
>>>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/utils/importlib.py",
>>>>  line 40, in import_module
>>>> __import__(name)
>>>>   File "/home/kpennell/mezz-site/settings.py", line 442, in 
>>>> set_dynamic_settings(globals())
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py",
>>>>  line 184, in set_dynamic_settings
>>>> shortname = db["ENGINE"].split(".")[-1]
>>>> KeyError: u'ENGINE'
>>>>
>>>
>> So something with collect static doesn't work.  Something to do with 
>> set_dynamic_settings.  I copied his tut verbatim and cloned the project he 
>> gave me and both hit the snag there.
>>
>> I can post the code here if you want but thought pushing to github would 
>> be easier:
>>
>> https://github.com/kpennell/mezz-try
>>
>>
>>
>> Any ideas?
>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mezzanine-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.

[mezzanine-users] Re: Video of quickly deploying Mezzanine to Google App Engine with django-deployer

[Kyle Pennell]

How much harder is it to use Heroku vs. GAE?

On Wednesday, April 10, 2013 4:05:07 PM UTC-5, Nate Aune wrote:
>
> I wanted to let folks on this list know about a new deployment tool that 
> I've been working on called django-deployer. 
> http://natea.github.io/django-deployer
>
> Here is a short 5 minute video showing how to deploy Mezzanine to Google 
> App Engine, with instructions on how to set up your Mezzanine-based project 
> on App Engine and Cloud SQL.
>
> http://appsembler.com/blog/deploy-django-apps-to-google-app-engine-with-django-deployer-in-5-minutes/
>
> django-deployer is essentially a fabric script that automates the creation 
> of all the configuration files necessary to deploy your Django app to any 
> of the PaaS providers. Currently there is support for Dotcloud, Stackato 
> and Google App Engine, but there are plans to add support for Heroku, 
> OpenShift and Gondor as well. 
>
> When you run the script, django-deployer asks you a series of questions 
> about your project and writes the answers out to a deploy.yml file. The 
> hope is that in the future, you could stick a deploy.yml file in your 
> Github repo, and any of the PaaS providers could consume this yaml file and 
> translate it into their specific way of deploying your app. Until then, 
> django-deployer is the babelfish that does that translation for you. :)
>
> While the script works mostly as advertised, it's very much still an alpha 
> quality piece of software, and I consider it a work-in-progress. If you 
> want to try it out, I'd love to get feedback on how it can be improved.
>
> Nate
>
>

-- 
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] Tried 3-4 heroku deployment tutorials but stuck on each one.

[Kyle Pennell]

What else do you recommend?

On Tuesday, March 25, 2014 4:35:56 PM UTC-6, Josh Cartmell wrote:
>
> Hey Kyle, I've never used Heroku, are you set on using it?
>
> The fabfile that comes bundled with Mezzanine will deploy to a vanilla 
> ubuntu VPS and is basically completely automated.
>
> I also have had good success hosting Mezzanine on Webfaction and can 
> deploy there fairly easily.
>
>
> On Tue, Mar 25, 2014 at 11:36 AM, Kyle Pennell 
> > wrote:
>
>> Hey all,
>> Would love to get some help here if you could.  Hit the wall on what I 
>> can do/try.
>>
>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
>> triedJosh's tutorial<https://gist.github.com/joshfinnie/4046138>, 
>> Ben's 
>> Tutorial<http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/>, 
>> searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
>> and interesting bugs on each one.
>>
>> So I'm trying Steven Elliot's tutorial<http://stevenelliottjr.github.io/>. 
>>  I reasoned that it was the newest (15 days ago) and might work better. 
>>  He's been extremely helpful on Twitter.
>>
>> Hit this roadblock here:
>>
>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic   
>>  
>>
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>>>>  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
>>>> 1.5 requires
>>>> . Will fall back to the domains configured as sites.
>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>>>>  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>>> Traceback (most recent call last):
>>>>   File "manage.py", line 29, in 
>>>> execute_from_command_line(sys.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 399, in execute_from_command_line
>>>> utility.execute()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 392, in execute
>>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 261, in fetch_command
>>>> commands = get_commands()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 107, in get_commands
>>>> apps = settings.INSTALLED_APPS
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 54, in __getattr__
>>>> self._setup(name)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 49, in _setup
>>>> self._wrapped = Settings(settings_module)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 128, in __init__
>>>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/utils/importlib.py",
>>>>  line 40, in import_module
>>>> __import__(name)
>>>>   File "/home/kpennell/mezz-site/settings.py", line 442, in 
>>>> set_dynamic_settings(globals())
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py",
>>>>  line 184, in set_dynamic_settings
>>>> shortname = db["ENGINE"].split(".")[-1]
>>>> KeyError: u'ENGINE'
>>>>
>>>
>> So something with collect static doesn't work.  Something to do with 
>> set_dynamic_settings.  I copied his tut verbatim and cloned the project he 
>> gave me and both hit the snag there.
>>
>> I can post the code here if you want but thought pushing to github would 
>> be easier:
>>
>> https://github.com/kpennell/mezz-try
>>
>>
>>
>> Any ideas?
>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mezzanine-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] Tried 3-4 heroku deployment tutorials but stuck on each one.

[Kyle Pennell]

Is Google App Engine the better solution?

On Tuesday, March 25, 2014 5:10:07 PM UTC-6, Danny S wrote:
>
> Biggest problem I had with Heroku is that it doesn't have any 
> permanent storage - each time you redeploy, you're creating your 
> project/app/static from scratch. It doesn't work so well with 
> Mezzanine's ability to upload media files. There is a way of hooking 
> things in with Amazon S3 but I never managed to get it to work with 
> any Django project, so I ended up giving up on Heroku. 
>
> (Also the, SSL add-on pack is quite expensive!) 
>
> On 26 March 2014 09:34, Kyle Pennell > 
> wrote: 
> > Hey Josh, 
> > Was hoping to stick to Heroku because it's free and I didn't want to 
> scatter 
> > my apps around too much.  But I'm open to other ideas. 
> > 
> > 
> > On Tuesday, March 25, 2014 4:35:56 PM UTC-6, Josh Cartmell wrote: 
> >> 
> >> Hey Kyle, I've never used Heroku, are you set on using it? 
> >> 
> >> The fabfile that comes bundled with Mezzanine will deploy to a vanilla 
> >> ubuntu VPS and is basically completely automated. 
> >> 
> >> I also have had good success hosting Mezzanine on Webfaction and can 
> >> deploy there fairly easily. 
> >> 
> >> 
> >> On Tue, Mar 25, 2014 at 11:36 AM, Kyle Pennell  
> wrote: 
> >>> 
> >>> Hey all, 
> >>> Would love to get some help here if you could.  Hit the wall on what I 
> >>> can do/try. 
> >>> 
> >>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
> tried 
> >>> Josh's tutorial, Ben's Tutorial, searched Stackoverflow, here, etc. 
>  Going 
> >>> on 10 hours trying.  Hit unique and interesting bugs on each one. 
> >>> 
> >>> So I'm trying Steven Elliot's tutorial.  I reasoned that it was the 
> >>> newest (15 days ago) and might work better.  He's been extremely 
> helpful on 
> >>> Twitter. 
> >>> 
> >>> Hit this roadblock here: 
> >>> 
> >>>>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic 
> >>>>> 
> >>>>> 
> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>  
>
> >>>>> UserWarning: You haven't defined the ALLOWED_HOSTS settings, which 
> Django 
> >>>>> 1.5 requires 
> >>>>> . Will fall back to the domains configured as sites. 
> >>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which " 
> >>>>> 
> >>>>> 
> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>  
>
> >>>>> UserWarning: TIME_ZONE setting is not set, using closest match: 
> Etc/UTC 
> >>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz) 
> >>>>> Traceback (most recent call last): 
> >>>>>   File "manage.py", line 29, in  
> >>>>> execute_from_command_line(sys.argv) 
> >>>>>   File 
> >>>>> 
> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>  
>
> >>>>> line 399, in execute_from_command_line 
> >>>>> utility.execute() 
> >>>>>   File 
> >>>>> 
> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>  
>
> >>>>> line 392, in execute 
> >>>>> self.fetch_command(subcommand).run_from_argv(self.argv) 
> >>>>>   File 
> >>>>> 
> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>  
>
> >>>>> line 261, in fetch_command 
> >>>>> commands = get_commands() 
> >>>>>   File 
> >>>>> 
> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>  
>
> >>>>> line 107, in get_commands 
> >>>>> apps = settings.INSTALLED_APPS 
> >>>>>   File 
> >>>>> 
> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>  
>
> >>>>> line 54, in __getattr__ 
> >>>>> self._setup(na

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

[Kyle Pennell]

Hey Josh,
Was hoping to stick to Heroku because it's free and I didn't want to 
scatter my apps around too much.  But I'm open to other ideas.

On Tuesday, March 25, 2014 4:35:56 PM UTC-6, Josh Cartmell wrote:
>
> Hey Kyle, I've never used Heroku, are you set on using it?
>
> The fabfile that comes bundled with Mezzanine will deploy to a vanilla 
> ubuntu VPS and is basically completely automated.
>
> I also have had good success hosting Mezzanine on Webfaction and can 
> deploy there fairly easily.
>
>
> On Tue, Mar 25, 2014 at 11:36 AM, Kyle Pennell 
> > wrote:
>
>> Hey all,
>> Would love to get some help here if you could.  Hit the wall on what I 
>> can do/try.
>>
>> I'm just trying to deploy a basic mezzanine setup on Heroku.  I've 
>> triedJosh's tutorial<https://gist.github.com/joshfinnie/4046138>, 
>> Ben's 
>> Tutorial<http://www.benhavilland.com/blog/deploying-mezzanine-on-heroku/>, 
>> searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
>> and interesting bugs on each one.
>>
>> So I'm trying Steven Elliot's tutorial<http://stevenelliottjr.github.io/>. 
>>  I reasoned that it was the newest (15 days ago) and might work better. 
>>  He's been extremely helpful on Twitter.
>>
>> Hit this roadblock here:
>>
>> (mezzenv)kpennell@vm-0:~/mezz-site$ python manage.py collectstatic   
>>  
>>
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>>>>  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
>>>> 1.5 requires
>>>> . Will fall back to the domains configured as sites.
>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>>
>>>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>>>>  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
>>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>>> Traceback (most recent call last):
>>>>   File "manage.py", line 29, in 
>>>> execute_from_command_line(sys.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 399, in execute_from_command_line
>>>> utility.execute()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 392, in execute
>>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 261, in fetch_command
>>>> commands = get_commands()
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>  line 107, in get_commands
>>>> apps = settings.INSTALLED_APPS
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 54, in __getattr__
>>>> self._setup(name)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 49, in _setup
>>>> self._wrapped = Settings(settings_module)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>>>  line 128, in __init__
>>>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/utils/importlib.py",
>>>>  line 40, in import_module
>>>> __import__(name)
>>>>   File "/home/kpennell/mezz-site/settings.py", line 442, in 
>>>> set_dynamic_settings(globals())
>>>>
>>>>   File 
>>>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/me

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

[Kyle Pennell]

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

I'm just trying to deploy a basic mezzanine setup on Heroku.  I've triedJosh's 
tutorial, 
Ben's 
Tutorial, 
searched Stackoverflow, here, etc.  Going on 10 hours trying.  Hit unique 
and interesting bugs on each one.

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

Hit this roadblock here:

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

 
>>
>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51:
>>  UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 
>> 1.5 requires
>> . Will fall back to the domains configured as sites.
>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>
>> /home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:59:
>>  UserWarning: TIME_ZONE setting is not set, using closest match: Etc/UTC
>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>> Traceback (most recent call last):
>>   File "manage.py", line 29, in 
>> execute_from_command_line(sys.argv)
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>  line 399, in execute_from_command_line
>> utility.execute()
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>  line 392, in execute
>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>  line 261, in fetch_command
>> commands = get_commands()
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>  line 107, in get_commands
>> apps = settings.INSTALLED_APPS
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>  line 54, in __getattr__
>> self._setup(name)
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>  line 49, in _setup
>> self._wrapped = Settings(settings_module)
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/conf/__init__.py",
>>  line 128, in __init__
>> mod = importlib.import_module(self.SETTINGS_MODULE)
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/django/utils/importlib.py",
>>  line 40, in import_module
>> __import__(name)
>>   File "/home/kpennell/mezz-site/settings.py", line 442, in 
>> set_dynamic_settings(globals())
>>
>>   File 
>> "/home/kpennell/mezz-site/mezzenv/local/lib/python2.7/site-packages/mezzanine/utils/conf.py",
>>  line 184, in set_dynamic_settings
>> shortname = db["ENGINE"].split(".")[-1]
>> KeyError: u'ENGINE'
>>
>
So something with collect static doesn't work.  Something to do with 
set_dynamic_settings.  I copied his tut verbatim and cloned the project he 
gave me and both hit the snag there.

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

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



Any ideas?


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

Re: [mezzanine-users] What is needed to deploy a Mezzanine project to Heroku?

[Kyle Pennell]

Also getting that Internal Server error each time.  I tried Josh's tut and Ben 
Havlliand's
 
and no luck.

H...

Will try to be more specific but am so confused as to where I'm going wrong 
exactly.

On Friday, September 27, 2013 1:30:32 PM UTC-5, Josh Finnie wrote:
>
> Hey Juan,
>
> I am also on this email list too if you have any questions. I haven't 
> installed Mezzanine on Heroku since I wrote that, and I would even do 
> somethings differently now. But still, it should get you started.
>
> Cheers,
>
> josh
>
>
> Josh Finnie
> --
> mobile: (860) 716-5996
> home: (202) 657-5346
>
>
> On Thu, Sep 26, 2013 at 2:28 PM, Josh Cartmell 
> 
> > wrote:
>
>> Hey Juan, I'm the person that told you to come here, so I'm glad you did!
>>
>> I would definitely look at the tutorial that Ken mentioned.
>>
>> Besides that I looked at the error messages you posted again and it does 
>> say what the problem is:
>>
>> Downloading/unpacking bonjour-py==0.3 (from -r requirements.txt (line 9))
>>  Could not find any downloads that satisfy the requirement 
>> bonjour-py==0.3 (from -r requirements.txt (line 9))
>>No distributions at all found for bonjour-py==0.3 (from -r 
>> requirements.txt (line 9))
>>Storing complete log in /app/.pip/pip.log
>>
>> That error isn't related to Mezzanine because Mezzanine doesn't use 
>> bonjour-py, but it's telling you that bonjour-py 0.3 is not available for 
>> installation using pip (I tried and no version is available) so when it 
>> tries to install it it fails.  I'm not sure how/if you can manually install 
>> packages on Heroku, but that's probably what you need to do.
>>
>> It might be best to initially try to install vanilla Mezzanine to Heroku 
>> using the tutorial Ken posted and then build up your additional 
>> requirements from there.
>>
>>
>> On Thu, Sep 26, 2013 at 10:02 AM, Ken Bolton 
>> > wrote:
>>
>>> Hi Juan,
>>>
>>> Take a look at Josh Finnie's tutorial on the matter at 
>>> https://gist.github.com/joshfinnie/4046138.
>>>
>>> hth, and let us know how things work out.
>>>
>>> ken
>>>
>>>
>>> On Thu, Sep 26, 2013 at 12:54 PM, Juan Gallardo 
>>> 
>>> > wrote:
>>>
 My background is Rails. New to python so can use a little help here 
 deploying a mezzanine project to Heroku. 


 After I downloaded the default project I just wanted to deploy it to 
 heroku to begin the blog that I want to launch. Before deploying I knew 
 there would have to be some files necessary for Heroku. I looked up the 
 Getting 
 Started with Python on 
 Herokudocumentation
  but was stuck at the Profile. I did not see one in my project 
 so I created a new one and added what was in the tutorial which was 

 web: gunicorn hello:app

 and yeah obviously I was copypasting but what does that above even mean? 
 Well I posted to Stackoverflow and no one seems to know but they told me 
 to come here. 
  
 The link to my question on stackoverflow with the error logs is 
 http://stackoverflow.com/questions/18998618/django-mezzanine-cms-project-not-deploying-to-heroku





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

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

-- 
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] Mezzanine on Heroku

[Kyle Pennell]

Hey Stephen,
Did you since delete that repo?

On Friday, July 20, 2012 7:18:21 AM UTC-5, Stephen McDonald wrote:
>
> As discussed on IRC, here are the bits I used to get Mezzanine and 
> Cartridge up on Heroku (http://mezzanine.herokuapp.com) back in March 
> this year. My repo has a directory called "mezzroku" which is the project 
> itself.
>
> Procfile:
>
> web: python mezzroku/manage.py createdb --noinput; python 
> mezzroku/manage.py migrate; python mezzroku/manage.py run_gunicorn -b 
> "0.0.0.0:$PORT" -w 3
>
> requirements.txt:
>
> Cartridge==0.4.9
> Django==1.3.1
> distribute==0.6.19
> psycopg2==2.4.4
> wsgiref==0.1.2
> gunicorn==0.13.4
> South==0.7.3
> django-storages==1.1.4
> boto==2.2.2
>
>
> On Fri, Jul 20, 2012 at 4:52 AM, knite >wrote:
>
>> I recently deployed a Mezzanine project to Heroku. The process differs a 
>> bit from standard Django, and took some tinkering, so I thought I would 
>> document the necessary changes here.
>>
>> All of these changes stem from the fact that a typical Django project has 
>> a myproj/myproj/ folder structure (manage.py at the top level, the rest in 
>> the sub-folder), whereas Mezzanine eliminates the myproj/ sub-directory.
>>
>> 1) In settings.py, replace
>>
>> ROOT_URLCONF = "%s.urls" % PROJECT_DIRNAME
>>
>> with
>>
>> ROOT_URLCONF = "urls"
>>
>> (I found no instances of ROOT_URLCONF in Mezzanine's codebase, so I 
>> believe this change will not break anything.)
>>
>> 2) Create wsgi.py at the top level of your project. This file is created 
>> when using django-admin.py to start a project, but not when using 
>> mezzanine-project. The default contents should be tweaked slightly if you 
>> do not use the DJANGO_SETTINGS_MODULE environment variable:
>>
>> import os
>>
>> os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings")
>>
>> from django.core.wsgi import get_wsgi_application
>>  application = get_wsgi_application()
>>
>> 3) Modify the Procfile example given in Heroku's docs (
>> https://devcenter.heroku.com/articles/django):
>>
>> web: gunicorn wsgi -b 0.0.0.0:$PORT
>>
>> (Note: for production, gevent should be used. I haven't gotten there yet, 
>> but it should be as simple as appending '-w  -k gevent'.)
>>
>> You'll also need to serve your static files.There are a few ways to do 
>> this, the main choice being whether to wrap your web worker with a call to 
>> collectstatic, or use Amazon S3.
>>
>> ...and that's where I'm stuck! After the above, I get the following error 
>> when I deploy:
>>
>> 2012-07-19T18:41:39+00:00 app[web.1]: 2012-07-19 20:41:39 [5] [ERROR] 
>> Error handling request
>> 2012-07-19T18:41:39+00:00 app[web.1]: Traceback (most recent call last):
>> 2012-07-19T18:41:39+00:00 app[web.1]:   File 
>> "/app/.heroku/venv/lib/python2.7/site-packages/django/core/handlers/wsgi.py",
>>  
>> line 219, in __call__
>> 2012-07-19T18:41:39+00:00 app[web.1]:   File 
>> "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/workers/sync.py", 
>> line 99, in handle_request
>> 2012-07-19T18:41:39+00:00 app[web.1]: respiter = self.wsgi(environ, 
>> resp.start_response)
>> 2012-07-19T18:41:39+00:00 app[web.1]: self.load_middleware()
>> 2012-07-19T18:41:39+00:00 app[web.1]:   File 
>> "/app/.heroku/venv/lib/python2.7/site-packages/django/core/handlers/base.py",
>>  
>> line 47, in load_middleware
>> 2012-07-19T18:41:39+00:00 app[web.1]: raise 
>> exceptions.ImproperlyConfigured('Error importing middleware %s: "%s"' % 
>> (mw_module, e))
>> 2012-07-19T18:41:39+00:00 app[web.1]: ImproperlyConfigured: Error 
>> importing middleware mezzanine.core.middleware: "cannot import name utils"
>>
>> Does anyone know what might be happening in mezzanine.core.middleware? It 
>> doesn't directly import a module named utils, but does have:
>>
>> from django.utils.cache import get_max_age
>> from mezzanine.utils.cache import (cache_key_prefix, nevercache_token,
>>cache_get, cache_set, cache_installed)
>> from mezzanine.utils.device import templates_for_device
>> from mezzanine.utils.sites import templates_for_host
>>
>> --Aris
>>
>
>
>
> -- 
> 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.