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.
Three hours later still not working, at least on Chrome/Ubuntu. Just FYI.
Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
31–40 of 43 posts
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#32Earlier quoted context omitted.
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. Th…
Sure, write on a generalized approach for deploying a Flask app with Fabric, virtualsenvs, and whatever else you use.
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#33I’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…
Cool story bro.
Did you look at the actual main aspect of this simple tool, or just the one folder with the server-script? As previously mentioned. The main aspect of this is the automatic _Django Project Builder_, not "a collection of fragile scripts to get basic stuff done".
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#34Earlier quoted context omitted.
Noice, I'll go fix that now. Thanks! You get a free beta invite if you like for finding the bug.
Three hours later still not working, at least on Chrome/Ubuntu. Just FYI.
It's deployed now. I didn't want to deploy the fix until I got home where I have reliable internets. :)
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#35Earlier quoted context omitted.
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. Th…
Sure, write on a generalized approach for deploying a Flask app with Fabric, virtualsenvs, and whatever else you use.
I'll see if I can distill what I've learned so far. It'd be a pretty boring/long post though.
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#36Earlier quoted context omitted.
Have any Flask projects in the wild for us to see? The "Powered by Flask" section in the Flask docs is full of quick toy projects.
http://www.nutrivise.com/
On the frontpage, under the "Real world flexibility" header, the tab reads "Swap any meal you don't like with a nutritionally"
I think it got cut off when rendering to an image.
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#37I’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…
Idempotence, edge-cases, compliance ensurance.
What if you want to redeploy a configuration change to your web servers? What if you want to ensure such changes get re-deployed everytime a change is made to a config file?
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#38Earlier quoted context omitted.
Sure, write on a generalized approach for deploying a Flask app with Fabric, virtualsenvs, and whatever else you use.
I'll see if I can distill what I've learned so far. It'd be a pretty boring/long post though.
Great, I'll be looking forward to it. Cheers!
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#39Earlier quoted context omitted.
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…
One solution to the lack of pushState is to just offer the non-JS version of your website to such old browsers. Easiest way to do that is to have the JS bits disable themselves if pushState isn't found.
Re: Show HN: Pre-configured Django project, Git repo, and virtualenv with 1 command
#40Earlier quoted context omitted.
>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…
One solution to the lack of pushState is to just offer the non-JS version of your website to such old browsers. Easiest way to do that is to have the JS bits disable themselves if pushState isn't found.
Or, you know, just use regular links. That part of the site isn't a web app, it's just a regular web page. Why make things more complicated than they have to be?
edit: Particularly when I just tried it at home in Chrome, and it ended up at http://www.nutrivise.com/terms/ anyway. Or did you come to the same conclusion re: links?