Your Sovereign Lines dual-repository structure is now fully configured and validated.
./init.shGo to GitHub and create two new PRIVATE repositories:
SovereignLinesIO-frontend(will be public, GPL-3.0 licensed)SovereignLinesIO-backend(will remain private, proprietary)
# Add frontend remote
git --git-dir=.gitman/frontend remote add origin https://github.com/Nickalus12/SovereignLinesIO-frontend.git
# Add backend remote
git --git-dir=.gitman/backend remote add origin https://github.com/Nickalus12/SovereignLinesIO-backend.git# Create initial frontend commit
./push-frontend.sh "Initial commit - Sovereign Lines frontend"
# Create initial backend commit
./push-backend.sh "Initial commit - Sovereign Lines backend (proprietary)"The push scripts will automatically push to GitHub if remotes are configured.
./status.sh# Push to both repos
./push-all.sh "Your commit message"
# Or push individually
./push-frontend.sh "Frontend changes"
./push-backend.sh "Backend changes"# Create feature branch
./create-feature.sh my-new-feature
# Work on your feature...
# Merge back to main/develop
./merge-feature.sh my-new-feature main- Never commit secrets - The backend repo is private but still follow security best practices
- Frontend is public - Don't include any proprietary logic in frontend code
- Use the scripts - Always use the provided scripts to ensure proper gitignore switching
- Regular backups - The scripts create backups, but consider additional backup strategies
-
Frontend (Public, GPL-3.0):
- Client-side code
- Public documentation
- Frontend CI/CD
-
Backend (Private, Proprietary):
- Server code
- Game logic
- Security systems
- Backend CI/CD
- Check
./validate-setup.shto ensure everything is configured correctly - Review the scripts in this directory for available commands
- See
docs/README.mdfor detailed documentation