Getting CouchDB running on Dokploy #1074
-
|
Hello! I would like to get CouchDB working on Dokploy(and potentially submitting a template PR if the maintainers are ok with that), but I don't know where to start. Can someone point me in the right direction? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Following this since I'm also wondering how to host an alternative database other than MySQL, MariaDB, PostgreSQL. (e.g. SQLite). Actually now that I think about it, maybe you can also check how Templates are added. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we are open to accept any PR, for many people who don't know, it is feasible and advisable to separate a docker compose and structure it in applications. services:
app:
image: dokploy/dokploy:latest
ports:
- 3000
backend:
image: dokploy/backend:latest
ports:
- 3000this easily becomes: 2 Applications 1 for the app and the other for the backend, what is the difference? In docker compose we can handle many applications in a single file, while applications are treated as a single entity and not multiple, so we need to separate them. you can use this template for cockroachdb version: '3.8'
services:
cockroach:
image: cockroachdb/cockroach:v23.2.0
command: start-single-node --insecure
ports:
- "26257"
- "8080"
volumes:
- cockroach-data:/cockroach/cockroach-data
environment:
COCKROACH_MAX_OPEN_FILES: 1024
restart: unless-stopped
volumes:
cockroach-data:
driver: localIn Domains when you deploy you can access to the dashboard Regarding how to contribute you can read here: https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#templates |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your answer! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
The PR is merged, you can now use the couchdb template! |
Beta Was this translation helpful? Give feedback.
Yes, we are open to accept any PR, for many people who don't know, it is feasible and advisable to separate a docker compose and structure it in applications.
this easily becomes:
2 Applications
1 for the app and the other for the backend, what is the difference? In docker compose we can handle many applications in a single file, while applications are treated as a single entity and not multiple, so we need to separate them.
you can use this template for cockroachdb