Skip to content

Add Easypanel deployment option - #561

Closed
Ahson-Shaikh wants to merge 1 commit into
Webreaper:masterfrom
Ahson-Shaikh:add-easypanel-deploy-docs
Closed

Ahson-Shaikh wants to merge 1 commit into
Webreaper:masterfrom
Ahson-Shaikh:add-easypanel-deploy-docs

Conversation

@Ahson-Shaikh

Copy link
Copy Markdown

Hi — this is Ahson Shaikh, DevOps Engineer at Easypanel. Easypanel is a self-hosted Docker deployment platform, and Damselfly has a one-click deployment template there: https://easypanel.io/templates/damselfly

Adds a short Easypanel subsection to docs/Installation.md, with the official deploy badge and the three persistent volumes (config/thumbs/pictures) the template sets up.

@Webreaper

Copy link
Copy Markdown
Owner

Seriously, what is it with you people? I just had a similar request from Hostinger last week.

@Ahson-Shaikh I'm not going to publicise your platform in my app's documentation. The app is already trivially deployed via Docker - nobody needs Easypanel, and it's just a way of monetizing other people's free work.

I don't want people deploying Damselfly using EasyPanel - that's just more complexity for me to support. I don't give permission for you to publicise Damselfly in this way, so please remove the template from the Easypanel website.

I will not be merging this PR.

@Ahson-Shaikh

Copy link
Copy Markdown
Author

Hi @Webreaper, understood on the docs PR, I'll close it, that's your call.

I do want to push back gently on the framing though: we're not a hosting provider marketing to redirect your users to a paid service. Easypanel is self-hosted software people run on their own servers, and templates just help them deploy tools they've already chosen to self-host. We're not selling Damselfly or taking anything from your project. Support for deployment issues stays on us; only tool-specific bugs would ever come back to you, same as any Docker Compose setup someone assembles themselves.

On removing the template: since it's users self-hosting Easypanel on their own infrastructure rather than us hosting anything, I don't think it requires takedown, but I'll leave that to you to clarify if you feel differently.

@Webreaper

Copy link
Copy Markdown
Owner

The problem is that I have to support Damselfly, in my own time, for free. If you push a template for it (about which I know nothing, and which is presumably just some sort of abstraction over the docker-compose I already provide) then that's more work for me - and I don't get any revenue for Damselfly (and have a day job). It's fine for you to say "support for deployment issues stays on us" but that's not the reality.

Docker is trivial to deploy, so I'm really not sure why somebody would need EasyPanel - if they're technical enough to use it, they're technical enough to copy/paste a docker config and run docker-compose. If they're not, well, they probably shouldn't be self-hosting - particularly an app like Damselfly which isn't hardened security-wise to a level where it should be exposed directly to the internet, with personal photos etc.

Plus, you putting it on EasyPanel encourages companies like Hostinger, who were basically selling hosted instances of Damselfly - which means money for them, but more support overhead for me. So whilst you might not be selling it, you're making it easier for others to do so and monetise the product without my consent.

I can't prevent you from posting a template, as it's a free internet and you can do what you like. But I'd rather you didn't. What I certainly don't want to do is advertise EasyPanel in my docs as there seems to be no upside for me with doing that, but plelnty of downside.

@Webreaper Webreaper closed this Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants