Feat : draft gogs integration (WIP)

[AlexFernandes-MOVAI]

3.1 - GIT server on CE

New service to be installed on Manager / Flow :

• GIT server : gogs
• Single authentication : to be checked
• Allow anonymous access on GIT : to be checked

Launch it :

export APP_PATH=$PWD
/scripts/movai-flow-launch

Configure Gogs : http://localhost:30080/

Database infos : gitdb, user: gitmovai, password: gitmovai

SSH access : localhost:30022

Challenges:

• initial SSH configuration for GitServer, MovaiBackend:

  • validate DAL can access the GIT server using SSH / HTTPS (user, password)

• initial MOVAI repositories creation :

  • populate the server with MOVAI baselines (nodes, flow, cbs, ...)
  • import or fork the necessary repositories
  • create users repositories

  once the process is clear a master git server can then be deployed for whole R&D

• plug backend, spawner, health-node containers to these repositories local clones

  • replace redis-local / redis-master
  • handle git commit / git stash / git checkout .... operations

• packages compilation and generation will be handled by some complementary orchestration (mobros spawnable containers):

  • multiple ros distributions workspaces creation
  • c++ compilation
  • deb pack ===> apt repository
  • docker build ===> docker registry

---

• Make sure you are opening from a topic/feature/bugfix branch
• Ensure that the PR title represents the desired changes
• Ensure that the PR description detail the desired changes
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[guide-bot]

Thanks for opening this Pull Request!
We need you to:

1. Complete the activities.

   Action: Complete Link to relevant pull requests, esp. upstream and downstream changes
   Action: Complete Ensure you have provided tests - that demonstrates feature works or fixes the issue

   If an activity is not applicable, use '~activity description~' to mark it not applicable.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[engdorm]

didn't we want to use git tea?

[AlexFernandes-MOVAI]

didn't we want to use git tea?

@Mograbi told us the 2 tools were similar and a fork of each other.

Here we just want to POC the GIT solution and communication mechanism don't we ?

After we can change the git backend server without impacts ? right ?

[Mograbi]

@AlexFernandes-MOVAI I think this should be open to a seperate branch first and not dev

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication