Setting up Wordpress Blueprints in Cloudron?
-
Could someone run me through hypothetically the best way to set up pre-configured Wordpress (Developer) instances that I can launch from within Cloudron?
Please treat me as a complete newbie.
What I'm trying to do is take the Wordpress Developer "base" instance, and then pre-configure/add a default custom theme, plugins, licenses, customer name etc. I'm not expecting RunCloud here, just trying to evaluate the level of effort required to set something like this up and then maintain it as new updates are pushed.
So for example, when a new version of the Developer "base" image comes along from the Cloudron team, how could I automate pulling it and bundling my changes in? If someone could provide me with like a high level play by play of how that would work I think I can Chat GPT the details.
Much appreciated!
-
@umnz the basic idea would be to use the clone or the import functionality .
- Install WP. Configure it as needed. This is your base instance
- Take a backup of the app.
- Stop this app.
- When you want a new install, clone from the backup
You can always start the app again and update your base template.
Another idea is that you can use the new archive feature to archive the base app and then "restore" to create new app instances.
-
@umnz the basic idea would be to use the clone or the import functionality .
- Install WP. Configure it as needed. This is your base instance
- Take a backup of the app.
- Stop this app.
- When you want a new install, clone from the backup
You can always start the app again and update your base template.
Another idea is that you can use the new archive feature to archive the base app and then "restore" to create new app instances.
@joseph said in Setting up Wordpress Blueprints in Cloudron?:
You can always start the app again and update your base template.
I might even leave it running with auto updates on, otherwise it'd likely quite quickly get very out of date. Then clone from most recent backup.
-
I do this as well. I just have a www.template.(mydomain) install running. I use this as my blueprint site, and I leave it running for updates and to make sure it’s backed up routinely. I then clone from the backup to the new domain at www.staging.(theirdomain) when I’m starting a new site for a client, for example.