Re: [mezzanine-users] Subclassing SiteRelated
I thought so, Thanks Josh! On Wednesday, April 9, 2014 8:45:25 PM UTC-7, Josh Cartmell wrote: Yes, Mezzanine's multi tenancy features rely on the fields/managers added by SiteRelated ;) On Wed, Apr 9, 2014 at 12:23 PM, Matt Mansour slackb...@gmail.comjavascript: wrote: Howdy all - With a quick glance at the core I think I know the answer but thought I'd post the question as well. Would the best way to integrate an external django app - one that does not subclass Displayable - into Mezzanine's multi-tenancy functionality be to change the models of the app to subclass SiteRelated ? Best, 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Fab Script ImportError: No module named future.builtins
No worries, and that sounds good On Wed, Apr 9, 2014 at 5:59 PM, Kyle Pennell kpenn...@gmail.com wrote: 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 kpen...@gmail.com 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 kpen...@gmail.comwrote: 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. -- 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
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] Fabric Settings Path, PROJECT_NAME trouble, Repository not found
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 kpenn...@gmail.com 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-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] Fabric Settings Path, PROJECT_NAME trouble, Repository not found
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 kpen...@gmail.comjavascript:
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 javascript:.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Fabric Settings Path, PROJECT_NAME trouble, Repository not found
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
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 kpenn...@gmail.com 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 kpen...@gmail.com 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. -- 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.
