# LibreTime Demo site

**URL:** <https://discourse.libretime.org/t/libretime-demo-site/82>\
**Category:** Community\
**Created:** [January 11, 2018, 11:35pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82 "2018-01-11T23:35:29Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [September 9, 2019, 11:21pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/22 "2019-09-09T23:21:46Z")

</div>

> [@Togar](#):
>
> I’m feeling that a community radio station is worthy of its own thread

Possibly we could include [LibreTime radio in a beta](https://discourse.libretime.org/t/any-interest-in-libretime-available-as-a-saas-with-hosting-and-support/121/18)?

---

<div class="post-metadata">

**Author:** ![paddatrapper](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/paddatrapper/32/675_2.png) [@paddatrapper](https://discourse.libretime.org/u/paddatrapper)\
**Post date:** [October 8, 2019, 7:15pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/23 "2019-10-08T19:15:09Z")

</div>

I like the idea of a team-managed instance, but it performs a different function to a demo site. The demo allows potential users to try out LT so that they can evaluate if it works for what they need. A team-managed stream doesn’t allow this, rather it just demonstrates that the team has good tastes in music 🙂

---

<div class="post-metadata">

**Author:** ![k054](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/k054/32/489_2.png) [@k054](https://discourse.libretime.org/u/k054)\
**Post date:** [May 10, 2021, 6:42pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/24 "2021-05-10T18:42:07Z")

</div>

I have space/resources in a server and I can set it up there. All I would need afterwards would to have [demo.libretime.org](http://demo.libretime.org) pointed there I guess.

I would like it to be a Debian 10 vps (I’m currently running 5 LT instances on that setup), but I’m fine with any.

---

<div class="post-metadata">

**Author:** ![paddatrapper](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/paddatrapper/32/675_2.png) [@paddatrapper](https://discourse.libretime.org/u/paddatrapper)\
**Post date:** [May 10, 2021, 8:38pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/25 "2021-05-10T20:38:42Z")

</div>

@k054 that would be great if you’re open to running that. The thing I’m concerned with is how to reset the instance regularly to some known base state. That way users can test, but there are no lasting changes that could cause issues

---

<div class="post-metadata">

**Author:** ![k054](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/k054/32/489_2.png) [@k054](https://discourse.libretime.org/u/k054)\
**Post date:** [May 10, 2021, 8:51pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/26 "2021-05-10T20:51:57Z")

</div>

I think we can just create some demo content and `cat demo-condent.sql | mysql libretime` to restore it via cronjob once a week or something.

---

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [May 10, 2021, 8:53pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/27 "2021-05-10T20:53:09Z")

</div>

Would it make sense to see if Digital Ocean could provide a similar setup like they do for AzuraCast? [https://docs.azuracast.com/en/home#friends-of-azuracast](https://docs.azuracast.com/en/home#friends-of-azuracast)

> [@LibreTime Demo site](https://discourse.libretime.org/t/libretime-demo-site/82/20):
>
> A LibreTime radio station sounds like a great idea, but probably would be in addition to a demo site? With regards to hosting, it looks like [DigitalOcean](https://www.digitalocean.com/) provides server resources for similar OSS projects like AzuraCast [https://www.azuracast.com/about/#friends-of-azuracast](https://www.azuracast.com/about/#friends-of-azuracast) Might be worth seeing if they’d sponsor LibreTime? Either way, we should be able use [https://opencollective.com/libretime](https://opencollective.com/libretime) to offset any hosting cost. Especially if LibreTime radio provides opportunities to credit sponsors an…

There may some additional marketing/partnership benefits if we went that route. I believe setup and maintenance could still be a separate expense whoever is doing it could be reimbursed for (if needed). Seems like that would be one of the more straightforward costs in [OpenCollective Spending Proposal - #13 by paddatrapper](https://discourse.libretime.org/t/opencollective-spending-proposal/806/13)

---

<div class="post-metadata">

**Author:** ![k054](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/k054/32/489_2.png) [@k054](https://discourse.libretime.org/u/k054)\
**Post date:** [May 10, 2021, 9:02pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/28 "2021-05-10T21:02:22Z")

</div>

I really don’t mind where it’s hosted but I don’t have the time/energy to figure out what does it take for DO to provide that, and I know I can deploy a vm in our server in less than a minute (we have a fai server for that).

If you want to reach DO and ask I’m perfectly fine. All we would need is ssh access and root privileges.

---

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [May 10, 2021, 9:18pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/29 "2021-05-10T21:18:22Z")

</div>

I’m asking around just to see what Digital Ocean might be able to provide to projects using [Open Source Collective](https://opencollective.com/opensource) as their fiscal host/sponsor.

I’m sure the decision-makers are totally good w/ you hosting on your server if that’s easier. Seems like sponsor credit would be a good way to reciprocate on top of reimbursement for associated costs.

---

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [May 11, 2021, 7:28pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/30 "2021-05-11T19:28:55Z")

</div>

FWIW I’m having some asynchronous conversation with the head of product at Open Collective about leveraging their nonprofit entity (which in turn is LibreTime’s entity) for free tiers and discounts.

We’re agreeing that a project like LibreTime could list [Open Source Collective 501c6](https://www.oscollective.org/) in their application (if needed) and they wouldn’t really need to go beyond that…like brokering special deals on behalf of the 2500+ that use them for fiscal sponsorship.

The problem is it takes a lot of time for a project like LibreTime to just search around for vendors offering free tiers and discounts.

The solution would be if OpenCollective provided a searchable marketplace where projects tapped for resources (like LibreTime) could find what they need.

Again this wouldn’t be relevant if @k054 is providing the demo site (we just need to make sure the [Governance and spending policy](https://discourse.libretime.org/t/opencollective-spending-proposal/806) covers all associated costs.

It could be if LibreTime would like additional tools like [the ones AzuraCast is using](https://github.com/AzuraCast/AzuraCast/blob/main/README.md#friends-of-azuracast).

---

<div class="post-metadata">

**Author:** ![LoudLemur](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/loudlemur/32/418_2.png) [@LoudLemur](https://discourse.libretime.org/u/LoudLemur)\
**Post date:** [August 7, 2021, 7:35am UTC](https://discourse.libretime.org/t/libretime-demo-site/82/31 "2021-08-07T07:35:10Z")

</div>

I don’t have an objection, but I do have a concern.

Arranging to have a LibreTime demo setup on AWS (Amazon Web Services) would be convenient, however Amazon, like other big data companies, have a history of censorship. If the LibreTime community invest time and skills in setting up an instance, it should be platform independent. The skills LibreTime learn and teach should be applicable to any platfrom, rather than specific to one.

---

<div class="post-metadata">

**Author:** ![LoudLemur](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/loudlemur/32/418_2.png) [@LoudLemur](https://discourse.libretime.org/u/LoudLemur)\
**Post date:** [August 7, 2021, 8:15am UTC](https://discourse.libretime.org/t/libretime-demo-site/82/32 "2021-08-07T08:15:26Z")

</div>

Ghost is Free Software, and has an option for custom applications. That might be one possibility:

> **[Custom Integrations](https://ghost.org/integrations/custom-integrations/)**
>
> How to create custom API and webhook based integrations for the Ghost publishing platform, full developer documentation and guide.

---

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [August 16, 2021, 10:48pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/33 "2021-08-16T22:48:24Z")

</div>

> [@LibreTime Demo site](https://discourse.libretime.org/t/libretime-demo-site/82/24):
>
> I have space/resources in a server and I can set it up there. All I would need afterwards would to have [demo.libretime.org](http://demo.libretime.org) pointed there I guess. I would like it to be a Debian 10 vps (I’m currently running 5 LT instances on that setup), but I’m fine with any.

We could just accept @k054’s kind offer. Looks like there could be enough funds to cover the setup and ongoing hosting cost [LibreTime - Open Collective](https://opencollective.com/libretime#category-BUDGET)

---

<div class="post-metadata">

**Author:** ![paddatrapper](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/paddatrapper/32/675_2.png) [@paddatrapper](https://discourse.libretime.org/u/paddatrapper)\
**Post date:** [August 17, 2021, 2:26pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/34 "2021-08-17T14:26:41Z")

</div>

> [@paddatrapper](#):
>
> @k054 that would be great if you’re open to running that.

I did, just waiting on things to happen

---

<div class="post-metadata">

**Author:** ![LoudLemur](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/loudlemur/32/418_2.png) [@LoudLemur](https://discourse.libretime.org/u/LoudLemur)\
**Post date:** [September 14, 2021, 1:06pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/35 "2021-09-14T13:06:29Z")

</div>

Hello, k054! It would be great if you helped LibreTime setup a demo website. What is the latest on this? Did you receive any assistance?

---

<div class="post-metadata">

**Author:** ![LoudLemur](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/loudlemur/32/418_2.png) [@LoudLemur](https://discourse.libretime.org/u/LoudLemur)\
**Post date:** [December 7, 2021, 3:25pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/36 "2021-12-07T15:25:27Z")

</div>

This issue was started in January 2018. It is now nearly January 2022 and LibreTime is without a demo.

Supporting LibreTime on Cloudron would be a fantastic way to have a demo, as the Cloudron team would likely host it and make most of the functionality available for trial. In addition, supporting LibreTime on Cloudron would mean deployment of LibreTime would be as easy as one-click. (So would upgrades!)

If anybody has the skills to make this happen, I hope you try. A lot more people would be able to see what LibreTime is like and be able to use it.

---

<div class="post-metadata">

**Author:** ![LoudLemur](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/loudlemur/32/418_2.png) [@LoudLemur](https://discourse.libretime.org/u/LoudLemur)\
**Post date:** [January 18, 2022, 8:53pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/37 "2022-01-18T20:53:41Z")

</div>

Happy Birthday Request! :party:

It is 4 years today since the initial request for a LibreTime demo site. Will we have a nice surprise birthday present, like a LibreTime Docker image for Cloudron?  
🎂

---

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [April 11, 2022, 9:59pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/38 "2022-04-11T21:59:42Z")

</div>

I’m not quite sure what’s prevented this from happening. If it’s a funding issue, possibly @k054 or anyone else still able/interested in providing (or helping set up) could read over the [LibreTime Spending Policy](https://github.com/libretime/organization/blob/main/spending.md) and file the [appropriate Github issue](https://github.com/libretime/organization/issues/new/choose).

---

<div class="post-metadata">

**Author:** ![LoudLemur](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/loudlemur/32/418_2.png) [@LoudLemur](https://discourse.libretime.org/u/LoudLemur)\
**Post date:** [April 14, 2022, 9:22am UTC](https://discourse.libretime.org/t/libretime-demo-site/82/39 "2022-04-14T09:22:14Z")

</div>

As far as I can see, it is quite difficult to create a Docker image for LibreTime. @paddatrapper is trying to produce one. Once that has been accomplished, we will hopefully then be able to support LibreTime on Cloudron. Cloudron would then have a demo, as happens with all Cloudron applications.

The length of this whole process makes me wonder if there are just too few developers working on LibreTime for it to be considered a viable tool. If @paddatrapper ever dropped out of the picture, I have a feeling that the whole project would grind to a halt.

Anyway, lets hope there is a Docker and Cloudron soon!

---

<div class="post-metadata">

**Author:** ![joola](https://avatars.discourse-cdn.com/v4/letter/j/cab0a1/32.png) [@joola](https://discourse.libretime.org/u/joola)\
**Post date:** [April 14, 2022, 5:56pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/40 "2022-04-14T17:56:28Z")

</div>

The difficulty in making the docker image work mainly comes from the fact that the software has been edited by many different contributors without having a global architecture guidance to allow to run in isolated environment. This means a lot of code needs to be updated before this can take place.

With regards to the Demo, we don’t necessarily need to rely on the docker images.  
You can follow the different related issues on Github to know where it is heading:

> <https://github.com/libretime/libretime/issues/1497>
>
> In order to have direct feedback of the current state of the code living in mast…er, I propose that we continuously build and deploy Libretime on a demo / testing deployment.
> 
> In my opinion this would require the project to have:
> \- container images for each app, so we build and the host simply auto update the images,
> \- sample data that can be inserted in the stack if a big failure occur, and we need to reset the stack,
> \- a shared dashboard where we can graph, explore the logs and metrics of that stack (I am thinking about grafana + loki + prometheus).
> 
> The question is who can host this ? Do we want to put money in a Linode/Digital Ocean/Hetzner/\[insert any other provider...\] to run this ?

> <https://github.com/libretime/organization/issues/8>
>
> \*\*Describe the proposal\*\*
> 
> Context https://github.com/libretime/libretime/issu…es/1497 
> 
> I propose to provide a testing infrastructure for the project and a demo to the public. I will try not to elaborate too much on the technical details but they involve how much money goes into it.
> 
> In terms of testing I think we only need 2 different distributions, each with the latest system of both Debian and Ubuntu (Bullseye and Focal), this means 2 different devices to pay for. Once we fully support containers, we should only need a single device running different distributions inside containers.
> 
> In terms of a demo, having a second Libretime stack installed next to the testing installation should be good enough. I consider the demo a lower priority compared to the testing infrastructure.
> 
> Management of these devices should be handled use infrastructure as code, so changes can be reviewed and approved by maintainers. Transmission to future maintainers should also be easier.
> 
> These devices could be used for other purposes.
> 
> \*\*Cost breakdown\*\*
> 
> This depends on the platform offering these servers:
> 
> \- \[Hetzner\](https://www.hetzner.com/cloud?country=ot)
> 2 x CX11 3,49€ (no VAT) / month
> 
> \- \[Add providers if you have a better solution\]
> 
> I don't know how far we need to pan for the funding of this, if we plan yearly or every 6 month.
> 
> \*\*Involvement\*\*
> 
> I help to maintain LibreTime and expect that continuous testing of the deployed services will make the development cycle faster. The demo is intended to bring the project to the public in order to reach more people and grow the community.

---

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [April 14, 2022, 7:45pm UTC](https://discourse.libretime.org/t/libretime-demo-site/82/41 "2022-04-14T19:45:13Z")

</div>

Does that explain the technical reason we couldn’t see if a company like Digitial Ocean would sponsor hosting resources (like they’ve done for [projects like AzuraCast](https://discourse.libretime.org/t/libretime-demo-site/82/20))?

[Previous page](https://discourse.libretime.org/t/libretime-demo-site/82.md?page=1)

[Next page](https://discourse.libretime.org/t/libretime-demo-site/82.md?page=3)