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

Renaming repository and updating purpose #36

Open
immortal-tofu opened this issue Nov 4, 2024 · 4 comments
Open

Renaming repository and updating purpose #36

immortal-tofu opened this issue Nov 4, 2024 · 4 comments

Comments

@immortal-tofu
Copy link

  • docker compose for native and coprocessor
  • "default" terraform useful for partners
  • Testing suite to help partners (and us) test that everything works end to end
  • Benchmark tools

Possible name could be fhevm-devops

@0xawaz
Copy link

0xawaz commented Nov 4, 2024

the renaming sounds accurate for me.
I think we need to change the current setup of native/coprocessor mode, should we create a new repo, or find a way to implement it main?

@immortal-tofu
Copy link
Author

I'd prefer have a monorepo for everything mentioned above. It would simplify things.

@0xawaz
Copy link

0xawaz commented Nov 4, 2024

So, we will have to include some kind of switch native/coprocessor mode, because main-coprocessor this might cause breaking changes though, to what extent we are comfortable to introduce them?

@leventdem
Copy link
Collaborator

I agree we should rename it, not sure about devops, why not using fhevm-demo ?

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

No branches or pull requests

3 participants