4 ms·
And that's the problem; by then it's too late (i.e. never took the time to backup the db). It's about finding the balance, writing a PHP app shouldn't involve s
by esquire_900 6y ago
And that's the problem; by then it's too late (i.e. never took the time to backup the db). It's about finding the balance, writing a PHP app shouldn't involve studying C compilers and CPU design. But I think these tools (whichever you decide to use) are such an essential part of what you're building that "outsourcing" them as much as possible might be a bit ignorant.
That being said, as long as it works, it works. And if your app is small enough never to get into the grey waters, all the better.
- dan_can_code 6y agoI absolutely agree, were it something commercial these things would need to be considered. Are there any tools you recommend looking into, were I to take the next step? I don't plan on depending on CapRover to fill gaps in my knowledge for too long, but for now this product really is a good start for me.
- esquire_900 6y agoNo problem in depending on CapRover, as long as you are at least somewhat familiar with the tools it sets up for you. Combine that with some crude generic UNIX skills (quickly analyze cpu/ram/disk usage, search in logs, transfer files, modify configs etc.) and you're way better prepared. Ironically it's best learned "on the job" (for me at least); just try to deploy your app from scratch. Play around with nginx/apache, letsencrypt, your db stack, packages installation etc. and get a working product. I'm no expert by far in any of this, but think that knowing "just enough" about these tools really helped along the way. Up to the point where I can now use CapRover like tools with some degree of confidence, closing the full circle ;)
- dan_can_code 6y agoThanks for the info. I look forward to learning from it. I will try the 'on the job' approach as that's how I learn most effectively. :-)