Thanks for sharing the script. I maintain a couple of WordPress installations in my server and this will surely save me lot of time in keeping them updated.
Thanks Sudar – Hope you find it useful. Note that I found one small bug in the chown line (143) and just fixed it. You might want to grab a fresh copy, or just change line 143 to:
chown -R $owner:$owner *
(the previous version changed the ownership of the parent directory).
I haven’t set up my blog yet but I’m planning on customizing my wp configuration with plugins and themes
I was thinking that I’d need to install wp on my dev box and then svn checkin into my own SVN server from the dev box then svn update on the production box
Is there a way to use the wp SVN and still have customizations in my own SVN do you think?
Stuart – Your customizations would be in themes and plugins, not in core, right? So… no problem – just point the script to your own svn repo rather than to the official one.
I haven’t figured out how to set up svn so that the bulk of the wordpress files can come from the public svn while still maintaining my own svn of the local customizations
Right now I’m exporting the public wp svn into a folder structure and manually updating the core files in my own svn, then checking those files into my own svn, this works but introduces the potential for a screw up or two.
I was trying to install “WP-Create” and WP-mass Install.
But I don’t know how to start .. Its a just a text file. Its it a server side script ?
Can you help me how to proceed.
Ranga – Yes, it’s a bash shell script. It assumes a pre-existing knowledge of working with shell scripts. But basically just put in a directory along with root’s other scripts, chmod 700, and run it:
nice script! do you have any plans to automate symlink-based WP installs/upgrades? i run a few high-traffic blogs which had always been competing with each other for APC (inode-to-opcode cache) space: symlink-sharing their WP installs got rid of this redundancy.
Thanks Chris. No, I don’t have plans to do that particular modification. If you do, let me know and I’ll incorporate it if it plays well with the standard setup.
Hi Lee – This is a shell script that runs outside of WP. It is ignorant of WP itself and thus it is not possible for it to have a version incompatibility.
Great work, found this as I was about to (painfully) try and write a script to that effect. Apparently though, I get a syntax error when trying to run it on a standard (CentOS) dedicated Linux server: After all the input infos are entered, the script outputs
“./WP-create.sh: line 52: syntax error near unexpected token `newline'”
Did I do something wrong on installing it ?
Thank you !
Dennis – You’ll want to comment out either of line 50 or 51. If your system is not cPanel, you probably want to comment out line 51 (still I’m surprised you’re getting that error…)
Also try and “show invisibles” in your text editor to make sure you haven’t introduced some kind of hidden character after a line somewhere.
Thanks for the quick and efficient reply, I managed to make it run by changing those lines as I am indeed not using CPanel. I will now try to extend the script by appending the correct Virtual Host value and restart Apache: as I have a wildcard DNS thingy, this should make an instant functional WordPress install.
You have an interesting blog by the way !
Kudos for sharing such nice scripts.
Also if i have got fantastico installation will i be able to do a mass update on those as well by including them in the list without doing a fresh install.
(i have +- 120 wp installations and getting tired of doing upgrades one by one so this will work perfectly for me)
Johan – ” svn: command not found” means, of course, that you don’t have svn installed. Obviously you’ll need to install subversion if you want to use a tool that wp-create that’s all about managing WP via subversion.
As for the fantastico problem… I’m very familiar with that one 🙁 Your goal here is to take control of managing upgrades out of your user’s hands and put it in your own hands. And unfortunately that means a few things. 1) You need to disable WordPress in Fantastico so people are no longer able to use it, and 2) You need to convert all of those old non-subversion installations into subversion installations. I don’t have a script for that but I did write most of the Codex page covering the process — the last section of http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion . So yes, that initial process will be painful, but once you have all installations converted, the upgrade path server-wide becomes seamless and effortless. Worth putting the work in up front.
Denny – wpcreate already does generate the key for you. The rest are good suggestions. I’m in the middle of another project for a while but will definitely do these for the next revision. Patches welcome.
Hi everyone – I’m happy to announce a new version of wp-create and wp-mass-upgrade, including automatic backup of each database in the array and a new plugin finding tool. The tools have been folded into a single kit:
Thanks for sharing the script. I maintain a couple of WordPress installations in my server and this will surely save me lot of time in keeping them updated.
Thanks Sudar – Hope you find it useful. Note that I found one small bug in the chown line (143) and just fixed it. You might want to grab a fresh copy, or just change line 143 to:
chown -R $owner:$owner *(the previous version changed the ownership of the parent directory).
Hi
I haven’t set up my blog yet but I’m planning on customizing my wp configuration with plugins and themes
I was thinking that I’d need to install wp on my dev box and then svn checkin into my own SVN server from the dev box then svn update on the production box
Is there a way to use the wp SVN and still have customizations in my own SVN do you think?
Thanks
Pingback: Installing Multiple Blogs
Stuart – Your customizations would be in themes and plugins, not in core, right? So… no problem – just point the script to your own svn repo rather than to the official one.
Pingback: Links for Wed 14 May 2008 - Joseph Scott’s Blog
Thanks Shacker!
You mean change the svn checkout line
svn co http://svn.automattic.com/wordpress/tags/$wpver/
to
svn co http://svn.example.com/mysvn/wordpress/tags/$wpver/ .
I haven’t figured out how to set up svn so that the bulk of the wordpress files can come from the public svn while still maintaining my own svn of the local customizations
Right now I’m exporting the public wp svn into a folder structure and manually updating the core files in my own svn, then checking those files into my own svn, this works but introduces the potential for a screw up or two.
Thanks for the greats script
Pingback: Hosting multiple blogs on a single WordPress installation » Paul Maunders | Web log
Dear Scot,
I was trying to install “WP-Create” and WP-mass Install.
But I don’t know how to start .. Its a just a text file. Its it a server side script ?
Can you help me how to proceed.
Thanks and Regards
Ranga
rangaprasadmutyala@yahoo.co.in
Ranga – Yes, it’s a bash shell script. It assumes a pre-existing knowledge of working with shell scripts. But basically just put in a directory along with root’s other scripts, chmod 700, and run it:
/path/to/wp-create.sh
nice script! do you have any plans to automate symlink-based WP installs/upgrades? i run a few high-traffic blogs which had always been competing with each other for APC (inode-to-opcode cache) space: symlink-sharing their WP installs got rid of this redundancy.
Thanks Chris. No, I don’t have plans to do that particular modification. If you do, let me know and I’ll incorporate it if it plays well with the standard setup.
Is this valid with WP’s latest versions also?
Hi Lee – This is a shell script that runs outside of WP. It is ignorant of WP itself and thus it is not possible for it to have a version incompatibility.
sweet… like to be cautious and not get in over my head technical skill-level. 🙂
Hi
Great work, found this as I was about to (painfully) try and write a script to that effect. Apparently though, I get a syntax error when trying to run it on a standard (CentOS) dedicated Linux server: After all the input infos are entered, the script outputs
“./WP-create.sh: line 52: syntax error near unexpected token `newline'”
Did I do something wrong on installing it ?
Thank you !
Dennis – You’ll want to comment out either of line 50 or 51. If your system is not cPanel, you probably want to comment out line 51 (still I’m surprised you’re getting that error…)
Also try and “show invisibles” in your text editor to make sure you haven’t introduced some kind of hidden character after a line somewhere.
Thanks for the quick and efficient reply, I managed to make it run by changing those lines as I am indeed not using CPanel. I will now try to extend the script by appending the correct Virtual Host value and restart Apache: as I have a wildcard DNS thingy, this should make an instant functional WordPress install.
You have an interesting blog by the way !
Kudos for sharing such nice scripts.
Hi,
When i run the script i get error
wpinstall.sh: line 64: svn: command not found
Any reason why
Thanks
Johan
Hi,
Also if i have got fantastico installation will i be able to do a mass update on those as well by including them in the list without doing a fresh install.
(i have +- 120 wp installations and getting tired of doing upgrades one by one so this will work perfectly for me)
Thanks
Johan
Johan – ” svn: command not found” means, of course, that you don’t have svn installed. Obviously you’ll need to install subversion if you want to use a tool that wp-create that’s all about managing WP via subversion.
As for the fantastico problem… I’m very familiar with that one 🙁 Your goal here is to take control of managing upgrades out of your user’s hands and put it in your own hands. And unfortunately that means a few things. 1) You need to disable WordPress in Fantastico so people are no longer able to use it, and 2) You need to convert all of those old non-subversion installations into subversion installations. I don’t have a script for that but I did write most of the Codex page covering the process — the last section of http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion . So yes, that initial process will be painful, but once you have all installations converted, the upgrade path server-wide becomes seamless and effortless. Worth putting the work in up front.
how bout a new features: auto fill for latest wp version, and auto generate db user & passwd, secret key and table prefix.
imho, no one need to know any of these. if anyone want to know, just read the generated config file.
Denny – wpcreate already does generate the key for you. The rest are good suggestions. I’m in the middle of another project for a while but will definitely do these for the next revision. Patches welcome.
Hi Shacker,
I am interested with the new features that Denny suggested. Hope we can have the next version soon. Thanks.
Hi everyone – I’m happy to announce a new version of wp-create and wp-mass-upgrade, including automatic backup of each database in the array and a new plugin finding tool. The tools have been folded into a single kit:
WordPress Mass Management Tools