Discourse as a GTD Reference Repository

gtd
Discourse as a GTD Reference Repository
0

#22

Wondering if I could install it on my webfaction server where I host my blog.


(Joe Buhlig) #23

As long as you can run Docker:

I will say that it’s usually not worth it. The $5 a month isn’t much to ask I don’t think.


(Curtis Spendlove) #24

I’ve not heard of webfaction before, but as long as it is a VPS “server” host, you should be ok.

If it is something like a shared PHP “Wordpress” host, then probably not.

I agree with Joe, though, this setup is pretty amazing for $5/month.


(Justin DiRose) #25

I just spun a personal instance up alongside my Wordpress micro.blog instance on a $5 droplet. Works like a charm. If anyone needs help, let me know :slight_smile:


(Curtis Spendlove) #26

Just checking in. So far this experiment has been going quite well. I’m very happy with it.

I’ll try to have some stuff to share soon. (No guarantees, I’m horrible at being too self conscious to show many workflows.)

:slight_smile:


(Joe Buhlig) #27

I’m definitely curious about half-baked systems. I share mine all the time. :wink:


(Wilson Ng) #28

Our lives are a half-baked system. We just gotta keep turning the grilled steaks a little more…

I think I’m always trying to break through that barrier of being self conscious in real life situations. It’s easier when you’re on the keyboard. Give it a go! I’m always game for constructive critiques of my workflow when I post here!


(Mike N) #29

Is there a way to default closed topics to the bottom of a category? i.e. Open topics are sorted by date with closed always at the bottom?

Not sure if my google skills are weak or that isn’t possible.


(Joe Buhlig) #30

You can set up a category with an “Auto-Close” timeframe. And then you can append ?status=open to any topic list URL to remove all the closed topics from the list.


(Brett McHargue (The Ruby Troubadour)) #31

So I’m on a new team and they are willing to try out Discourse. For my sins in suggesting though, I have been tasked with setting it up. We are currently running everything on Heroku, so that would be the best place for me to do it, but it looks like that may be difficult. If I go with Digital Ocean I need to go have a chat with the man with the credit card. Have you ever set Discourse up on Heroku? Or know anyone who has?


(Justin DiRose) #32

I personally don’t know but you might be able to with Heroku’s Docker support, as the supported install of Discourse uses Docker. That being said, a small team can easily run off a $5/mo DO droplet.


(Joe Buhlig) #33

Save yourself the headache. I’ve seen this attempted a couple times and even experienced Discourse installers have a rough time with Heroku. I’ve not seen it completed successfully. It’s worth the $5 that @justindirose mentioned to follow the standard setup on Digital Ocean.


(Brett McHargue (The Ruby Troubadour)) #34

While I am inclined to agree, it really is a shame. It means setting up yet another service to keep track of. We do have some services on AWS (S3 and Cloudfront) so I will try there first.

thanks!


(Joe Buhlig) #35

I’ve not run it myself, but I’ve heard of some folks having luck with this tutorial for AWS: