51–56 of 56 posts
https://github.com/Postleaf/postleaf for those who haven't figured it out yet. I assume the database error is due to some sort of slashdotting effect.
Anyways, the link to GitHub will be on the homepage soon. As I mentioned earlier, the org repo didn't even exist until late last night!
Nice work on the site. I'd give the software a shot on my own server but its sort of hard to give up the WP ecosystem. Any import capability for messages and categories?
Earlier quoted context omitted.
It's not really all _that_ arrogant to say your stuff doesn't suck, is it?
Sure, but in doing so, you're accepting that readers will be looking at what you present within the frame of certain parameters. I agree with the title change. (ctrl-f for 'suck' on this page of comments.)
Earlier quoted context omitted.
Your question is bait? Maybe you are suggesting that PHP+MySQL apps aren't universally terrible. In this case, please state that and defend it. Or you are unaware that PHP+MySQL apps have a history of being terrible. In this case, I am not sure what to say.
Not bait, just curious as to why you'd say that and didn't want to make any assumptions. Sure, I could have built Postleaf in Node, for example. It's all the rage these days. I even considered it, but then I considered my end users who (sadly) still have trouble setting up a basic PHP app on a shared LAMP box. I think part of the allure with Postleaf is the ease of use from the initial install all the way to publishi…
Why? Is it because this dev is clearly trying hard and looking for support?
I'm GIVING support. Much, much more than I got when I was searching altavista for information about how CGI works.
I don't recommend using PHP for your next project.
What's really needed is a WYSIWYG GUI editor that exports all (custom and editable) fields to JSON, so you can use something like Middleman to generate a static site based on that content. This way, anytime someone updates and saves content through the GUI, a script will trigger and re-build your static site based on the new JSON file, and publish to s3. To completely decouple the editing experience (and those who cr…
Earlier quoted context omitted.
Not bait, just curious as to why you'd say that and didn't want to make any assumptions. Sure, I could have built Postleaf in Node, for example. It's all the rage these days. I even considered it, but then I considered my end users who (sadly) still have trouble setting up a basic PHP app on a shared LAMP box. I think part of the allure with Postleaf is the ease of use from the initial install all the way to publishi…
Well, I'm getting downvoted for chatting with you about this. Why? Is it because this dev is clearly trying hard and looking for support? I'm GIVING support. Much, much more than I got when I was searching altavista for information about how CGI works. I don't recommend using PHP for your next project.