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

refactor: use common DATA_DIRECTORY env var #10268

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

alexghr
Copy link
Contributor

@alexghr alexghr commented Nov 28, 2024

This PR removes the custom env var to specify data directories for the prover and broker in favour of using the common config we already have

I have created a separate issue to cleanup the config for the broker/agent/prover/prover-client #10269

@alexghr alexghr linked an issue Nov 28, 2024 that may be closed by this pull request
Base automatically changed from ag/proving-changes to master November 28, 2024 13:19
@alexghr alexghr enabled auto-merge (squash) November 28, 2024 13:22
proverBrokerDataDirectory: {
env: 'PROVER_BROKER_DATA_DIRECTORY',
description: 'If starting a prover broker locally, the directory to store broker data',
dataDirectory: {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can ...dataConfigMappings be done instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not without adding a dependency on @aztec/kv-store to @aztec/circuit-types

Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm, it feels wrong then that circuit-types contains configuration types for apps. It seems much too low level for that.

proverAgentCount: {
env: 'PROVER_AGENT_COUNT',
description: 'The number of prover agents to start',
...numberConfigHelper(1),
},
dataDirectory: {
Copy link
Collaborator

Choose a reason for hiding this comment

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

And here

/** Where to store temporary data */
cacheDir?: string;

dataDirectory?: string;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you do export type ProverConfig = ActualProverConfig & { blah } & DataStoreConfig;?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same problem, we'd have to depend on kv-store in circuit-types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Prover] use common DATA_DIRECTORY config
2 participants