Open yawaflua opened 5 months ago
Suggest a fix. Maybe distribute frotnend and backend on different branches, or on different repos.I agree, the potential problem is indeed there
Suggest a fix. Maybe distribute frotnend and backend on different branches, or on different repos.I agree, the potential problem is indeed there
Distribute front and back to different branches very bad practice, doesnt do that plz, use another git repo
Suggest a fix. Maybe distribute frotnend and backend on different branches, or on different repos.I agree, the potential problem is indeed there
Distribute front and back to different branches very bad practice, doesnt do that plz, use another git repo
This solution will be very labor-intensive, because the frontend and backend are very dependent on each other. You will have to somehow synchronize these two repos, set new parameters, etc. Moreover, if the user wants to install an entire project, he will have to clone two repositories at once. Perhaps this is a really good idea, but in a project that was done by two people to defend a project in college, it does not make sense. I'll probably take this into account in future projects.
What the heck? Why are your backend and frontend located in the same project, even in different folders? Of course you haven't used Docker, but that's a lot of nonsense!
Backend and frontend in one project:
Please, fix it