Live data from Hacker News

Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

builtbyptm.com

21–30 of 43 posts

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#21
post #17

Earlier quoted context omitted.

The about link is giving me a 404.

Noice, I'll go fix that now. Thanks! You get a free beta invite if you like for finding the bug.

Heh. Whatever nifty location rewriting javascript you're using makes it impossible for me to browse your site - eg. http://www.nutrivise.com/#terms/ just points to your homepage.

Also: the 'terms of use' on that page are bogus. "The most advanced nutrition system [evar!!1!]" vs. "NUTRIVISE MAKES NO WARRANTIES ABOUT THE ACCURACY, RELIABILITY, COMPLETENESS, OR TIMELINESS OF THE MATERIAL OR THE WEB SITE ... WHETHER BASED ON THIRD PARTY INFORMATION OR ON RATINGS GENERATED BY NUTRIVISE." Oh? So what are people paying you for then, if not expert advice that you're willing to stand behind?

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#22
post #8
post #7

I wrote a tool (along similar ideas, starting out is always a needless time sink) called GluStik (punning Paster) https://github.com/leetrout/glustik#default-djangoglu-method... Now GluStik scratched my itch of needing a very specific, custom layout, represented in code, and plopping in Django's files (like settings) so it provides hooks to use Django's templates. I'm curious what sort of design decisions went into p…

We have included settings_local.py for development purposes, which gets imported by settings.py if it can be found. The main purpose for this is for the settings_local.py to be using sqlite3 rather than postgres, which is the default in settings.py. Another thing which is kind of hidden is the ptm1.4 branch. This is a branch that includes a lot more, and will be growing quickly. We wanted the master branch to be gene…

You do see the difference between importing local settings into settings.py and importing both of them from separate modules in a package's init so they can override (per my example), yes?

I feel like you should take a harder look at the modular settings link I included. MUCH better way to solve this problem.

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#23

Earlier quoted context omitted.

Noice, I'll go fix that now. Thanks! You get a free beta invite if you like for finding the bug.

Heh. Whatever nifty location rewriting javascript you're using makes it impossible for me to browse your site - eg. http://www.nutrivise.com/#terms/ just points to your homepage. Also: the 'terms of use' on that page are bogus. "The most advanced nutrition system [evar!!1!]" vs. "NUTRIVISE MAKES NO WARRANTIES ABOUT THE ACCURACY, RELIABILITY, COMPLETENESS, OR TIMELINESS OF THE MATERIAL OR THE WEB SITE ... WHETHER BASE…

The location rewriting is the Backbone router stuff that uses pushState. Pretty common HTML5 stuff, you'd have to be using a moderately old web browser. Most common one we're aware of that's guilty of not supporting this is Firefox 3. What's yours in this case?

This is how terms of use work on most websites. In our case, we're in a particularly tricky situation because the meal plans we lay out have the ability to be incredibly useful to our users, but only if they actually comply with them.

Since compliance isn't something we can ensure without a human being watching them 24/7 (including when they're asleep in case they're sleep-eaters, an actual phenomenon), we have to put in place that terms of use for that reason and others.

Others including situations like people with severe allergies. We cannot guarantee the absence of allergens in recipes/food coming from some of our third party sources. To guarantee as much would endanger the health of our users and would be irresponsible.

I'm sorry you don't feel we don't stand behind our product. We really do stand behind what we do and believe we're working on something that has the potential to help a large portion of westerners with weight issues.

The nutrition researchers and dietitians we work with feel so strongly about our product that it's being used in a weight loss case study involving many subjects that will allow us to further refine our already substantial improvement on the current state of consumer nutrition.

My email is in my profile, contact me if you'd like to discuss this further. I'd be interested to hear what you think we could do to better show we feel confident about our software.

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#24
post #16

You guys would lose your minds with envy if you saw how my company automates Flask :P

I suppose you're not free to show us? ;)

The problem is that a lot of it is hacky and somewhat specific to our site. Not necessarily generalizable.

I will say this though, I've been using Fabric for a very long time and abuse it with glee.

Are there any dev-opsy/provisioning/whatever type pain points you'd like a blog post or exposition on?

Edit: I'm the CTO. I'm open to open sourcing our stuff, but the lack of generalizability makes it less than useful. There's an abundance of magic in our stack that automates everything. Idempotence was a core design goal.

Edit2: For local development, I automate everything surrounding the python packages and the virtualenvs for the various repos we have as well. It's pretty damned handy.

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#25
post #11

Or just have a skeleton/boilerplate code in a repo and clone it for each new project. Here's mine http://github.com/senko/dj-skeletor (feat. south, debug toolbar, raven/sentry, fabric).

Django also allows you to specify project templates https://docs.djangoproject.com/en/dev/ref/django-admin/#star... , very useful.

There is also support for app templates as well if you want to go that far.

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#26

I’m really sorry to get all critical, but if you personally have to SSH into the server to do setup or deployment—especially if you have to be root—you’re doing it wrong. I also feel that if anyone or anything has to SSH into a server for deployment, it could be done better. I use Chef to automate all of this stuff; it's surprising that we have great tools like Chef, Puppet and CFEngine and people still feel the need…

You're right, I should be using these. How's the learning curve? Should I find a tutorial? Which should I choose, and why?

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#27

I’m really sorry to get all critical, but if you personally have to SSH into the server to do setup or deployment—especially if you have to be root—you’re doing it wrong. I also feel that if anyone or anything has to SSH into a server for deployment, it could be done better. I use Chef to automate all of this stuff; it's surprising that we have great tools like Chef, Puppet and CFEngine and people still feel the need…

Of course deploying as root is doing it wrong.

However, I still haven't found enough reason to switch from using SSH for deployment. It's almost always three lines. ssh; git pull; ./manage.py syncdb/migrate/collectstatic.

The only hindrance has been configuring the site to work on the server for the first time, i.e what the site at this link claims to solve.

I've spent several hours on fabric before but gave up when I realised I've spent more time on learning it than the time I spent deploying my code.

Can you tell me what I am missing out? I'm still relatively new to django deployment and I feel I'm missing something but I haven't found it yet.

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#28

Earlier quoted context omitted.

Heh. Whatever nifty location rewriting javascript you're using makes it impossible for me to browse your site - eg. http://www.nutrivise.com/#terms/ just points to your homepage. Also: the 'terms of use' on that page are bogus. "The most advanced nutrition system [evar!!1!]" vs. "NUTRIVISE MAKES NO WARRANTIES ABOUT THE ACCURACY, RELIABILITY, COMPLETENESS, OR TIMELINESS OF THE MATERIAL OR THE WEB SITE ... WHETHER BASE…

The location rewriting is the Backbone router stuff that uses pushState. Pretty common HTML5 stuff, you'd have to be using a moderately old web browser. Most common one we're aware of that's guilty of not supporting this is Firefox 3. What's yours in this case? This is how terms of use work on most websites. In our case, we're in a particularly tricky situation because the meal plans we lay out have the ability to be…

Yep, Firefox 3.6.24. The most up to date one on the version of Linux that I'm using at work. I'm not sure why you/backbone need to rewrite the URL though - surely a vanilla page would work just as well?

I understand compliance, allergies etc. are a tricky issue. There a more narrow disclaimer and/or warning (eg. this recipe contains nuts/gluten/...) would be definitely appropriate, not to mention useful if it were on the actual recipe page.

But that's separate to the information that you're providing - I assume meal plans and exercises? In that case the disclaimers completely overstep the mark, and undermine any claims of competence. Would you trust an engineer who disclaimed all liability should their bridge fall down? Or a doctor who wanted you to waive the right to all negligence suits?

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#29

Earlier quoted context omitted.

Noice, I'll go fix that now. Thanks! You get a free beta invite if you like for finding the bug.

Heh. Whatever nifty location rewriting javascript you're using makes it impossible for me to browse your site - eg. http://www.nutrivise.com/#terms/ just points to your homepage. Also: the 'terms of use' on that page are bogus. "The most advanced nutrition system [evar!!1!]" vs. "NUTRIVISE MAKES NO WARRANTIES ABOUT THE ACCURACY, RELIABILITY, COMPLETENESS, OR TIMELINESS OF THE MATERIAL OR THE WEB SITE ... WHETHER BASE…

Liability.

Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command

#30

Earlier quoted context omitted.

The location rewriting is the Backbone router stuff that uses pushState. Pretty common HTML5 stuff, you'd have to be using a moderately old web browser. Most common one we're aware of that's guilty of not supporting this is Firefox 3. What's yours in this case? This is how terms of use work on most websites. In our case, we're in a particularly tricky situation because the meal plans we lay out have the ability to be…

Yep, Firefox 3.6.24. The most up to date one on the version of Linux that I'm using at work. I'm not sure why you/backbone need to rewrite the URL though - surely a vanilla page would work just as well? I understand compliance, allergies etc. are a tricky issue. There a more narrow disclaimer and/or warning (eg. this recipe contains nuts/gluten/...) would be definitely appropriate, not to mention useful if it were on…

>Yep, Firefox 3.6.24. The most up to date one on the version of Linux that I'm using at work. I'm not sure why you/backbone need to rewrite the URL though - surely a vanilla page would work just as well?

It's not really that simple, it has to do with how Backbone falls back when the pushState functionality is missing and how it interacts with the structure of our site. We're currently looking into better ways to shim/workaround this somewhat lackluster default functionality.

>I understand compliance, allergies etc. are a tricky issue. There a more narrow disclaimer and/or warning (eg. this recipe contains nuts/gluten/...) would be definitely appropriate, not to mention useful if it were on the actual recipe page.

I just listen to the lawyers (and my CEO) on these matters. My job is to build product to help people.

>In that case the disclaimers completely overstep the mark, and undermine any claims of competence. Would you trust an engineer who disclaimed all liability should their bridge fall down? Or a doctor who wanted you to waive the right to all negligence suits?

Would you refuse to work with a doctor because he had malpractice insurance or an engineer because he worked through an LLC? It would be irresponsible for either of them to do without.

You seem to act as if our terms of use is somehow extraordinary when it is anything but.

I'm not here to debate hypothetical circumstances, just make things to help people.

Let me know if you want a beta invite via my email address so you can decide for yourself.

Post reply on HN