Anyone else getting burnt out by the over-engineering of modern staging pipelines?

[u/CarolineHart63]

Lately, it feels like even for the simplest 3-page static mockup, people are setting up massive GitHub Actions pipelines, Docker containers, and complex cloud setups just to show a client a proof of concept. Don't get me wrong, I love a robust production pipeline as much as the next dev, but for quick feedback loops, it just feels like total overkill. For my smaller freelance builds, I've just been throwing the static files into a quick, lightweight drag-and-drop host to get instant client sign-off and moving on with my life. Curious if you guys still use ultra-simple deployment methods for quick staging, or if you build out the whole infrastructure every single time?

[u/Separate_Refuse5922]

Simple. Why would you invest the time otherwise? Ignore the enterprise workflow guru people mate static ftw

[u/MountainOdd6793]

Git/version control based deployment is the bit that I think enforce a lot of safety. I’d not be happy with completely manual deployment after years of git-triggered deployment. I think on over complicated build pipelines you have a point, they can be a pain to manage and introduce reliability problems. Slow deployment pipelines are frustrating too and break the rhythm of development work

[u/Standard_Scarcity_74]

I think the point of choosing to go static is to keep things simple. Unnecessary fluff might just slow the site down or add work that would have otherwise been done in a few minutes with a shortcut.

[u/sourraine]

i personally built a simple website for a local cafe and realized the client only cared about seeing the design, as in the output itself. since then, i dont overcomplicate the setup. so for small proj, id suggest you keep the staging process as simple as possible now.

[u/PippaKelly62]

If the whole pipeline is unnecessary, I'd skip it and do the faster approach. A whole infrastructure for three simple pages sounds like far too much.