[ftr] Separate frontend and backend

[daniel-jettka]

Is your feature request related to a problem? Please describe.
Edirom's JavaScript-based frontend and XQuery-based backend are stored in the same repository.
For modularization purposes they can and should go into separate repositories.

Describe the solution you'd like
Have in total four repos: backend, API, frontend

(a) Docker repository

• use this repo to provide a Dockerfile and documentation on how to build the complete Edirom
• move other contents to following repos

(b) Frontend repository

• split from this and move to https://github.com/Edirom/Edirom-Online-Frontend
• use git filter-branch ... to split and preserve history

(c) Backend repository

• split from this and move to https://github.com/Edirom/Edirom-Online-Backend
• use git filter-branch ... to split and preserve history

(d) API repository

• new repo https://github.com/Edirom/Edirom-Online-API
• contains OpenAPI Swagger definition of API

Describe alternatives you've considered
Keep as is.

Additional context
./.

[krHERO]

Branches to frontend and backend

we moved branches from Edirom-Online to dedicated branches in the following two repositories

Edirom-Online-Backend

• ftr/144-prefs-namespace --> still in edirom-online as branch
• ftr/audio-player-web-component this branch contained frontend and backend stuff and backend content was split to this place, see #99 --> still in edirom-online as branch
• fix/help-internal-links see #24 --> still in edirom-online as branch
• https://github.com/Edirom/Edirom-Online/tree/ftr/306-create-central-meixqm-module @riedde see #306 --> behind, but no conflicts with update (only one separate new file in this branch)
• https://github.com/Edirom/Edirom-Online/tree/ftr/metadata-view @bwbohl PR423 [EDIT] @bwbohl updated the PR and branch and associated handle mei:annot in running text, e.g. meiHead Edirom-Online-Backend#25 as sub-issue to metadataView: reactivate  Edirom-Online-Backend#27

Edirom-Online-Frontend

• ftr/audio-player-web-component this branch contained frontend and backend stuff and frontend content was split to this place, see #99
• feature/ExtJS-5.1.1 see #379 --> still in edirom-online as branch
• https://github.com/Edirom/Edirom-Online/tree/fix/annot-tool-tip-layout @riedde see PR354 comment: "Maybe opening an Issue and closing this PR draft?"
• https://github.com/Edirom/Edirom-Online/tree/fix/stable-sencha-cmd @bwbohl restored the branch to migrate it
• https://github.com/Edirom/Edirom-Online/tree/ftr/improve-build-feedback @bwbohl see Ftr/improve build feedback #552

TODO: updates to branches

We encountered some branches that were really a lot behind, so we did not moved them today.
@Edirom/edirom-online-developer please update to develop-branch (or deal with it in an appropriate way), so they can also be moved to the frontend or backend repositories if they are still relevant.

• https://github.com/Edirom/Edirom-Online/tree/ftr/measure-label-handling @riedde PR302
• https://github.com/Edirom/Edirom-Online/tree/ftr/teitext-transfromation-parameters @bwbohl deleted branch
• https://github.com/Edirom/Edirom-Online/tree/feature/extJS-7 --> @bwbohl @DennisFriedl @hizclick @daniel-jettka see #375 but we want to upgrade to v5 --> deleted

general TODO

• please provide issue-numbers to your branches --> this was added to CONTRIBUTING.md meanwhile with a commit
• delete https://github.com/Edirom/Edirom-Online/tree/develop/validation because deprecated --> no content anymore in the branch, that will be the content for the future Edirom-Online main repo

[bwbohl]

I was hoping to migrate the fix/stable-sencha-cmd branch to the Frontend repo but still don’t see what and how I should achieve this by using git filter-branch and how I can migrate a branch… any help would be appreciated.

I was just wondering if I could add a new remote to my local clone, create a branch of the same name, and cherry-pick the commits onto it. Would that be an alternative?

[bwbohl]

I migrated ftr/improve-build-feedback to the frontend repository, I hope it’s the way you want it. Just for documentation and future use, here’s what I did:

• create clean clone of source-repo
• switch to the branch you want to migrate
• Clean history to respective paths, e.g.:

  git filter-repo --path build.sh

• add new repo as remote

  git remote add new https://github.com/Edirom/Edirom-Online-Frontend.git

• push branch to new remote

  git push -u new

• clone new repository
• checkout branch created above
• rebase on develop and fix rebase conflicts
• force-push the branch to overwrite it’s now merged history

  git push --force

• create pull-request

[daniel-jettka]

I migrated ftr/improve-build-feedback to the frontend repository, I hope it’s the way you want it. Just for documentation and future use, here’s what I did:

Thanks @bwbohl Yes, since it only concerns the one file, this looks good.

[daniel-jettka]

Hi @bwbohl Due to the changed structure of the https://github.com/Edirom/Edirom-Online-Backend (no add directory anymore) and the complexity of the branch https://github.com/Edirom/Edirom-Online/tree/ftr/metadata-view, after trying different other strategies, I created a branch https://github.com/Edirom/Edirom-Online-Backend/tree/ftr/metadata-view and checked out the changes and committed those.

Is this okay for you? It summarizes the 68 original commits into 1 commit.

[bwbohl]

Great thanks! Yes, it’s ok for me to squash it. Nevertheless, I still spotted some code indented wrong there, and I will fix it.

Did you also transfer the corresponding issue(s)?
Do you want to merge this before mei:annot elements are being processed properly?

[daniel-jettka]

Did you also transfer the corresponding issue(s)?

Corresponding issue: Edirom/Edirom-Online-Backend#27
Corresponding PR: Edirom/Edirom-Online-Backend#28

Do you want to merge this before mei:annot elements are being processed properly?

No, I have to leave this to you because I did not have a look into it :-)

[daniel-jettka]

Notes on moving a backend branch to the backend repo:

git clone https://github.com/Edirom/Edirom-Online.git Edirom-Online-SEP-backend/
cd Edirom-Online-SEP-backend/
python3 ../../newren/git-filter-repo --path add/ --path testing/ --path build.xml --path build.sh --path build.bat 
git remote add backend https://github.com/Edirom/Edirom-Online-Backend.git 
git checkout ftr/measure-label-handling
git push -f backend ftr/measure-label-handling
cd ../Edirom-Online-Backend/
git fetch --all
git checkout ftr/measure-label-handling
git pull
git merge develop 

[daniel-jettka]

Backend release:
https://github.com/Edirom/Edirom-Online-Backend/tree/v1.0.0
https://doi.org/10.5281/zenodo.14998458

[daniel-jettka]

Frontend releases:
https://github.com/Edirom/Edirom-Online-Frontend/releases
https://doi.org/10.5281/zenodo.15013103