Use Git submodules for P2P apps in /pages/p2p/

[akhileshthite]

Currently, our P2P apps are maintained locally in the ./src/pages/p2p/ directory. To simplify maintenance and keep each app independent, I propose we switch to using Git submodules for these apps. This change would allow us to update and manage each P2P app in its own repository and other forks, making it easier to track changes, pull updates, and collaborate.

Proposed changes:

• Move the current P2P apps in /pages/p2p/ to their respective repositories (e.g., chat.p2plabs.xyz, etc.).
• Add these repositories as submodules in the main project.
• Update our build process to ensure that submodules are initialized and updated when installing dependencies.

"scripts": {
  "postinstall": "git submodule update --init --recursive"
}

This command will ensure that whenever someone runs npm install, all submodules are automatically initialized and updated.

[RangerMauve]

I think that's a good idea. I used a similar approach in the past for extensions before I switched to downloading them from releases.

[RangerMauve]

Also for Agregore I've been publishing apps on the website then linking to them from the welcome page.
I was thinking it could be good to preload the website content statically in the install binary to have available offline out of the box.

...

Submodules seem easier tho! :P

[akhileshthite]

Also for Agregore I've been publishing apps on the website then linking to them from the welcome page. I was thinking it could be good to preload the website content statically in the install binary to have available offline out of the box.

...

Submodules seem easier tho! :P

Yep!

[Ayush-Vish]

Hi @akhileshthite I want to work on this issue.