Further adventures in IndieWeb prettygoodhat.com
Micro.blog
@alans great setup! How’d you find standing up your own instance of quill? I’ve thought about doing that but haven’t taken the time to do it yet.
@alans This looks great. And inspires me to pick up my adventures from where I left them. And there are many components common in your setup with mine. So I know this will work out.
@eli Quill was actually pretty easy to get working! I opted to use sqlite for the DB so I wouldn't have to fuss with mySQL and my web host's control panel. Finding the right places to enable annotating a like-of post was a little more involved, but turned out to be straightforward once I had traced through the data flow.
@jack My impression has always been that your act is quite well put together! But I'm glad to be of motivation help :) This m.b indie community is extremely motivating for me, generally.
@seishonagon @amit Now that I understand the pieces it's easy to look back with a lot of comprehension, but there's definitely a learning/implementation curve. I'm really, really satisfied with having figured it out and joined up all the pices that I'm using so far. (Of course, my host made a change that temporarily broke things today! Aaaack.)
@alans did you have to futz with a .htaccess file to handle the routing? I've got everything set up — and I can't get the login page to resolve if I navigate directly to the public directory, but I'm not getting the rewrite to work
@eli Ah, I forgot about that detail. I started to try the .htaccess config, then found that my host control panel could remap the web root for me. So I just set it to the repo’s public directory that way and avoided figuring it out by myself with .htaccess.
@alans ah, that makes sense. Thanks! Time to have some fun with symlinks to see if I can get quill up and running!
@seishonagon it can most certainly be daunting — quill is documented, but spareslly, especially if you haven't done much config. before. Luckily, there area already a couple of publicly accesible instances of quill, so it isn't necessary to host your own to use. As soon as I'm sure mine is up and running a-okay, I'll post a link to it for others to use.
@seishonagon Oh man. I don’t know a single thing about Nginx. 😬 I think Quill works best when its public folder is placed at the root level of a domain or subdomain.
@eli I’ve tried to use the original public one. But really, I don’t see the benefit of using this rather than mars edit, e.g.
@seishonagon there isn't a heap of benefit to using it over marsedit if you are running WP already. My website leverages the micropub to handle all posting, so it isn't (currently) compatible with marsedit.
@seishonagon No, in my case I put quill as a sub domain of my primary one, so it doesn’t add any cost. (I’m on a $5 per month plan from Pair and it’s meeting all my needs really well.)
@eli given @danielpunkass ‘s participation around here, i may just wait to see what he comes up with around micropub...
@alans damn man, I started out knowing sqrt(feck all) about nginx and subdomains. Now I have like ten subs. If I’d known you were struggling I’d have popped in.
@dgold Thanks! Fortunately I'm on Apache and haven't had to solve any Nginx issues, but @seishonagon may be working on Nginx and subdomains.
@seishonagon I’m not sure what you mean.
Nginx files live under /etc/nginx/ , you set the document root in the nginx server block. They don’t need to be uploaded anywhere.
@seishonagon I need to get my head on straight about Micropub. When I looked at it before it was missing something (maybe downloading existing posts?) that made me think I had to wait.
@seishonagon Butting in here, but typically a single database can be used to host data from multiple apps. WordPress has a "prefix" option to make sure any of its tables don't conflict with other apps (even other WP instances).
@danielpunkass it has an editing context, but I think you are right that it doesn’t support a generic way to retrieve a list of all past posts. @aaronpk does that sound right to you?
@eli I wouldn't say it's "not supported" so much as hasn't been spec'd yet. Most of the clients so far are posting clients not editing clients. I would love to see that part of the spec fleshed out tho!
@eli Welcome to the bleeding edge! I tend to take a pragmatic approach to writing specs. Don't put something in the spec til there's a demonstrated need for it. Would love to start brainstorming this here: https://github.com/indieweb/micropub-extensions/issues
@alans Agreed. When I got to it, I wasn’t sure what I will gain out of this. It was more of a learning experience. But then I started posting from multiple clients and that itself proved I was on the right track.
@danielpunkass no worries, I didn’t mean you had to. More that I had better wait for somebody to do it right. After all I almost lost ALL my dB tinkering yesterday, because “backups? Who has time for backups?”