[meta issue] code quality improvement plan

[ofey404]

This is a meta issue, tracking the progress of a multi-step change.

Purpose

We have something minimum working now, to verify the idea.

But without basic quality assurance, the codebase would decay, and developer productivity would drop to an unacceptable status. And refactor would be impossible.

So this issue proposes the integration of basic quality control methods into this repo.

Idea: incremental is the key

This must be an incremental process.

Incremental means:

The key to incremental‐ism is not just splitting up the work into a series of small steps but splitting up the work in such a way that every step brings its own value—even if the later steps never happen.

--"Terraform: Up & Running" by Yevgeniy Brikman

It's not about spending 7 days to refactor the whole codebase, pause the development of all new features, and pray for everything would work fine.

I'll do it bit by bit, every step is self-contained.

Roadmap

For those working parts, I should ensure they are still working after each step.

• [devops] write a test for endpoint /imagen #3
  • /generate is the most used endpoint now.
  • This test can act as a startpoint of all possible following refactors.
• config file.
• backend structure - best practice.
• CI.
• minimum memory stream. [feature] Generative Interaction of Pokemons #1

[ofey404]

FastAPI file structure best practice

• zhanymkanov/fastapi-best-practices
• Bigger Applications - Multiple Files