Orbit should be usable at https://orbit.chat

Question

Orbit should be usable at https://orbit.chat

haadcode opened this issue 8 years ago · 14 comments

We want to make Orbit available at a nice url with minimal setup and installation to user. The ideal UX here is that user opens https://orbit.chat in their browser and will be able to use Orbit. That's it.

What needs to be done here is to figure out:

orbit-web release process
how we can deploy new version to https://orbit.chat

Deleted user commented 8 years ago

and ipv6

Answer 1 · 2017-01-31T15:39:31.000Z

@lgierth just to verify, we have orbit.chat domain, right?

Answer 2 · 2017-01-31T15:41:03.000Z

yep we have orbit.chat

Answer 3 · 2017-01-31T18:10:31.000Z

@lgierth What do we need to do to get it up at orbit.chat? Is the process to go through https://github.com/ipfs/ops-requests?

Answer 4 · 2017-02-02T15:54:04.000Z

@RichardLitt I think, as long as you can hand over a multihash with the application running, we can pin & deploy it on the domain. As of right now we have no automated way of deploying websites.

Answer 5 · 2017-02-02T18:33:59.000Z

At some point in the last couple of months, I had a chat with @haadcode and we found that having web.orbit.chat to be the hosted web version and orbit.chat to be the entry point where people can find about orbit and download the executables too :)

Answer 6 · 2017-02-03T07:04:52.000Z

having web.orbit.chat to be the hosted web version and orbit.chat to be the entry point where people can find about orbit and download the executables too

Correct. However, as we don't have a website for orbit, yet, and building a separate (from dist.ipfs.io) download page is not in the scope for this sprint, I think the best way forward here is to start with orbit (the web app) being at orbit.chat. There's a task to add a banner "You can also use Orbit as a Desktop app, download here" to the app that points to dist.ipfs.io, which should be trivial. Over time, as we build a proper website for Orbit, we can move the app to web.orbit.chat and have the website at orbit.chat.

@victorbjelkholm is there a way to have this process so that I could deploy it myself to the domain? Who, at the moment, is able to deploy it to the domain? I'm trying to make sure that we don't have a bottleneck between dev and ops and can quickly deploy new versions as needed.

Answer 7 · 2017-02-06T16:03:17.000Z

@RichardLitt orbit-web build process has now been documented, see here https://github.com/orbitdb/orbit-web#distribution-package. That should be all you need from orbit's side to progress with this. Following the instructions, you'll get a folder dist/ (and its multihash) which can be deployed on a web server or as a stand-alone local app. It contains index.html and all the assets orbit-web needs to run.

Answer 8 · 2017-02-06T16:09:53.000Z

@RichardLitt small request: when you start working on this again actively, can you move the card in https://waffle.io/haadcode/orbit to "In Progress"?

Answer 9 · 2017-02-08T17:43:21.000Z

I've added a command to automatically add the hash to ops-requests. A bit overkill, but now it's automated. orbitdb-archive/orbit-web#1

Answer 10 · 2017-02-08T17:49:05.000Z

@haadcode I think this can be closed? Is this done now?

Answer 11 · 2017-02-09T06:24:50.000Z

I'll review this today and check the workflow and tools. Will let you know 👍

Answer 12 · 2017-02-09T16:33:22.000Z

now with ssl: https://orbit.chat

Answer 13 · 2017-03-22T12:51:41.000Z

This has been completed now. We have been deploying latest version of orbit-web to orbit.chat for a while now. With the latest merges to master, we now have the deployment process documented at https://github.com/orbitdb/orbit-web#publish.

Thank you everyone for making this happen, it's been a long road since last summer but we now have https://orbit.chat working and integrated into our workflow! 😄 🏅 ❤️ 🎉