A music player that connects to your cloud/distributed storage.
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Add note about "hosting it yourself" to the README

+25 -3
+25 -3
README.md
··· 21 21 - [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) <small>(browser)</small> 22 22 - [IPFS](https://ipfs.io/) 23 23 - [RemoteStorage](https://remotestorage.io/) 24 - - [~~Solid~~](https://solid.inrupt.com/) <small>(TODO)</small> 25 24 - [Textile](https://github.com/textileio/go-textile) 26 25 27 26 #### Music layer ··· 32 31 - [~~Blockstack Gaia Storage~~](https://github.com/blockstack/gaia) <small>(TODO)</small> 33 32 - [Dropbox](https://dropbox.com/) 34 33 - [Google Drive](https://drive.google.com/) 35 - - ~~HTTP Server~~ <small>(TODO)</small> 36 34 - [IPFS](https://ipfs.io/) 37 35 - [WebDAV](https://en.wikipedia.org/wiki/WebDAV) 38 36 ··· 42 40 43 41 44 42 45 - ### Development 43 + ### Hosting on your own server 44 + 45 + Diffuse is a static web application, which means it's just HTML, CSS and Javascript. No REST API, database, or anything backend-related involved. That said, the app does require a HTTP web server so it can have "clean urls". It also requires one special rule, and that is, no matter which HTML page is requested, it should always render the root `200.html` or `index.html` file. `https://diffuse.sh` uses Netlify, which in turn uses the `_redirects` file for this. 46 + 47 + In short: 48 + - Diffuse is a static, serverless, web application 49 + - Diffuse requires a HTTP server 50 + - Always render root `200.html` or `index.html` file 51 + 52 + ```shell 53 + # Example of a nginx configuration 54 + # Disclaimer: I'm not confident this'll actually work, 55 + # but it should be something along these lines. 56 + location ~ .html$ { 57 + try_files $uri /200.html; 58 + } 59 + ``` 60 + 61 + 62 + 63 + --- 64 + 65 + 66 + 67 + ### Building it yourself 46 68 47 69 For version numbers, 48 70 see `.tool-versions` and `stack.yaml`.