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

(WIP) spin up audiusd container without audius-docker-compose #10441

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

phelpsdb
Copy link
Contributor

Description

Drop the complex configuration that audius-docker-compose requires and just run a self-contained audiusd container.

How Has This Been Tested?

WIP

Copy link

changeset-bot bot commented Nov 14, 2024

⚠️ No Changeset found

Latest commit: 43cb00d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@phelpsdb phelpsdb force-pushed the phelpsdb-wrapperless-audiusctl branch from 48c154b to 7de4845 Compare November 14, 2024 10:36
Copy link

gitguardian bot commented Nov 14, 2024

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
14086629 Triggered Generic Password 4b7f416 cmd/audiusd/entrypoint.sh View secret
11648680 Triggered Generic High Entropy Secret 4b7f416 dev-tools/templates/devnet.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@endline endline self-requested a review November 14, 2024 17:41
@phelpsdb phelpsdb force-pushed the phelpsdb-wrapperless-audiusctl branch from 7de4845 to 4d62614 Compare November 15, 2024 19:35
@endline endline force-pushed the phelpsdb-wrapperless-audiusctl branch from 32583b9 to f10b323 Compare December 6, 2024 16:57
@endline endline force-pushed the phelpsdb-wrapperless-audiusctl branch from 0e80dfc to 43cb00d Compare December 6, 2024 18:22
@endline endline mentioned this pull request Dec 6, 2024
3 tasks
@endline endline removed their request for review January 3, 2025 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants