mirror of
https://github.com/LukeHagar/documentation-coolify.git
synced 2025-12-09 12:27:48 +00:00
chore: Update database image paths in knowledge base
This commit is contained in:
66
src/content/docs/databases/index.mdx
Normal file
66
src/content/docs/databases/index.mdx
Normal file
@@ -0,0 +1,66 @@
|
||||
---
|
||||
title: Introduction
|
||||
head:
|
||||
- tag: "meta"
|
||||
attrs:
|
||||
property: "og:title"
|
||||
content: "Databases you can host with Coolify"
|
||||
description: "An overview of the databases supported by Coolify and their characteristics."
|
||||
---
|
||||
|
||||
import { Aside } from '@astrojs/starlight/components';
|
||||
|
||||
Coolify supports a variety of databases to suit different application needs. Even if you don't see your favorite database here, you can still host it with Coolify, using Docker.
|
||||
|
||||
Coolify offers one-click setup for the following databases:
|
||||
|
||||
- [PostgreSQL](/docs/knowledge-base/databases/postgresql)
|
||||
- [Redis](/docs/knowledge-base/databases/redis)
|
||||
- [DragonFly](/docs/knowledge-base/databases/dragonfly)
|
||||
- [KeyDB](/docs/knowledge-base/databases/keydb)
|
||||
- [Clickhouse](/docs/knowledge-base/databases/clickhouse)
|
||||
- [MongoDB](/docs/knowledge-base/databases/mongodb)
|
||||
- [MySQL](/docs/knowledge-base/databases/mysql)
|
||||
- [MariaDB](/docs/knowledge-base/databases/mariadb)
|
||||
|
||||
Each database has its own strengths and use cases. Click on a database to learn more about it.
|
||||
|
||||
# Deploy a database
|
||||
|
||||
When selecting a New Resource, you can select a database from the list.
|
||||
|
||||
|
||||

|
||||
|
||||
You can configure a database with a simple click. Coolify supports the following databases:
|
||||
|
||||
- PostgreSQL
|
||||
- MySQL
|
||||
- MariaDB
|
||||
- MongoDB
|
||||
- Redis
|
||||
- DragonFly
|
||||
- KeyDB
|
||||
- Clickhouse
|
||||
|
||||
## Ports Mapping vs Public Port
|
||||
|
||||
### Ports Mapping
|
||||
|
||||
Ports mapping is using the Docker [port mapping](https://docs.docker.com/network/#published-ports) feature. It is used to map the container port to the host port. For example, if you set the port mapping to `8080:80`, the container port `80` will be mapped to the host port `8080`.
|
||||
|
||||
### Public Port
|
||||
|
||||
Public port is used to expose the container port to the internet, by starting an Nginx TCP proxy.
|
||||
|
||||
### Which one should I use?
|
||||
|
||||
- Port mappings makes the connection/port permanent (you need to restart your database to change it).
|
||||
- The public port makes the connection/port dynamic (you can change it without restarting the database, Coolify will restart the Nginx TCP proxy for you).
|
||||
|
||||
## Access database during builds
|
||||
|
||||
If you are using `Nixpacks` build pack, you have two ways to access your database during builds:
|
||||
|
||||
1. Database & your application are `in the same network`: You can reach it using the `internal URL` provided by Coolify.
|
||||
2. Database & your application `are not in the same network`: You need to set your database to be `Accessible over the internet` and use the `public URL` provided by Coolify.
|
||||
Reference in New Issue
Block a user