Add soketi-app-manager service template 🚀

[rahulhaque]

Submit Checklist (REMOVE THIS SECTION BEFORE SUBMITTING)

• I have selected the next branch as the destination for my PR, not main.
• I have listed all changes in the Changes section.
• I have filled out the Issues section with the issue/discussion link(s) (if applicable).
• I have tested my changes.
• I have considered backwards compatibility.
• I have removed this checklist and any unused sections.

Changes

• Added one click install service template for Soketi App Manager.

Issues

• Fixes service template request for Support for Soketi App Manager📡 #4678

[peaklabs-dev]

I think it would make more sense if the database Postgres and probably Redis and so on where in the compose directly as well and use our magic envs for stuff like passwords and so on so it is truly one click. Can you change that please?

[rahulhaque]

@peaklabs-dev thank you for your thoughtful feedback. I thought of that as well. However soketi server and my app, both can work with mysql and postgresql. My app doesn't require redis but expects soketi to be run with redis. All of these have separate services under Coolify. Considering everything, finally I went with the bare-bone app leaving other choices to users. Thought my repo will contain instructions on how to set things up. Let me know what do you think of it.

Also, do you have any suggestion on how to automate the laravel app key generation if any.

Edit: You can have a look at the original compose file here. The only difference is the comments.

[rahulhaque]

@peaklabs-dev as I was exploring other templates, I found that I can follow the WordPress approach as well. It has two services with and without database. That's one option.

To make my app truly one clickable service, I can include soketi server as well and configure nginx to forward websocket request to soketi exposing only one port and domain. But this will make it less flexible and scalable to users.

In any case I'll wait for your feedback. Thank you.

[peaklabs-dev]

• For the app key you can use ${SERVICE_PASSWORD_APPKEY}
• I think a service without DB makes sense, and one with DB and soketi too, but if possible use internal Docker networking or the Coolify proxy so you don't have to add nginx, which would not be optimal.

[rahulhaque]

I think a service without DB makes sense.

So, will the current pull request need any changes from your perspective? Name change (such as - without-database or auto app key generation), anything? The user will have to drop to terminal anyway to migrate the database.

and one with DB and soketi too

Will need some time and proper testing. It would be nice to offer the bare-bone one in Coolify to see how people prefer to use it. Right now I don't have any idea which approach is the best for general use.

if possible use internal Docker networking or the Coolify proxy so you don't have to add nginx, which would not be optimal.

Sure. Will keep that in mind.

[peaklabs-dev]

Yes, the App Key should be auto generated, and migrations can be automated with a entry point script.

[rahulhaque]

Auto migration of database working fine on first try. However the app key generation by Coolify magic variable not working as expected. Always getting this error - Unsupported cipher or incorrect key length. I got it working by generating a REALBASE64 key and prefixing that with base64: manually. Any suggestion on automating this through Coolify?

Edit: I mean - APP_KEY=base64:${SERVICE_REALBASE64_APPKEY} is not working. Is it a bug? @peaklabs-dev

[rahulhaque]

@peaklabs-dev any update on the APP_KEY generation? I've pushed some changes related to auto migration.