feat: added docker-compose.yml and .env.example for self-hosting

[alt-glitch]

🚀 This description was created by Ellipsis for commit fefebc2

Summary:

This PR adds a docker-compose.yml and .env.example file to the /deploy directory, updates the OPENAI_API_KEY placeholder, and removes the entrypoint line from the worker service in docker-compose.yml to facilitate self-hosting.

Key points:

• Added docker-compose.yml in /deploy directory for self-hosting.
• Added .env.example in /deploy directory as a template for environment variables.
• Updated OPENAI_API_KEY placeholder in .env.example.
• Removed entrypoint line from worker service in docker-compose.yml to facilitate self-hosting.

---

Generated with ❤️ by ellipsis.dev

[ellipsis-dev]

❌ Changes requested.

• Reviewed the entire pull request up to b2b5f31
• Looked at 112 lines of code in 2 files
• Took 42 seconds to review

More info

• Skipped 0 files when reviewing.
• Skipped posting 2 additional comments because they didn't meet confidence threshold of 50%.

1. /deploy/.env.example:1:

• Assessed confidence : 100%
• Grade: 0%
• Comment:
  Sensitive information like API keys and tokens should not be included in the .env.example file. Please replace them with placeholder values.
• Reasoning:
  The .env.example file contains sensitive information like API keys and tokens. This is a security risk. The example file should contain placeholder values instead of real keys or tokens.

2. /deploy/docker-compose.yml:4:

• Assessed confidence : 80%
• Grade: 40%
• Comment:
  It's a good practice to define a network for the services in a docker-compose file. This helps with service discovery and communication between the containers.
• Reasoning:
  The docker-compose.yml file does not specify any network. This could lead to issues with service discovery and communication between the containers. It's a good practice to define a network for the services in a docker-compose file.

Workflow ID: wflow_bZxCOr2vjEjN3WHX

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. We'll respond in a few minutes. Learn more here.

[ellipsis-dev]

The entrypoint for the worker service is set to 'tail -f /dev/null', which means the service will do nothing. Please set a proper entrypoint for the worker service.

[creatorrr]

remove it

[ellipsis-dev]

👍 Looks good to me!

• Performed an incremental review on 568b7ca
• Looked at 13 lines of code in 1 files
• Took 32 seconds to review

More info

• Skipped 0 files when reviewing.
• Skipped posting 1 additional comments because they didn't meet confidence threshold of 50%.

1. deploy/.env.example:13:

• Assessed confidence : 50%
• Comment:
  Please add a newline at the end of the file.
• Reasoning:
  The .env.example file is missing a newline at the end of the file. This is a minor issue but it's a common convention to end files with a newline. This can prevent potential issues with some tools that might not handle files without a newline at the end correctly.

Workflow ID: wflow_qCKKNuZOqvwIlWoy

---

Not what you expected? You can customize the content of the reviews using rules. Learn more here.

[ellipsis-dev]

👍 Looks good to me!

• Performed an incremental review on fefebc2
• Looked at 12 lines of code in 1 files
• Took 1 minute and 7 seconds to review

More info

• Skipped 0 files when reviewing.
• Skipped posting 1 additional comments because they didn't meet confidence threshold of 50%.

1. /deploy/docker-compose.yml:31:

• Assessed confidence : 50%
• Comment:
  The entrypoint for the worker service has been removed. Please ensure that the Dockerfile for the worker image has a default entrypoint defined.
• Reasoning:
  The entrypoint for the worker service has been removed. This could potentially cause issues if the Docker image does not have a default entrypoint defined. I need to check the Dockerfile for the worker image to see if a default entrypoint is defined.

Workflow ID: wflow_hNFam0v9b7WcHMQv

---

Not what you expected? You can customize the content of the reviews using rules. Learn more here.