- [Docker](https://www.docker.com/get-started) or [Node.js](https://nodejs.org/en/download) ( > v18.x )
- [Docker](https://www.docker.com/get-started) or [Node.js](https://nodejs.org/en/download) ( > v18.x )
## Quick try
## Quick try
### Docker
### Docker
@ -107,7 +107,7 @@ docker-compose up -d
</TabItem>
</TabItem>
</Tabs>
</Tabs>
:::tip
:::tip
To persist data in docker you can mount volume at `/usr/app/data/` since 0.10.6. In older version mount at `/usr/src/app`.
To persist data in docker you can mount volume at `/usr/app/data/` since 0.10.6. In older version mount at `/usr/src/app`.
If you plan to input some special characters, you may need to change the character set and collation yourself when creating the database. Please check out the examples for [MySQL Docker Compose](https://github.com/nocodb/nocodb/issues/1313#issuecomment-1046625974).
If you plan to input some special characters, you may need to change the character set and collation yourself when creating the database. Please check out the examples for [MySQL Docker Compose](https://github.com/nocodb/nocodb/issues/1313#issuecomment-1046625974).
:::
:::
@ -121,7 +121,7 @@ You can run below command if you need an interactive configuration.
Every time you create it, it will add a new version. If it is not existing, the version will be 1.
Every time you create it, it will add a new version. If it is not existing, the version will be 1.
```bash
```bash
aws ecs register-task-definition \
aws ecs register-task-definition \
@ -239,7 +239,7 @@ npm start
This json file defines the container specification. You can define secrets such as NC_DB and environment variables here.
This json file defines the container specification. You can define secrets such as NC_DB and environment variables here.
:::
:::
Here's the sample Task Definition
Here's the sample Task Definition
```json
```json
{
{
@ -281,7 +281,7 @@ This json file defines the container specification. You can define secrets such
}
}
```
```
#### Create ECS Service
#### Create ECS Service
```bash
```bash
aws ecs create-service \
aws ecs create-service \
@ -298,7 +298,7 @@ This json file defines the container specification. You can define secrets such
:::tip
:::tip
If your service fails to start, you may check the logs in ECS console or in Cloudwatch. Generally it fails due to the connection between ECS container and NC_DB. Make sure the security groups have the correct inbound and outbound rules.
If your service fails to start, you may check the logs in ECS console or in Cloudwatch. Generally it fails due to the connection between ECS container and NC_DB. Make sure the security groups have the correct inbound and outbound rules.
:::
:::
@ -309,9 +309,9 @@ If your service fails to start, you may check the logs in ECS console or in Clou
<details>
<details>
<summary>Click to Expand</summary>
<summary>Click to Expand</summary>
#### Pull NocoDB Image on Cloud Shell
#### Pull NocoDB Image on Cloud Shell
Since Cloud Run only supports images from Google Container Registry (GCR) or Artifact Registry, we need to pull NocoDB image, tag it and push it in GCP using Cloud Shell. Here are some sample commands which you can execute in Cloud Shell.
Since Cloud Run only supports images from Google Container Registry (GCR) or Artifact Registry, we need to pull NocoDB image, tag it and push it in GCP using Cloud Shell. Here are some sample commands which you can execute in Cloud Shell.
```bash
```bash
# pull latest NocoDB image
# pull latest NocoDB image
@ -324,7 +324,7 @@ If your service fails to start, you may check the logs in ECS console or in Clou