Standardize to single non-root Dockerfile

[chungyau97]

Description

Standardizes the project to use a single non-root Dockerfile instead of maintaining multiple Dockerfiles.

[gemini-code-assist]

Summary of Changes

Hello @chungyau97, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the security posture of the Docker environment by standardizing the application to run as a non-root user. It involves updating critical file paths within the container and adjusting the application's startup command to align with this more secure configuration, ensuring a consistent and safer deployment strategy.

Highlights

• Non-Root User Standardization: All internal Docker paths for database, secret keys, logs, and blob storage have been updated from /root/.flowise to /home/node/.flowise, ensuring the application runs as a non-root user for enhanced security.
• Application Startup Command Update: The Docker Compose entrypoint has been modified to use pnpm start instead of flowise start, indicating a change in how the application is initiated within the container.
• Docker Image Reference Change: The Docker image in docker-compose.yml has been updated to flowiseaiyau/test:latest, likely for testing purposes by the author.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request standardizes the Docker configuration to use a single non-root user, which is a great improvement for security. The changes in .env.example and docker-compose.yml correctly reflect the new user's home directory. However, the docker-compose.yml file points to a temporary test image. This must be corrected before merging to ensure the correct image is used in deployments.

[gemini-code-assist]

The Docker image is set to a test image (flowiseaiyau/test:latest). This should be changed back to the official image, likely flowiseai/flowise:latest, before this PR is merged to avoid deploying a potentially unstable or incorrect version.

        image: flowiseai/flowise:latest