feat(deployment): added one click-deployment

[Lasim]

feat: Add one-click cloud deployment support

Enable users to deploy LinkAce instantly on AWS, DigitalOcean, or Render.com using Infrastructure as Code templates. This adds deployment automation while maintaining all configuration options.

Project URL: https://deploystack.io/c/kovah-linkace

Added:

• One-click deploy buttons in README.md for supported cloud providers
• .deploystack/docker-compose.yml - Docker compose configuration
• .deploystack/env - Environment variables template for deployment configuration

The .deploystack directory enables automated template updates when container configs change. See docs at:
https://deploystack.io/docs/deploystack/deploystack-configuration-directory

Auto update to docker config change

To enable automated template updates, install the DeployStack GitHub App: https://github.com/apps/deploystack-repository-sync/installations/select_target

-> DeployStack GitHub Sync App Docs

---

Reference: https://deploystack.io/docs

[Kovah]

To enable automated template updates, install the DeployStack GitHub App: https://github.com/apps/deploystack-repository-sync/installations/select_target

How would that handle different versions of LinkAce? Version 2 is in the pipeline and will slightly change the docker compose stack.

[Lasim]

How would that handle different versions of LinkAce? Version 2 is in the pipeline and will slightly change the docker compose stack.

You're absolutely right - this is a crucial consideration for projects maintaining multiple versions.
I've just created a feature request to address exactly this scenario: deploystackio/feedback#12

Currently, DeployStack only generates templates from your default branch. I'll develop the multi branch support to end of this month.

Once implemented, I'll create a new PR for the LinkAce Version 2 support.

Btw, the issue for DigitalOcean is solved. All three templates are working out of the box.

[Kovah]

That sounds awesome, great work!

In the meantime, am I able to just copy this to the v2 version and do the needed changes there? Or would this mix up both versions once released? The 2.x branch would become the new default branch then.

[Lasim]

In the meantime, I suggest merging this PR for v1, as the IaC templates work as intended.

The files can be copied into v2 without any concerns. I guess the image tag needs to be adjusted in .deploystack/docker-compose.yml. But I would create the PR for v2 myself, as the feature is new, and I would like to support it so that everything runs smoothly :)