Your dynamic website (often called a webapplication) is very probably
OS-specific anyway. I've seen websited that can run only on Ubuntu. Most often
you could as well settle with what OS provides to deploy it, especially that
you won't need another instance on the same server. Even more so if it's not
a hobbyst project, but a professional one.
> I don't use OS specific packaging because it was intentionally written to be
non-portable.
Only if you use it mindlessly. It's not really different to build a package
for Debian, Red Hat, Slackware, or Gentoo (been there, done all of these). All
it takes is to properly separate downloading sources and building things,
which is a good engineering on its own. And guess what you get in exchange?
Easy dependency installation, both for development and for deployment.
> I don't use OS specific packaging because it was intentionally written to be non-portable.
Only if you use it mindlessly. It's not really different to build a package for Debian, Red Hat, Slackware, or Gentoo (been there, done all of these). All it takes is to properly separate downloading sources and building things, which is a good engineering on its own. And guess what you get in exchange? Easy dependency installation, both for development and for deployment.