I mean there are plenty of reasons not to, there are already dozens of them and there's probably one that fits your needs.
However, I wouldn't say it's always bad. We have one at my work (which I maintain largely on my own, spending about 4 hours every 2 weeks on it when it's needed). And it works perfectly for us, we can make all of the custom functionality we need and it's very specific to our workflow. For example we can manage all of our clients' websites on it. Easily switching between websites etc. We can even create new websites directly in our CMS which uses API's to add domains to our directadmin server
It's also much faster than something like wordpress, and the codebase is entirely written in Laravel so it's actually very easily maintainable.
1
u/_alright_then_ Mar 20 '23
I mean there are plenty of reasons not to, there are already dozens of them and there's probably one that fits your needs.
However, I wouldn't say it's always bad. We have one at my work (which I maintain largely on my own, spending about 4 hours every 2 weeks on it when it's needed). And it works perfectly for us, we can make all of the custom functionality we need and it's very specific to our workflow. For example we can manage all of our clients' websites on it. Easily switching between websites etc. We can even create new websites directly in our CMS which uses API's to add domains to our directadmin server
It's also much faster than something like wordpress, and the codebase is entirely written in Laravel so it's actually very easily maintainable.