chore: change postgres deploy

[carneiro-cw]

No description provided.

[github-actions]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the PR involves a straightforward change in the Dockerfile and a minor update in the Kubernetes configuration. The Dockerfile changes are typical for setting up a Rust project, and the Kubernetes config change is a simple path update.
🧪 Relevant tests	No
🔍 Possible issues	Possible Performance Issue: The RUN apt update and RUN apt-get install -y libclang-dev cmake commands in the Dockerfile could slow down the build process due to network latency and the size of the packages.
🔒 Security concerns	No

Code feedback:

---

relevant file	docker/Dockerfile.run_with_importer_postgres
suggestion	Consider combining RUN apt update and RUN apt-get install -y libclang-dev cmake into a single RUN command to reduce the number of layers in the Docker image, which can help in reducing the build time and the size of the final image. [important]
relevant line	RUN apt-get install -y libclang-dev cmake

---

relevant file	docker/Dockerfile.run_with_importer_postgres
suggestion	It's recommended to clean up the apt cache by adding rm -rf /var/lib/apt/lists/* at the end of the RUN command where you install packages. This will help reduce the Docker image size, which is crucial for deployment efficiency. [important]
relevant line	RUN apt-get install -y libclang-dev cmake

---

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review which includes several types of feedbacks, such as possible PR issues, security threats and relevant test in the PR. More feedbacks can be added by configuring the tool.

The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.

• When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

• With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

See the review usage page for a comprehensive guide on using this tool.

[github-actions]

PR Code Suggestions

Category	Suggestions
Best practice	Combine Docker RUN commands to reduce image layers. Combine the apt update and apt-get install commands into a single RUN instruction to reduce the number of layers in the Docker image, which can help to optimize the build process and reduce the image size. docker/Dockerfile.run_with_importer_postgres [12-13] -RUN apt update -RUN apt-get install -y libclang-dev cmake +RUN apt update && apt-get install -y libclang-dev cmake
	Use a specific version tag for the Docker base image to ensure consistent builds. Use a more specific base image tag instead of rust:1.75 to ensure consistent builds and prevent unexpected issues if the 1.75 tag is updated. Consider using an image with a full version specification, such as rust:1.75.0-buster. docker/Dockerfile.run_with_importer_postgres [2] -FROM rust:1.75 as builder +FROM rust:1.75.0-buster as builder
	Clear the apt cache to reduce the Docker image size. Clear the apt cache by adding rm -rf /var/lib/apt/lists/* at the end of the RUN command which installs packages. This will help to reduce the Docker image size by removing unnecessary files. docker/Dockerfile.run_with_importer_postgres [12-13] -RUN apt update && apt-get install -y libclang-dev cmake +RUN apt update && apt-get install -y libclang-dev cmake && rm -rf /var/lib/apt/lists/*
	Optimize Docker COPY commands to reduce image size. Ensure that the COPY commands only copy necessary files to avoid bloating the Docker image. Consider using a .dockerignore file to exclude files that are not needed in the build context. docker/Dockerfile.run_with_importer_postgres [5-10] +# Ensure only necessary files are copied COPY src /app/src COPY static /app/static -COPY .sqlx /app/.sqlx -COPY build.rs /app/build.rs COPY Cargo.toml /app/Cargo.toml COPY Cargo.lock /app/Cargo.lock
	Use multi-stage builds to optimize Docker image size. Use multi-stage builds to separate the build environment from the runtime environment more effectively. This can help to minimize the runtime image size by only including the necessary binaries and dependencies. docker/Dockerfile.run_with_importer_postgres [2-18] -FROM rust:1.75 as builder +# Builder stage +FROM rust:1.75.0-buster as builder ... -FROM rust:1.75 as runtime +# Runtime stage with only necessary components +FROM debian:buster-slim as runtime +COPY --from=builder /app/target/release/run-with-importer /app/run-with-importer

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

• When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

• With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

See the improve usage page for a comprehensive guide on using this tool.