Blog Listing Management
Create listing entries via a simple form, preview JSON, merge with the live SVN blogs.json, and deploy — no manual JSON editing required.
Two systems: This app runs on jsonbuilder.gventure.info (cms-json server). blogs.json lives on a different remote SVN server: newsvn.gventure.co.in — fetch/commit goes over the network.
/var/www/html/cms-json
JSON Builder app — Repo A
http://newsvn.gventure.co.in/repos/gventure_website/website/Gventure_web_design/server/gventure_website/en/blogs.json
Website JSON — Repo B (not on this server)
/var/www/html/cms-json/svn-workspace/en
Temporary checkout folder — disk only, not the repo
Workflow: Create Entry → Generate JSON Preview → Fetch SVN JSON → Preview Merge → Merge to SVN
Blog Entry
Fill in the card fields. Blog ID is assigned automatically from the next available ID in SVN.
Entry Preview
Current SVN Data
Fetch blogs.json from the remote SVN repo URL below (not from a local folder path).
- Remote SVN server
- newsvn.gventure.co.in
- SVN Repo URL (remote — Repo B)
- http://newsvn.gventure.co.in/repos/gventure_website/website/Gventure_web_design/server/gventure_website/en/blogs.json
- Local cache folder (this server only)
- Checkout cache — not the repo URL
SVN Fetch Diagnostics
- Total Blogs
- 0
- Next Available ID
- —
- Data source
- —
Current JSON (blogs[] only)
Merge Preview
New entries are inserted at the beginning of blogs[] (newest publish date / highest id first). If the slug already exists in SVN, the listing card is updated in place (same id; order follows publish date).
Merged JSON — new entry highlighted
Deployment
Validate, backup, merge, and commit to SVN. The frontend listing page reads this file automatically.
Last Merge
- Time
- 2026-06-16T07:18:41+00:00
- Action
- merge_to_svn (append)
- Revision
- 74119
- Blog ID
- 31
- Title
- How SMS Marketing Helps Businesses Reduce Customer Acquisition Costs
- Backup
- /var/www/html/cms-json/logs/blog-listing-backups/blogs-backup-2026-06-16_071840.json