Oh, awesome. I use the stash constantly and always run into the wall of having to add untracked files before doing it. upgrades
In particular there was no good way around the untracked files, even with a fairly complex shell script.
Git 1.7.7 changes affecting the everyday developer
41–48 of 48 posts
Re: Git 1.7.7 changes affecting the everyday developer
#42Slightly misleading title. Should have been something like Git 1.7.7 benefiting the everyday developer
Sorry, it wasn't my intention to be misleading. I'll give it more thought next time. I see how "changes" could be deemed with a negative connotation in that context.
Re: Git 1.7.7 changes affecting the everyday developer
#43Re: Git 1.7.7 changes affecting the everyday developer
#44Hacker News has been an education for me about how many people don't realize that WordPress will destroy their server without caching.
Anyone know why WordPress doesn't ship with some form of caching?
As I understand it, basically two reasons:
1. WordPress is very proud of its quick-setup process, and caching needs to be configured away from the defaults on a non-trivial number of systems.
2. Using caching makes your blog less dynamic. Things like "latest comments" don't update immediately across your site. Users who haven't explicitly installed caching don't necessarily understand why this isn't a bug.
So WordPress makes it really easy to install a caching plugin, and lets the tiny number of blogs that get enough traffic to need it install it themselves.
Re: Git 1.7.7 changes affecting the everyday developer
#45Earlier quoted context omitted.
I really like the simplicity of this approach. It reminds me of late 90s, when I used Makefiles to compile complex web pages from a set of templates. But it seems like static site generators became a fad recently, like Rails a few years ago, and this makes me slightly skeptical. It's always suspicious when somebody claims there is only one right way to do something. When it comes to me, feel free to have a backend fo…
> But it seems like static site generators became a fad recently, The year 1994 called and would like to talk to you about your backward flowing sense of time and fads. :) In all seriousness... when the Web was born (on Tim Berner-Lee's computer) it was pretty much just static HTML reached by HTTP. Then folks added static file generation, optionally, behind the scenes. Then techniques like CGI to make it dynamic each…
Fashion often returns, and this doesn't apply only to apparel. Thanks for a history lesson, but I never claimed this is a wrong approach, just not the only reasonable one.
Re: Git 1.7.7 changes affecting the everyday developer
#46Earlier quoted context omitted.
I really like the simplicity of this approach. It reminds me of late 90s, when I used Makefiles to compile complex web pages from a set of templates. But it seems like static site generators became a fad recently, like Rails a few years ago, and this makes me slightly skeptical. It's always suspicious when somebody claims there is only one right way to do something. When it comes to me, feel free to have a backend fo…
> But it seems like static site generators became a fad recently, The year 1994 called and would like to talk to you about your backward flowing sense of time and fads. :) In all seriousness... when the Web was born (on Tim Berner-Lee's computer) it was pretty much just static HTML reached by HTTP. Then folks added static file generation, optionally, behind the scenes. Then techniques like CGI to make it dynamic each…
Fashion often returns, and this doesn't apply only to apparel. Thanks for a history lesson, but I never claimed this is a wrong approach, just not the only reasonable one.
Re: Git 1.7.7 changes affecting the everyday developer
#47Earlier quoted context omitted.
Though not written in Python, I'm a fan of Jekyll ( https://github.com/mojombo/jekyll ). You write your entries in Markdown, it converts them to HTML, sets up links and embedded content, and then publishes them to your server via Git to be served up by Apache, Nginx, etc.
The Python equivalent is, of course, Hyde ( http://hyde.github.com ).
Also blogofile(http://www.blogofile.com/)
Re: Git 1.7.7 changes affecting the everyday developer
#48Enabled WP Super Cache plugin, site should be back and operating as normal.
It's returning a blank page at blazing speed.
Turns out the problem was an issue between APC and WP Super Cache. After WPSC tried to run garbage collection on cache files (a cron, configured in the plugin's settings), the server would end up then returning a 500 error. I'm still not entirely sure why, but I disabled APC for now and things are running as they should.