feat: add Misskey service template

[maebahesioru]

Changes

Adds a one-click deployment template for Misskey, an open-source decentralized social media platform (Fediverse / ActivityPub). Misskey is widely used especially in Japan and has no existing Coolify template.

The template includes misskey (port 3000), postgres:18-alpine, and redis:7-alpine. The URL and database credentials are passed via environment variables that Misskey natively supports (MISSKEY_URL, DATABASE_USER, DATABASE_PASSWORD, DATABASE_DB). Static connection config (db host/port, redis host/port) is injected via a bind-mounted config.yml.

Note: MISSKEY_URL must be set to your public domain before deploying (e.g. https://misskey.example.com). This value is permanent and cannot be changed after first run.

Issues

• Fixes

Category

• Bug fix
• Improvement
• New feature
• Adding new one click service
• Fixing or updating existing one click service

Preview

AI Assistance

• AI was NOT used to create this PR
• AI was used (please describe below)

If AI was used:

• Tools used: Kiro
• How extensively: Template structure and environment variable handling were verified against Misskey source code (config.ts, compile_config.js) and official docker-compose example.

Testing

Deployed and verified on a live Coolify instance:

• All 3 services (misskey, db, redis) reached Running (healthy) state
• Misskey web UI accessible and functional at the configured domain
• Database migrations ran successfully on first boot
• Verified against Misskey source: MISSKEY_URL, DATABASE_USER, DATABASE_PASSWORD, DATABASE_DB are the only supported env vars; config.yml provides db/redis host and port

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this is not a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.

[ShadowArcanist]

Did you deployed this service on Coolify?

[maebahesioru]

I have not deployed this on a live Coolify instance. The template was verified by reading the official Misskey source code (config.ts, compile_config.js, docker-compose example) to ensure correct environment variables, config file structure, and healthcheck endpoint. I understand this does not substitute for actual deployment testing. If you are able to test it, I would appreciate any feedback.

[ShadowArcanist]

Thanks for the contribution and for clearly explaining your approach — that’s appreciated.

That said, matching the official example doesn’t always guarantee the service will work correctly on Coolify. Because of this, we require contributors to test their templates by actually deploying them on a Coolify instance before submitting a PR.

I also noticed you’ve submitted multiple service templates in a short time. Before opening PRs, please make sure each one has been properly tested.

To test a service template, you don’t need a full local setup. You can simply create a new resource in your Coolify instance, choose “Docker Compose Empty,” paste your compose file, and deploy it.

Once you’ve verified everything works as expected, feel free to update your PRs — we’ll be happy to take another look.

[ShadowArcanist]

Untested PR.

I spent 2hrs testing and fixing it, but didn't got so far.

The issues I managed to fix:

1. App won't deploy because database doesn't start due to the volume mount path issue (volume mount path is changed on postgres-18
2. Missing SERVICE_URL_MISSKEY_3000
3. MISSKEY_URL doesn't need to be set by user manually, we can automate it using SERVICE_URL_MISSKEY
4. Fixing above 3 issues will get you to the login page but it will ask for setup password which we have to on the config file (it could be automated using https://coolify.io/docs/knowledge-base/docker/compose#create-a-file-with-content but Coolify is not expanding the variables (could be a bug) on file content)

Please do not send us untested PRs like these.