mirror/coolify-docs
1
0
Fork 0
mirror of https://github.com/coollabsio/coolify-docs.git synced 2026-06-19 07:35:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(content): fix inline codes showing escaped Vue braces

Browse Source
This commit is contained in:
ShadowArcanist
2026-05-11 22:09:03 +05:30
parent f8d36aa12b
commit 297d083d1c
4 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/docs/applications/ci-cd/github/preview-deploy.mdx
+2 -2
View File
@@ -18,8 +18,8 @@ These preview deployments are automatically deleted once the associated pull req
<ZoomImage src="/docs/images/applications/ci-cd/github/preview-deploy/4.webp" />
- **Preview URL Template:** Each preview deployment gets its own unique URL based on this template.
- Use <code v-pre>&#123;&#123;random&#125;&#125;</code> to generate a random subdomain each time a PR is deployed.
- Use <code v-pre>&#123;&#123;pr_id&#125;&#125;</code> to use the pull request ID as the subdomain.
- Use `{{random}}` to generate a random subdomain each time a PR is deployed.
- Use `{{pr_id}}` to use the pull request ID as the subdomain.
<Callout type="warn" title="IMPORTANT">
content/docs/applications/index.mdx
+2 -2
View File
@@ -141,7 +141,7 @@ Preview deployments are a great way to test your application before merging it i
#### URL Template
You can setup your preview URL with a custom template. Default is <span v-pre>`&#123;&#123;pr_id&#125;&#125;.&#123;&#123;domain&#125;&#125;`</span>.
You can setup your preview URL with a custom template. Default is <span v-pre>`{{pr_id}};.{{domain}};`</span>.
This means that if you open a Pull Request with the ID `123`, and you resource domain is `example.com` the preview URL will be `123.example.com`.
@@ -149,7 +149,7 @@ This means that if you open a Pull Request with the ID `123`, and you resource d
<Callout type="success" title="TIP">
If you have several domains for your resource, the first will be used as the&#123;" "&#125;
<span v-pre>`&#123;&#123; domain &#125;&#125;`</span> part.
<span v-pre>`{{ domain }};`</span> part.
</Callout>
content/docs/knowledge-base/docker/compose.mdx
+1 -1
View File
@@ -154,7 +154,7 @@ If in developer view, you can enter it like so;
SOME_VARIABLE_IN_COOLIFY_UI={{environment.SOME_SHARED_VARIABLE}}
```
Or in the normal view, the Name is what's referenced in the Docker Compose file `SOME_VARIABLE_IN_COOLIFY_UI` with the Value being the referenced environment variable `&#123;&#123;environment.SOME_SHARED_VARIABLE&#125;&#125;` as seen below. Once saved if correct, you'll see there's a third text box, if you reveal this, you should be able to see the true value, in this case `SOME_VALUE`.
Or in the normal view, the Name is what's referenced in the Docker Compose file `SOME_VARIABLE_IN_COOLIFY_UI` with the Value being the referenced environment variable `{{environment.SOME_SHARED_VARIABLE}}` as seen below. Once saved if correct, you'll see there's a third text box, if you reveal this, you should be able to see the true value, in this case `SOME_VALUE`.
</Callout>
content/docs/knowledge-base/environment-variables.mdx
+3 -3
View File
@@ -162,15 +162,15 @@ Then you can use these variables anywhere. For example: You defined `NODE_ENV` t
### Team Based
You can set them on the `Team` page and use it with <code v-pre>&#123;&#123;team.NODE_ENV&#125;&#125;</code>. Do not replace "team" with your actual team name.
You can set them on the `Team` page and use it with `{{team.NODE_ENV}}`. Do not replace "team" with your actual team name.
### Project Based
You can set them on the `Projects` page, under the gear icon and use it with <code v-pre>&#123;&#123;project.NODE_ENV&#125;&#125;</code>. Do not replace "project" with your actual project name.
You can set them on the `Projects` page, under the gear icon and use it with `{{project.NODE_ENV}}`. Do not replace "project" with your actual project name.
### Environment Based
You can set them on the `Environments` page (select a `Project`), under the gear icon and use it with <code v-pre>&#123;&#123;environment.NODE_ENV&#125;&#125;</code> Do not replace "environment" with your actual environment name.
You can set them on the `Environments` page (select a `Project`), under the gear icon and use it with `{{environment.NODE_ENV}}` Do not replace "environment" with your actual environment name.
### Using Environment and Shared Variables in Docker Compose