search

orbitdb-archive / orbit

A distributed, serverless, peer-to-peer chat application on IPFS
MIT License
1.64k stars 117 forks source link

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

Closed haadcode closed 7 years ago

haadcode commented 7 years ago

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:

haadcode commented 7 years ago

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

ghost commented 7 years ago

yep we have orbit.chat

RichardLitt commented 7 years ago

@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?

victorb commented 7 years ago

@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.

daviddias commented 7 years ago

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 :)

haadcode commented 7 years ago

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.

haadcode commented 7 years ago

@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.

haadcode commented 7 years ago

@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"?

RichardLitt commented 7 years ago

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

RichardLitt commented 7 years ago

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

haadcode commented 7 years ago

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

ghost commented 7 years ago

now with ssl: https://orbit.chat

ghost commented 7 years ago

and ipv6

haadcode commented 7 years ago

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! 😄 🏅 ❤️ 🎉