[bisq-network/proposals] Migrate from Slack to an alternative platform (#54)

[chirhonul]

I have acquired the `bisq.space` domain and performed a basic rocket.chat installation:
* https://bisq.space/

The service runs on a single dedicated server currently:

* CPU: Intel® Celeron® Processor G3900T 2C/2T (2M Cache, 2.60 GHz)
* RAM: 16GB DDR4 ECC
* 1 HDD: 3.5" 1TB 6GB/S SATA3
* 2 HDD: 3.5" 1TB 6GB/S SATA3
* RAID Array: RAID 1 (Mirroring)

I would not recommend migrating over all users yet, since there's no monitoring in place and I've only done very basic testing. There also could be performance issues or need for downtime in the future.

I also have not set up an SMTP email server, which seems to be required to deliver "account activation" emails. However in my testing, new users can join and chat even without clicking the activation link from the emails. I tried signing up for a free sendgrid.com account for this purpose, but it was flagged as "high-risk". I've filed a support ticket with them and can update on any progress here.

There seems to be tools available to export Slack data and import it into rocket.chat:

* https://rocket.chat/docs/administrator-guides/import/slack/

There is also a tool to act as a bridge from Slack <-> rocket.chat:

* https://rocket.chat/docs/administrator-guides/import/slack/slackbridge/

I am writing up operational notes for the installation, and will make a plan for how to monitor the basic health of the service and perform backup and other basic operational tasks. The operational planning also will need include a recovery plan in the eventuality of losing the `bisq.space` domain and/or the server, or suffering prolonged unavailability if I am unavailable in the future. Perhaps having regular backups accessible by a few contributors in addition to clear documentation on how to restore services on a new domain would suffice.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/54#issuecomment-441435523
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181125/4467628e/attachment.html>