fix(service): add usesend configuration file and Remove unused unsend SVG

[yipfram]

Changes

• Unsend rebranded to Usesend
• Pinned image version
• changed logo and deleting old one
• Set github creds as mandatory

[ShadowArcanist]

Hey, there is already an PR (#6606) for this exact same change and it got everything working but need minor changes.

We will wait some more time for that PR author to implement the requested change, if they didn't respond then we can consider this PR.

[yipfram]

Hey, there is already an PR (#6606) for this exact same change and it got everything working but need minor changes.

We will wait some more time for that PR author to implement the requested change, if they didn't respond then we can consider this PR.

Sorry i did not check... Will do next time !

I updated the docs, adding SMTP documentation also

[yipfram]

? @Cinzya
Why ui ux tag for this PR?

[ShadowArcanist]

? @Cinzya Why ui ux tag for this PR?

She probably thought its a UI related PR after reading the first part of the Title "Remove unused svg" xD

Next time please start the title like fix(service):

[github-actions]

Hi @yipfram! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation

[yipfram]

Fixed title

[yipfram]

BTW, if this PR (#6606) is not changed and we end up using mine, i'll probably change the Cert system, which can make this template click and deploy...

For now you have to make changes in the server proxy and compose file... That's too complicated if we can just attach let'sencrypt... But Idk if this works for everyone (idk how those work...)

[ShadowArcanist]

Hey @yipfram thanks for the PR, for now I am putting this PR on Hold since that other PR author responded + implemented some changes (waiting to implement few more).

The changes on this PR for the usesend.yaml is same as the other PR, so let's wait and see if that PR author addresses my questions + provides a way to test the changes - if they don't then we can merge this one (I may forget this PR so feel free to ping me here or in discord after 2 weeks of this comment)

[yipfram]

Ok, in the meantime I'll check the other cert system and see how this can work

[yipfram]

Could we make this work? @ShadowArcanist

coolify/templates/compose/usesend-with-smtp.yaml

Lines 43 to 54 in c1e8986

	USESEND_API_CERT_PATH: "${TLS_CERT}"
	USESEND_API_KEY_PATH: "${TLS_KEY}"
	ports:
	- "25:25" # Standard SMTP
	- "587:587" # SMTP with STARTTLS
	- "2587:2587" # Alternative SMTP port
	- "465:465" # SMTP over SSL/TLS
	- "2465:2465" # Alternative SMTPS port
	volumes:
	- type: bind
	source: /etc/letsencrypt
	target: /certs

Like Letsencrypt

[ShadowArcanist]

Could we make this work? @ShadowArcanist

coolify/templates/compose/usesend-with-smtp.yaml

Lines 43 to 54 in c1e8986

	USESEND_API_CERT_PATH: "${TLS_CERT}"
	USESEND_API_KEY_PATH: "${TLS_KEY}"
	ports:
	- "25:25" # Standard SMTP
	- "587:587" # SMTP with STARTTLS
	- "2587:2587" # Alternative SMTP port
	- "465:465" # SMTP over SSL/TLS
	- "2465:2465" # Alternative SMTPS port
	volumes:
	- type: bind
	source: /etc/letsencrypt
	target: /certs

Like Letsencrypt

Sadly I have little to no experience with email related stuff so I can't suggest/recommend anything here without testing + understanding stuffs on my own

[yipfram]

Basically it works, the only question is how you collect the certs for the smtp server. I don't think it's related to email stuff

[ShadowArcanist]

Basically it works, the only question is how you collect the certs for the smtp server. I don't think it's related to email stuff

I think you can simply map the /data/coolify/proxy/acme.json (proxy stores the certs there), if the user is using custom certs the you can map /data/coolify/proxy/certs

[yipfram]

Acme can work in the place of cert and key file?
Like as place of the cert path?

Sorry I'm on mobile now, I can't give an example snippet

[ShadowArcanist]

Acme can work in the place of cert and key file? Like as place of the cert path?

Sorry I'm on mobile now, I can't give an example snippet

I just checked it on my dev instance and we can't use acme.json if we need a cert and key files T-T, so we may need something like traefik cert dumper

[yipfram]

Ok, any way we could attach it to this docker compose? (Not the proxy one)

[ShadowArcanist]

Ok, any way we could attach it to this docker compose? (Not the proxy one)

I think it's only needed for the proxy to work, if they are not using the usesend proxy then no need for certs (I maybe wrong here)