While custom domain for emails would be cool, I don’t know of any tools which restrict or permit account access by a user’s email domain, but instead simply by inviting people to a group using arbitrary email addresses.
Yeah, that sounds good. Several months ago I created a group in DigitalOcean named “PureScript Community” and moved a snapshot of the existing Discourse instance over to it, but I discovered the new instance rehydrated from that snapshot had a new IP address, which meant I couldn’t change the https://discourse.purescript.org DNS entry to point to it. I believe that was the only blocker for doing that.
@hdgarrood, did you create a group for this on your account? I don’t know whether who creates the account affects anything, or if ownership of a DigitalOcean group can be transferred.
@chexxor yeah I created a group a couple of days ago. Up to you: I’m happy to use the one you created already, or to invite you to the one I created. It might be easier to use the one you created already if you already have a snapshot with Discourse all set up.
Oh also, another thing that occurred to me is that it might be nice to put each app on a separate droplet, for the sake of security, easier monitoring, and so that if one app misbehaves it doesn’t affect the others. But that might cost more and complicate things a little. Perhaps we should just get the Discourse instance up and running first.
Something I mentioned before but just want to reiterate here — in addition to server access, members also ought to have access to the repositories for things like Pursuit, Try PureScript, the website, etc. in order to make updates for things like new releases.
I invited @hdgarrood to the DigitalOcean Team I used for the instance hosting Discourse. We might need to cooperate to move the instance from my DO account to the Team one because it involves taking a snapshot and transferring it, which can mean posts to the old instance would be lost while the new one gets up and DNS pointed to it.
Also, @gabejohnson recently pointed out to me that discourse offer free hosting for OSS: https://blog.discourse.org/2018/11/free-hosting-for-open-source-v2/ I think this is worth seriously considering, as this way we no longer need to worry about things like updates and backups, and it’s free up until we reach 50k page views per month (at the moment I think we are around 25k so plenty of headroom).
I think that’s a good idea – I’d rather be able to leave responsibility for updates, backups, etc. to the company that develops the platform itself. I’d prefer this to the AWS credits.
I just had a look (at opencollective) and the page still says “Don’t make any more contributions” … take your time by all means, but know that I for one am itching to become a backer.
Update: I have Pursuit running on a DigitalOcean box with IP address 206.189.189.151. If you put an entry in your /etc/hosts file for that IP address like this
206.189.189.151 pursuit.purescript.org
then you can have a play with it. You may also need to temporarily disable your browser cache using developer tools, as the current Pursuit instance has a 301 redirect set up from http to https. I also have some code in a branch to handle automatic deployment, although that’s not quite all set up properly yet, there are still a couple of kinks to work out. The only remaining things to set up for the Pursuit instance itself are SSL, the domain name, and automatic database backups.