[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technology-en-digitalocean":3,"technology-projects-en-digitalocean":28,"mdc-bcb9jk-key":77},{"id":4,"title":5,"category":6,"content":7,"description":8,"extension":9,"faq":10,"icon":11,"links":12,"meta":21,"projects":22,"since":24,"stem":25,"updated":26,"__hash__":27},"technologies_en\u002Fen\u002Ftechnologies\u002Fdigitalocean.yml","DigitalOcean","infrastructure","DigitalOcean is a cloud infrastructure provider. I used its Droplet virtual machines for early DigiSpace projects, managing the Linux environment and deploying the applications myself.\n\n## Working with Droplets\n\nRunning separate virtual machines gave each service its own configuration and release cycle. The work included web servers, database setup, firewall rules, operating system updates and backups. A Droplet is an unmanaged server: creating it is quick, but keeping its software running remains the operator's responsibility.\n\n## Moving to dedicated hosting\n\nAs my hosting setup grew, I moved workloads to a rented Hetzner dedicated server with Proxmox. Docker made the application environments easier to transfer. Persistent data, DNS changes and recovery planning still needed separate attention.\n\n## How I compare hosting options\n\nI consider resource use, maintenance time, backup storage and availability requirements together. Cloud virtual machines are useful when environments need to be created or resized independently. A dedicated server can suit steady workloads, but it also concentrates services on one physical machine. Neither option is automatically cheaper for every project.\n","DigitalOcean hosting experience: Linux Droplets, application deployments and the move to a dedicated server for ongoing SaaS workloads.","yml",null,"i-simple-icons-digitalocean",[13,18],{"label":14,"to":15,"color":16,"icon":17},"digitalocean.com","https:\u002F\u002Fwww.digitalocean.com","neutral","i-heroicons-arrow-top-right-on-square",{"label":19,"to":20,"color":16,"icon":17},"Technical reference","https:\u002F\u002Fdocs.digitalocean.com\u002Fproducts\u002Fdroplets\u002Fdetails\u002Fpolicies\u002F",{},[23],"digispace","2020","en\u002Ftechnologies\u002Fdigitalocean","2026-09-20","Zr41-b59GxzuyZY1nrISaZYPmAv0udTW4opUm2x3pBM",[29],{"id":30,"title":31,"content":32,"date":33,"description":34,"extension":9,"featured":35,"image":36,"links":37,"meta":46,"stack":47,"stem":72,"tags":73,"url":40,"__hash__":76},"projects_en\u002Fen\u002Fprojects\u002Fdigispace.yml","DigiSpace","The production website behind digispace.pro — the agency's public site, admin panel and custom CMS in a single Laravel app, now fully multilingual (EN\u002FUK\u002FPL) with a Filament admin panel running alongside the legacy Inertia + Vue one. The same code that runs the live site is available on GitHub.\n\n## Key Features\n\n- **Filament admin panel** - a parallel `\u002Fcontrol` panel (24 resources) with a TipTap rich editor, straight-to-MinIO image uploads and content-first navigation, rolled out resource-by-resource next to the existing Inertia admin\n- **Multilingual by design** - both content and structural UI strings (menus, footer, buttons) are translated per locale, not just page text, with hreflang-aware localized routing\n- **SEO built in** - JSON-LD structured data, localized sitemaps and proper 404 handling across every locale\n- **Monolith done right** - public site and two admin surfaces live in one Laravel app, no separate API to maintain\n- **Self-managed content** - pages, services and portfolio entries are edited in the CMS — no deploy needed for a text or translation change\n- **Quality gates** - PHPUnit tests and PHPStan static analysis run in CI\n- **Source available** - the exact code serving digispace.pro is public on GitHub\n\n## Tech Stack\n\n- **Backend**: Laravel\n- **Admin**: Filament 5 (`\u002Fcontrol`) + legacy Inertia.js + Vue admin\n- **Frontend**: Vue.js, Vite\n- **Localization**: EN\u002FUK\u002FPL content and structure translations\n- **Architecture**: Custom CMS\n","2022-10-05","The agency's multilingual (EN\u002FUK\u002FPL) production site with a custom CMS — a Filament admin panel with a rich content editor, content translations, JSON-LD and localized sitemaps built in, alongside the legacy Inertia + Vue admin",true,"\u002Fhero\u002Fdigispace.avif",[38,42],{"label":39,"to":40,"color":41,"icon":17},"Live Demo","https:\u002F\u002Fdigispace.pro","primary",{"label":43,"to":44,"color":16,"icon":45},"GitHub","https:\u002F\u002Fgithub.com\u002FYurij2015\u002FDigiSpace","i-simple-icons-github",{},[48,51,54,57,60,63,66,69],{"name":49,"icon":50},"Laravel","i-simple-icons-laravel",{"name":52,"icon":53},"Inertia","i-simple-icons-inertia",{"name":55,"icon":56},"Vue","i-simple-icons-vuedotjs",{"name":58,"icon":59},"Vite","i-simple-icons-vite",{"name":61,"icon":62},"MySQL","i-simple-icons-mysql",{"name":64,"icon":65},"Tailwind CSS","i-simple-icons-tailwindcss",{"name":67,"icon":68},"Filament","i-simple-icons-filament",{"name":70,"icon":71},"CMS","i-heroicons-document-text","en\u002Fprojects\u002Fdigispace",[49,67,52,55,74,75],"i18n","SEO","dtWB-9st6fApdLs4qomkqmMQVq9PBqeHoPzR0Ywgu0I",{"data":78,"body":79},{},{"type":80,"children":81},"root",[82,90,97,102,108,113,119],{"type":83,"tag":84,"props":85,"children":86},"element","p",{},[87],{"type":88,"value":89},"text","DigitalOcean is a cloud infrastructure provider. I used its Droplet virtual machines for early DigiSpace projects, managing the Linux environment and deploying the applications myself.",{"type":83,"tag":91,"props":92,"children":94},"h2",{"id":93},"working-with-droplets",[95],{"type":88,"value":96},"Working with Droplets",{"type":83,"tag":84,"props":98,"children":99},{},[100],{"type":88,"value":101},"Running separate virtual machines gave each service its own configuration and release cycle. The work included web servers, database setup, firewall rules, operating system updates and backups. A Droplet is an unmanaged server: creating it is quick, but keeping its software running remains the operator's responsibility.",{"type":83,"tag":91,"props":103,"children":105},{"id":104},"moving-to-dedicated-hosting",[106],{"type":88,"value":107},"Moving to dedicated hosting",{"type":83,"tag":84,"props":109,"children":110},{},[111],{"type":88,"value":112},"As my hosting setup grew, I moved workloads to a rented Hetzner dedicated server with Proxmox. Docker made the application environments easier to transfer. Persistent data, DNS changes and recovery planning still needed separate attention.",{"type":83,"tag":91,"props":114,"children":116},{"id":115},"how-i-compare-hosting-options",[117],{"type":88,"value":118},"How I compare hosting options",{"type":83,"tag":84,"props":120,"children":121},{},[122],{"type":88,"value":123},"I consider resource use, maintenance time, backup storage and availability requirements together. Cloud virtual machines are useful when environments need to be created or resized independently. A dedicated server can suit steady workloads, but it also concentrates services on one physical machine. Neither option is automatically cheaper for every project."]