6 ms·
Git 1.7.7 changes affecting the everyday developer
- m0shen 15y agoSeems to be down: http://webcache.googleusercontent.com/search?q=cache:johnkary.net/git-1-7-7-changes-affecting-the-everyday-developer/&hl=en&strip=1 http://webcache.googleusercontent.com/search?q=cache:johnkar...
- johnkary 15y agoSorry! Trying to get the server back to normal and responsive. Give me a few minutes. :)
- davidcollantes 15y agoWP Super Cache is your friend. That, or Jekyll. :-)
- mauriciob 15y ago> Adding cache plugins, back up in a sec :) The next thing Google will cache is your maintenance message. You should serve those messages with HTTP 503, not HTTP 200.
- kemayo 15y agoHacker News has been an education for me about how many people don't realize that WordPress will destroy their server without caching.
- herge 15y agoOn that subject, anyone know of good blogging software written in python?
- itsnotvalid 15y agoYou may get away with having some forms of caching. Using python won't help given you have no caching.
- Pewpewarrows 15y agoI haven't seen any blogging platforms written in Python that requires hundreds of queries to render a homepage like Wordpress does in PHP. If your site is running on a single modest server, needs 190 queries to render a page, has zero caching, and gets a spike in traffic then it will go down like a sack of bricks. That same scenario with <10 queries is a completely different story.
- itsnotvalid 15y agoI guess, I am just not using enough of wordpress.
- Pewpewarrows 15y agoIf your site is only a blog, then you really should only be using Jekyll or Hyde to generate it. Having a backend is pretty overkill.
- adambyrtek 15y agoI 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 for your blog. This certainly has some advantages, just don't forget about performance. Or just use a hosted service. TMTOWTDI.
- udp 15y agoI don't know if it's just a fad - what more is a blog backend with a cache plugin doing than generating static HTML? It's more like the universally accepted "right way of doing things" being taken a step further. Why should the system that generates the HTML be the same one that serves it?
- peterjmag 15y agoAnyone know why WordPress doesn't ship with some form of caching?
- jacques_chester 15y agoBecause that's not the Wordpress Way (tm).
- kemayo 15y agoAs 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.
- phatbyte 15y agoI for one welcome our new overlord = HN effect :P
- johnkary 15y agoEnabled WP Super Cache plugin, site should be back and operating as normal.
- ward 15y agoIt isn't, not at the moment anyway.
- weaksauce 15y agoNo indeed; Still down for me in CA.
- n30 15y agodown for me as well.
- pepijndevos 15y agoIt's returning a blank page at blazing speed.
- calloc 15y agoSeems to be 0 bytes long ... at least for me, so it is certainly doing its job in cutting down page size ;-)
- johnkary 15y agoTurns 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.
- manojlds 15y agoeffect of being linked to from HN :)
- dupe123 15y agoThese changes are both awesome. Particularly the one to submodule update. I have a project setup where not everyone has access to all its submodules. Prior to this, people would have to manually run update for each submodule they were allowed to access. Otherwise it would fail part way through on the ones they didn't have access to. Great news!
- manojlds 15y agoSlightly misleading title. Should have been something like Git 1.7.7 benefiting the everyday developer
- johnkary 15y agoSorry, 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.
- skimbrel 15y agoOh, awesome. I use the stash constantly and always run into the wall of having to add untracked files before doing it. upgrades
- bostonvaulter2 15y agoIn particular there was no good way around the untracked files, even with a fairly complex shell script.
- deleted 15y ago[deleted]
- naithemilkman 15y agomaybe he didnt expect to hit frontpage