Provide a quick way to deploy Openwhyd to DigitalOcean

openwhyd.org is an open-source music platform used daily by thousands of users to create playlists of songs from the web (Youtube, Soundcloud, etc…), and discover musical gems from similar users.

Tech stack: Node.js, MongoDB, Docker, Mocka, Webdriver.io, jQuery, Electron + iOS app

---

Goal

Doing this would allow anybody to run their own Openwhyd server online, on their own DigitalOcean account.

There are several ways this could be achieved:

• Write and publish a guide on how to deploy to a new DigitalOcean droplet => markdown file in the docs folder
• Make Openwhyd’s repo deployable in one click (see https://www.digitalocean.com/products/one-click-apps/), e.g. by using our docker image (see our Dockerfile)

Context: As DigitalOcean renewed their sponsoring of Openwhyd, they kindly asked if we could add that functionality to our open-source project, cf Kamal’s email:

create a guide on how to deploy their project on DigitalOcean or write a blog post on how they are using DigitalOcean to host their project.

I saw that you use Docker, so it can be a short guide on spinning up a Droplet using the Docker one-click image and setting up the containers.

---

Howto

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to install, setup and run Openwhyd on your computer: INSTALL.md
• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

[uLan08]

This looks interesting! I have read your initial discussions and for now I agree with using a wrapper to handle the OAuth process, but I’ll have to dive in deeper and see. I’ll let you know what I think then.

[adrienjoly]

Awesome!

I think that Brawrdon is on it, so I guess that you could offer your help. Or take over if he no longer wants to do it.

Otherwise, if you’re into back-end, there’s a project that may be interesting for you and that on which your contribution could have a huge impact on Openwhyd’s future: find a way for external clients/front-ends to auth & connect to Openwhyd’s API. (see issue #55)

I was thinking of adding a OAuth layer to Openwhyd’s back-end, but we’re open to other solutions, as long as we don’t make too many changes to the current back-end codebase. Ideally, the proposed solution would either wrap around or proxy Openwhyd’s existing API.

How does that sounds? I’d love to read your ideas and suggestions in issue #55, if you have any! ^^