Separate project for backend

troeger / fuzzed

The Open Reliability Editor (ORE) for dependability modeling and analysis.

https://live.ore-project.org

20 stars 9 forks source link

Open troeger opened 9 years ago

troeger commented 9 years ago

The mixed fronted and backend code in the project is a pain point, both for the build and the Ansible parts.

The backend (daemon) parts should become a separate GitHub project. This includes:

Separation of Ansible playbooks.
Separate Vagrant files. Maybe the frontend does not really need Vagrant support any more.
Splitting up the code base.

Common points, such as the GraphML and the job request format, may go into a third glue repository.

laena commented 9 years ago

Is the Ansible playbook in the frontend then responsible for cloning and building the backends?

What about the files in FuzzEd/static/xsd (obsolete with GraphML, but anyways...)?

troeger commented 9 years ago

The XSD files may belong to the glue repository with common data formats.

The Ansible playbook configures the Vagrant / Dev / production machines, the building is handled in the SCons scripts.