New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Maybe I need to hack the part of themes today
I generally like Ghost, but I haven't been able to really use it for anything quite yet. As soon as they get more standardized comments, page support, and a few other things I may start to transition some of my WordPress blogs over to this platform.
I find Node.js a lot easier to work with than PHP. Lately I've been messing around with creating some new templates, and trying to make templates that match my WordPress templates.
awww, love the simple blog.. definitely gonna try it.. thanks for sharing!
I would just stick with Wordpress.
can I install it to any directories?
can I install on server that has sveral website? I just scared it would mess up with any setting made by my other domain.. Im using virtualmin btw..
It isn't fully equipped with all the the bells and whistles as of v3.*, they still have a long way to go (fixing bugs and deploying the new features as per their Roadmap — https://github.com/TryGhost/Ghost/wiki/Roadmap).
However, I must confess. I love the idea behind Ghost, keeping blogging simple and focusing more onto the meat; the content.
I'll put it this way though, It's WordPress done right. Oppss!
(remember the good ol' days when WP v1.* used to \m/)
PHP vs Node.JS — I'm not gonna jump into that bandwagon.
@psycholyzern It runs as its own web server on its own port. Just make sure if you use port 80, you give NodeJS its own IP address. Otherwise it wont even start.
@Francisco and his BuyVM team has already got a OVZ template up and running with Ghost pre-installed for those who wants to try them:
PHP spawns a process for every request, node doesn't, node wins.
What. Learn yourself some FastCGI or PHP-FPM.
Got the Ghost.org template working on my BuyVM VPS:
Which still use a single process per request.
Well it is not spawned to handle the request and then dies. There is a pool of long-lived processes which handle all the coming requests. And the reason for there being "a pool" to begin with, is primarily multi-threading/multi-core efficiency. Describing this as "a process per request" is really misrepresenting it for the worse.
No, that's simply how it works, except for that FPM reuses processes.
PHP to serve websites can hog up icredible amount of resources or be very slow (because it's queueing) please just stop denying that lol...
No it's not misrepresenting it, it's exactly what it is. Regardless whether it's in a pool or not, one child does one job then goes back to sleep. You still have to have one process for every request that will be served at once.
Node therefore wins at this particular aspect because it can reach or exceed the same level of performance with a single event loop.
I'm in no way dissing PHP. My job consists primarily of PHP, but that being said I've been messing with Node for some time and it definitely has some strong pluses. As such I don't think its cool that you push it aside because you have a few broken rendering libs on your system and blame Node when it has nothing to do with the client side.
I wonder how well does that super advanced technology "single event loop" working out for it on a 8-16 core CPU. Or are you supposed to run 8-16 instances of node.js to fully utilize your cores?
Indeed, you are. Node.js doesn't support multiple CPUs.
I set up a blog as soon as Ghost came out the other week, then I realized I don't like to write or blog
true! i have a feeling i will end up that way too..
Ha, that's usually how I end up. I actually like to write I just find it hard to initiate the topics.
I'm on day #6 with Ghost blog at http://ghost.centminmod.com - like it alot !