Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docker-compose so it can run properly now #2966

Conversation

namnx228
Copy link

Background

Update the docker-compose it can run properly with Redis support.

Changes

  • Update the docker-compose file to reflect the new mounting point
  • Update doc file to describe how to run docker-compose with redis.

Documentation

The change is small and can be understood by this pull request description.

Test Plan

Follow the step I described in the doc file change.

PR Quality Checklist

  • My pull request is atomic and focuses on a single change.
  • I have thoroughly tested my changes with multiple different prompts.
  • I have considered potential risks and mitigations for my changes.
  • I have documented my changes clearly and comprehensively.
  • I have not snuck in any "extra" small tweaks changes

@namnx228
Copy link
Author

@Torantulino @BillSchumacher Please take a look

@ntindle ntindle added the docker label Apr 23, 2023
@ppetermann
Copy link
Contributor

partially duplicates #2923

profiles: ["exclude-from-up"]

redis:
image: "redis/redis-stack-server:latest"
image: redis/redis-stack-server:latest
container_name: redis-stack-server
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't name containers if not necessary, naming containers can create conflicts with other containers of the same name

#### Using docker-compose
In addition to the above changes in environment variables, change this one:
```sh
REDIS_HOST=redis-stack-server
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that would explain why you are naming the container. use the service name instead (redis), and docker will take care of the rest

@codecov
Copy link

codecov bot commented Apr 23, 2023

Codecov Report

Patch coverage has no change and project coverage change: -6.25 ⚠️

Comparison is base (986bdaa) 43.88% compared to head (2270f6c) 37.64%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2966      +/-   ##
==========================================
- Coverage   43.88%   37.64%   -6.25%     
==========================================
  Files          60       60              
  Lines        2855     2856       +1     
  Branches      472      472              
==========================================
- Hits         1253     1075     -178     
- Misses       1498     1719     +221     
+ Partials      104       62      -42     

see 17 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@github-actions github-actions bot added the conflicts Automatically applied to PRs with merge conflicts label Apr 24, 2023
@github-actions
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

@Pwuts
Copy link
Member

Pwuts commented Apr 26, 2023

Closing as deprecated; this was already fixed in #1843

@Pwuts Pwuts closed this Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflicts Automatically applied to PRs with merge conflicts docker size/m
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants