[module0000]

I get this experience using non-netlify-specific tools and processes already. I've also been doing this type of work professionally for 15+ years. If I was just starting out today, netlify would be a huge time saver, at the cost of a ton of knowledge you gain doing it yourself.

"But wait...there's more". If you're a new to development or operations, you might be tempted to use something like netlify. If your project has a high probability(>75%) of generating real income, then DEFINITELY use netlify. Anything that stands between you and deployment is costing you money. But... if your project is a hobby or non-serious-revenue-generating endeavor: please please please do it yourself. Learn apache syntax, learn nginx syntax, explore why `setenforce 0` is for hacky amateurs. You'll learn marketable skills, that will help you in your future career endeavors.

Netflify creates a skilled "user of netlify". Doing it yourself creates an "engineer". Which of those two would you rather be?

[rchaud]

As someone who works in the amorphous realm of "digital strategy", I was pursuing this exact "learning path" by deploying my personal website on Digital Ocean, where your droplet is a blank slate, and you have to configure everything.

Given the number of help threads and spotty documentation I had to look through to deploy a simple Wordpress site, I'd say it was more of a hassle than anything else. Unless you plan on doing this several more times, at which point you'd likely have worked the kinks out, stick with deepening your knowledge in an existing area of proficiency.

[hbosch]

Not to turn a Netlify topic into a DigitalOcean topic, but when you created your droplet did you select the pre-built Wordpress option? May have helped you a bit. (I used dokku-wordpress[0] on my dokku imaged server, personally.)

--

0. https://github.com/dokku-community/dokku-wordpress

[rchaud]

I did not, specifically because I wanted to learn how DO worked, without any "Wordpress 1-click wizard" stuff. Bluehost has the same "Instant Wordpress" thing that I avoid, as I write my own CSS and page templates and I wasn't planning to use an off-the-shelf theme.

On DO, I learned that you have to set up everything yourself, like SSH, Apache, MySQL, PHP, SFTP. I haven't found good documentation on how to set up a Git workflow from my local dev environment, so that's the next step. I have a non-database PHP site I plan to use for that.

[reificator]

> But... if your project is a hobby or non-serious-revenue-generating endeavor: please please please do it yourself. Learn apache syntax, learn nginx syntax, explore why `setenforce 0` is for hacky amateurs. You'll learn marketable skills, that will help you in your future career endeavors.

One of the many hats I wear is to do a lot of those things[0]. I setup nginx inside a docker container to act as a reverse proxy for an http api living in another container, and now that's done but it's time to put on another hat and train users on the new core platform we're using, but now it's time for the legacy maintenance hat, but this hat is on fire, and...

If I'm working on a project for fun, I want to have as few barriers as possible, because I'm already facing an uphill motivational battle after a long day at work, or on a weekend where I just want to relax.

[0]: I did have to lookup `setenforce`, because I've never had reason to disable SELinux.