snapshot: preserve workdock repo rename phase

This commit is contained in:
Md Bayazid Bostame
2026-03-27 00:33:28 +01:00
parent 8553482ddd
commit bbc9b7b646
2 changed files with 5 additions and 5 deletions

View File

@@ -6,7 +6,7 @@ Turn the current TUBCO-specific onboarding/offboarding portal into Workdock, a r
Current branch roles:
- `main`: current TUBCO-oriented working baseline
- `main`: current TUBCO customer baseline
- `product_company_portal_foundation`: generic product-development branch
## Core Product Principles
@@ -180,7 +180,7 @@ Reason:
Examples already identified:
- `TUBCO Onboarding & Offboarding Portal`
- former TUBCO-specific portal title kept only as historical baseline context
- logo asset references
- invitation email wording mentioning TUBCO
- welcome-email defaults mentioning TUB/CO
@@ -209,7 +209,7 @@ This is the first productization slice because it gives:
## Guardrails
- keep current TUBCO defaults as the initial values
- keep current customer deployment values stable while generic product defaults move to Workdock
- keep migrations backward-compatible
- update both wiki and developer handbook for every architecture change
- snapshot at the end of each major phase

View File

@@ -41,7 +41,7 @@
<div class="box">
<p>This handbook is for developers and maintainers. It documents the actual engineering workflow of the standalone product repository.</p>
<ul>
<li>Repository: <code>tubco-onboarding-offboarding-portal</code></li>
<li>Repository: <code>workdock-platform</code> (current local path; legacy compose project name may still be retained for runtime continuity)</li>
<li>Main stack: Django + Celery + PostgreSQL + Redis + MailHog</li>
<li>Runtime mode: Docker Compose for local development and staging-style operation</li>
</ul>
@@ -64,7 +64,7 @@
<h2 id="local">3) Local Development Workflow</h2>
<h3>Start</h3>
<pre><code>cd /Users/bostame/Documents/tubco-onboarding-offboarding-portal
<pre><code>cd /path/to/workdock-platform
docker compose up -d --build</code></pre>
<h3>Main URLs</h3>
<ul>