You don’t mention if you have virtualmin pro if you don’t
Buy virtualmin pro that is integrated with a nice ui
Which gets around it I guess, however as I don’t use wordpress this post maybe totally wrong
Apologies for not specifying, but I have Virtualmin Pro.
I think the WP Workbench is a Pro-only feature - at least, the last topic I read on it indiciated it was.
And thank you for mentioning the GUI, but I had hoped my message made it clear that I’m not trying to use the GUI. The entire point is to be able to write bash scripts for automation and voide the GUI, because the GUI - while nice - is not nearly as fast as CLI.
Yes, we have a CLI for nearly everything, and both WP Workbench and the upcoming WP Workbench Manager will have full CLI support.
To create a new virtual server, use Virtualmin’s virtualmin create-domain command. To install an LE certificate, use virtualmin generate-letsencrypt-cert. To install a new WordPress app, use the virtualmin install-script sub-command. For WP Workbench, use virtualmin configure-script --app wordpress (currently it’s --script-type, but that will change to --app in the new release).
The upcoming Virtualmin and WP Workbench releases will let you manage multiple WordPress instances on one or more servers, update all instances, themes, and plugins at once, schedule backups, and handle many other automated tasks. The new API command will be virtualmin configure-all-scripts --app wordpress, and it comes with an extensive set of options.
When you run it, you’ll see detailed descriptions and plenty of examples.
You can also use the remote API as a domain user for both configure-script and configure-all-scripts, like this:
You’ll have to wait for this to go live in production, but the development versions are available at software.virtualmin.dev, which has the latest Virtualmin and WP Workbench (including Manager) if you want to test it out, especially since you seem quite tech-savvy.
I’m working through what you gave me, and struggling a bit on instaling Wordpress.
Do I need to create a database first? I’m hoping to use the existing user’s database, just specify the name to use, like if my user is “sampleuser”, I’d like to use e.g. “sampleuser_wp1” or somesuch.
It’s saying database exampledb doesn’t exist, but I confirmed it does in the database settings for the domain - there’s already three scripts using it, in fact… so maybe I’m missing something here…
Also for anyone looking to do this, here’s anonymized versions of the commands I used that might be something like the bare minimum that might help you along:
No, you don’t. Installation script will handle it all for you.
I recommend against it. It’s better to have a separate database for each application, as this is a much better design.
It’s saying database exampledb doesn’t exist , but I confirmed it does
Is this database associated with the virtual server? You can check it by running virtualmin list-databases --domain example.com command. If not, you can import it by using virtualmin import-database.
And somehow I forgot that child sites still get their own db.
You rock so very much!
And while I hesitate to install the dev version of virtualmin… I will absolutely be playing with this when it hits release!
I write simple bash scripts, but I’ve had AI help me be lazy and write a script that prompts for information like domain name, username - but also sets defaults like my contact email and things like that - then allows me to choose what to do from a text menu (i.e. numbered list of options) - like install wordpress, the Divi theme I have stred in a location accessible to all users…
I’ll do a writeup of this proess at some point soon and post a link to it in case it helps others.
Thank you for pointing me down the right path on this stuff!
