Clarification on setup scripts, configuration, and intended project structure #1162
Unanswered
Harshad071
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi maintainers 👋
I’ve been exploring the PictoPy codebase while setting up my local environment and had a few clarification questions to better understand the project’s intended architecture and contributor workflow.
1. Configuration approach
I noticed that some configuration values (like backend URLs in the frontend and model paths in backend/sync-microservice) are currently hardcoded or relative-path based.
Is this:
I want to make sure any future contributions align with the project’s direction.
2. sync-microservice setup expectations
The documentation describes running the sync-microservice alongside the backend, but the automated setup script doesn’t seem to prepare its environment yet.
Is the expectation that contributors set this up manually for now?
3. Frontend documentation
The frontend README still looks like the default Tauri + React template.
Is frontend documentation something the project plans to expand later, or is it currently out of scope?
I’m asking mainly to understand what is intentional vs what is still evolving, so I don’t raise issues or PRs that go against the project’s roadmap.
Thanks for the great project, really enjoying reading through the code! 🚀
Beta Was this translation helpful? Give feedback.
All reactions