Post-Radicle sync at 2025-05-31 08:36:40
This commit is contained in:
Mark Randall Havens
parent
506d7d60ef
commit
1e0d4d0785
3 changed files with 12 additions and 15 deletions
|
|
@ -1 +1 @@
|
|||
a9fb8c8f74f6f44b3a0b63731cfbbc1dac722f68
|
||||
2a9638280207c4d75310a980a2d506e6964297be
|
||||
|
|
|
|||
|
|
@ -37,3 +37,4 @@
|
|||
[2025-05-31 08:16:01] GitLab: https://gitlab.com/mrhavens/git-sigil
|
||||
[2025-05-31 08:16:09] Bitbucket: https://bitbucket.org/thefoldwithin/git-sigil
|
||||
[2025-05-31 08:16:12] Radicle: https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ
|
||||
[2025-05-31 08:36:43] Radicle: https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ
|
||||
|
|
|
|||
|
|
@ -58,25 +58,20 @@ The \`$REPO_NAME\` project employs a multi-repository strategy across four disti
|
|||
|
||||
The following platforms host the \`$REPO_NAME\` repository, each chosen for its unique strengths and contributions to the project's goals.
|
||||
|
||||
### 1. GitHub
|
||||
- **URL**: [$GITHUB_URL]($GITHUB_URL)
|
||||
- **Purpose**: GitHub serves as the primary platform for visibility, collaboration, and community engagement. Its widespread adoption and robust tooling make it ideal for public-facing development, issue tracking, and integration with CI/CD pipelines.
|
||||
- **Value**: Provides a centralized hub for open-source contributions, pull requests, and project management, ensuring broad accessibility and developer familiarity.
|
||||
### 1. Radicle - **URL**: [$RADICLE_URL]($RADICLE_URL) - **Purpose**: Radicle is a decentralized, peer-to-peer git platform that ensures sovereignty and censorship resistance. It hosts the repository in a distributed network, independent of centralized servers.
|
||||
- **Value**: Protects against deplatforming by eliminating reliance on centralized infrastructure, ensuring the project remains accessible in a decentralized ecosystem.
|
||||
|
||||
### 2. GitLab
|
||||
- **URL**: [$GITLAB_URL]($GITLAB_URL)
|
||||
- **Purpose**: GitLab offers a comprehensive DevOps platform with advanced CI/CD capabilities, private repository options, and robust access controls. It serves as a reliable backup and a platform for advanced automation workflows.
|
||||
- **Value**: Enhances project resilience with its integrated CI/CD pipelines and independent infrastructure, reducing reliance on a single provider.
|
||||
### 2. GitLab - **URL**: [$GITLAB_URL]($GITLAB_URL) - **Purpose**: GitLab offers a comprehensive DevOps platform with advanced CI/CD capabilities, private repository options, and robust access controls. It serves as a reliable backup and a platform for advanced automation workflows. - **Value**: Enhances project resilience with its integrated CI/CD pipelines and independent infrastructure, reducing reliance on a single provider.
|
||||
|
||||
### 3. Bitbucket
|
||||
- **URL**: [$BITBUCKET_URL]($BITBUCKET_URL)
|
||||
- **Purpose**: Bitbucket provides a secure environment for repository hosting with strong integration into Atlassian’s ecosystem (e.g., Jira, Trello). It serves as an additional layer of redundancy and a professional-grade hosting option.
|
||||
- **Value**: Offers enterprise-grade security and integration capabilities, ensuring the project remains accessible even if other platforms face disruptions.
|
||||
|
||||
### 4. Radicle
|
||||
- **URL**: [$RADICLE_URL]($RADICLE_URL)
|
||||
- **Purpose**: Radicle is a decentralized, peer-to-peer git platform that ensures sovereignty and censorship resistance. It hosts the repository in a distributed network, independent of centralized servers.
|
||||
- **Value**: Protects against deplatforming by eliminating reliance on centralized infrastructure, ensuring the project remains accessible in a decentralized ecosystem.
|
||||
### 4. GitHub
|
||||
- **URL**: [$GITHUB_URL]($GITHUB_URL)
|
||||
- **Purpose**: GitHub serves as the primary platform for visibility, collaboration, and community engagement. Its widespread adoption and robust tooling make it ideal for public-facing development, issue tracking, and integration with CI/CD pipelines.
|
||||
- **Value**: Provides a centralized hub for open-source contributions, pull requests, and project management, ensuring broad accessibility and developer familiarity.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -98,6 +93,7 @@ This multi-repository approach reflects a commitment to preserving the integrity
|
|||
- **Metadata Files**: Each platform generates a metadata snapshot in the \`.gitfield\` directory (e.g., \`github.sigil.md\`, \`gitlab.sigil.md\`, etc.), capturing commit details, environment information, and hardware fingerprints.
|
||||
- **Push Log**: The \`.gitfield/pushed.log\` file records the date, time, and URL of every push operation across all platforms, providing a transparent audit trail.
|
||||
- **Recursive Sync**: The repository is synchronized across all platforms in a recursive loop (three cycles) to ensure interconnected metadata captures the latest state of the project.
|
||||
- **Push Order**: The repository is synchronized in the following order: **Radicle → GitLab → Bitbucket → GitHub**. This prioritizes Radicle’s decentralized, censorship-resistant network as the primary anchor, followed by GitLab’s robust DevOps features, Bitbucket’s enterprise redundancy, and GitHub’s broad visibility, ensuring a resilient and accessible metadata chain.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -149,10 +145,10 @@ run_push_cycle() {
|
|||
info "Starting push cycle $cycle_number..."
|
||||
|
||||
# Push to each platform in order
|
||||
execute_push "gitfield-github" "GitHub" "$GITHUB_URL"
|
||||
execute_push "gitfield-radicle" "Radicle" "$RADICLE_URL"
|
||||
execute_push "gitfield-gitlab" "GitLab" "$GITLAB_URL"
|
||||
execute_push "gitfield-bitbucket" "Bitbucket" "$BITBUCKET_URL"
|
||||
execute_push "gitfield-radicle" "Radicle" "$RADICLE_URL"
|
||||
execute_push "gitfield-github" "GitHub" "$GITHUB_URL"
|
||||
}
|
||||
|
||||
# ╭─────────────────────────────────────╮
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue