TITOLO:
[Directus + JSON export] Quick beta setup — 8 days, $300 fixed
CORPO:
Hi everyone,
Looking for a Directus dev for a beta setup on an existing Hetzner server.
WHAT THIS PROJECT IS NOT
- Not a custom backend build — Directus handles the schema and admin
- Not a frontend custom UI — standard Directus interface is fine
- Not a complex data model — single collection, no advanced relationships
- Not a Python codebase to touch — the existing voice pipeline stays untouched
- Not a complex integration — your script writes JSON files to disk, that’s the contact point
- Not an exotic setup — standard Directus on Docker, standard SSL, standard scheduling
WHAT THE WORK IS
- Directus on Docker (dedicated container, isolated from other services on the host)
- “clients” collection with 12 fields: 8 simple data fields (string, dropdown, boolean) and 4 long-text containers for content I’ll write myself
- Conditional field visibility based on business_type dropdown
- Italian UI labels
- Export script (Python or Bash, your call) writing JSON files in a format I’ll provide as reference
- Cron or Directus Flow for scheduling
- Subdomain + Let’s Encrypt SSL
- Brief markdown docs
BUDGET & TIMELINE
$300 fixed-price, 8 days from contract start. Two informal check-ins (Day 3 and Day 6, screenshot or short video).
Payment via Upwork escrow once we agree.
TO APPLY
Reply with:
- Share 1-2 Directus projects you’ve worked on (links, screenshots, or commits — whichever is easiest)
- How would you structure the export script to handle the case where the consumer process reads a file while you’re rewriting it? (one short paragraph)
- How would you handle Directus updates without breaking the running setup on the host? (one short paragraph)
Looking forward to hearing from someone who enjoys clean Directus setups.
Giorgio