You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Request type
Request for enhancement of a component
Functionality
Merging the frontend and backend repositories into a single repository (see a super example of project architecture 😄) could reduce the maintainability and complexity of deployment. It is therefore proposed to integrate the backend repository into the frontend repository and then "delete" the backend repository.
With this adaptation, an automated package could then be generated and deployed so that the network graphics editor could be easily integrated into 3rd party software or deployed as a large Docker package.
The project from Flatland should also be considered for this and also PR #403
Link to design proposal file
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Request type
Request for enhancement of a component
Functionality
Merging the frontend and backend repositories into a single repository (see a super example of project architecture 😄) could reduce the maintainability and complexity of deployment. It is therefore proposed to integrate the backend repository into the frontend repository and then "delete" the backend repository.
With this adaptation, an automated package could then be generated and deployed so that the network graphics editor could be easily integrated into 3rd party software or deployed as a large Docker package.
The project from Flatland should also be considered for this and also PR #403
Link to design proposal file
No response
The text was updated successfully, but these errors were encountered: