Temp Questions
Phase 0 Questions
Q1 — Project URL structure RF uses /projects/{username}/active/001.html. For DS, simplify to /projects/{username}/001.html (drop the active/ from the public URL), or keep it identical to RF?
Q2 — DS site fund donations Does directsponsor.net need its own general donations page (to cover DS server/hosting costs), separate from the direct-to-project donations? Or is DS purely project-focused with no general fund?
Q3 — RF after migration After the fundraiser system moves to DS, does roflfaucet.com:
- (a) Keep its own minimal site-income/donations page for faucet hosting costs (independent of DS)
- (b) Remove donations entirely and just link to DS projects
- (c) Something else
Q4 — User accounts on DS Does DS need its own user registration and login, or will users always log in via RF (cross-site JWT)? The difference matters — if DS is standalone it needs its own auth flow.
Q5 — Webhook secret The RF webhook secret is currently roflfaucet_webhook_secret_2024. DS should have its own distinct secret. Do you want to pick one now, or leave it as a placeholder in the plan?
Q6 — Migration timing / order Is the intent to:
- (a) Build DS fundraiser system fresh (copy RF code as a starting point, adapt it), go live on DS, then strip it from RF
- (b) Run both in parallel for a while (RF and DS both show fundraisers, DS as the new home)
- (c) Something else — e.g. RF stays as-is while DS is built up, hard cutover once DS is ready
Q7 — Existing project data (lightninglova, evans) The live donation data currently lives on the RF server (/var/roflfaucet-data/projects/). When DS is ready, should those projects move to DS (RF no longer has them), or should they be mirrored on both during transition?