Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

novice question #79

Closed
geomajor56 opened this issue Feb 24, 2014 · 5 comments
Closed

novice question #79

geomajor56 opened this issue Feb 24, 2014 · 5 comments

Comments

@geomajor56
Copy link

I'm kind of new to Python/Django and this cookiecutter looks like it could save me. I've bought both of your books and I'm trying to stick to one particular school/concept. In your docs you say this won't work with Apache/mod_wsgi due to environment variables. Unfortunately thats the only way I know to deploy on Webfaction. Is it somewhat painless to overcome the constraint?

thanks in advance,

Michael

@pydanny
Copy link
Member

pydanny commented Feb 24, 2014

Unfortunately, there is no painless or even somewhat painless way to work around this issue. At least with cookiecutter-django and it's dependency on django-configurations. See #74, which this ticket arguably duplicates.

For what it's worth, this is why in Two Scoops of Django 1.6 we advocate Apache projects employ secrets files. Perhaps django-configurations will support that at some point.

@pydanny pydanny closed this as completed Feb 24, 2014
@geomajor56
Copy link
Author

Thanks for the quick reply. Looks like Plan B is in order. I don't have one
so I should probably start researching. From a Python/Django newb,
"Deploying Django is hell!!!"

thanks again,

Michael

On Mon, Feb 24, 2014 at 3:03 PM, Daniel Greenfeld
notifications@github.comwrote:

Closed #79 #79.

Reply to this email directly or view it on GitHubhttps://github.com//issues/79
.

@pydanny
Copy link
Member

pydanny commented Feb 24, 2014

Michael, I agree that deployment for Django (and Python) is a royal pain. Hence my advice: "Deploy with a PaaS".

Not using a PaaS means you are playing with an ungainly process that doesn't serve you any real purpose except causing you aggravation. Me, if I'm not using a PaaS, I'm doing it with a Salt or Ansible setup that someone else wrote.

One last thing: Webfaction might be cheap, but Heroku and PythonAnywhere have FREE developer levels.

@pydanny
Copy link
Member

pydanny commented Feb 24, 2014

It's dated now, but http://pydanny.com/you-should-heroku.html definately comes to mind. 😉

@geomajor56
Copy link
Author

Thanks for the heads up,playing with PythonAnywhere, nice.

If you don't mind, I'm struggling horribly with creating a forms in
general. In particular, a model based form(ModelForm). I've used Vanilla
Views with some success via their
examplehttps://github.com/tomchristie/django-vanilla-views/tree/master/example.
But in your book you say Vanilla Views can be a bit quirky so I'd like to
stay away from it.

My question is, is it possible to alter the layout the models fields for
Creating and Editing? I feel like I'm missing a big picture somewhere. Is
crispy-forms what I'm looking for, or is it floppy-forms? , or plain old
Django? I can't seem to find any thorough enough examples for a noob like
me.

If you could point me to any kind of reference, that would be great. I've
been stuck on this for a few days and it would be most satisfying do have a
not so foggy path to follow.

again, thanks in advance,

Michael

On Mon, Feb 24, 2014 at 4:12 PM, Daniel Greenfeld
notifications@github.comwrote:

It's dated now, but http://pydanny.com/you-should-heroku.html definately
comes to mind. [image: 😉]

Reply to this email directly or view it on GitHubhttps://github.com//issues/79#issuecomment-35938175
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants