10 Provision a single DigitalOcean droplet as unified LEMP / Node.js server for front and back end staging/production instances

victorkane commented 3 years ago

It's tempting to go with Cloudways or with SpinupWP, and automate everything with GUI control, and still retain control over the raw metal VP servers. But SpinupWP (look very cool) came out with a video training playlist on how complicated it would be to do things without their great automation and standardization. And it is complicated. It's just that with years of experience doing this, I realized that while for many people I really recommend going that route, but I don't really find any hurdles in the steps they outline, it really would be simpler, more transparent for me to do things myself and have fewer dependencies and third-party solutions.
So, LEMP server non-docker open source solution to manage a similar command-line driven thing along the same lines, where I can manage everything myself for wp instances: WordOps.
I could use SiteGround as a really simple place to stash the headless WordPress CMS, but they exclude Node.js from their otherwise excellent WordPress server solutions. So, with my own VP + automated help, the front end will allow for Node.js provisioning for Frontity or Next.js Clients if I want them on the same server, or neighboring "droplets", say, on DigitalOcean (See awebfactory/frontity-awf#2).

victorkane commented 3 years ago

[x] Create sturdy LEMP and NodeJS ready DO server
[x] Install and configure WordOps and spin up Staging/Production WP instances
[x] Push Flywheel Local instance to Staging, establish back and forth easy workflow
[x] Establish back and forth easy workflow between Staging and Production instances
[x] Launch already (see #2 11 Deploy staging/production backend instances. Launch

victorkane commented 3 years ago

victorkane commented 3 years ago

victorkane commented 3 years ago

victorkane commented 3 years ago

victorkane commented 3 years ago

awebfactory / wp-awf