If you access/store your repositories on Samba shares, but development is done on Windows machines, it can be a headache trying to update your SVN checkout using the Windows cmd. Most of my updates (using Tortoise SVN) are done through the context menus in Windows because of this. I have grown tired of updating each checkout manually, so I wanted to make a batch file that would do it for me. Yay for being lazy, right?
Basically, we’re telling the local SVN client directly how to make the update request…
c:
cd "C:\Program Files\TortoiseSVN\bin\"
TortoiseProc.exe /command:update /path:"z:\client_site1\" /closeonend:2
TortoiseProc.exe /command:update /path:"z:\client_site2\" /closeonend:2
TortoiseProc.exe /command:update /path"z:\client_site3\" /closeonend:2
TortoiseProc.exe /command:update /path:"z:\client_site4\" /closeonend:2
TortoiseProc.exe /command:update /path:"z:\client_site5\" /closeonend:2
TortoiseProc.exe /command:update /path"m:\sandboxes\client_site1\" /closeonend:2
TortoiseProc.exe /command:update /path:"m:\sandboxes\client_site2\" /closeonend:2
exit
So, TortoiseProc.exe needs to run the update command, on the path specified. I don’t [usually] care much if files are updated or added, so I have set the closeonend flag to level 2, which will only close the SVN console window if there are no conflicts.
You’ll want to change the path, obviously, and if desired, the closeonend integer.
Leave comments. Cheers!
This is a really quick post. I’ve listened to Ben’s latest edition of The Feeling of Trance AT LEAST 20 times this week. I LOVE IT. Great picks by Ben.
Ben Hunt’s The Feeling of Trance 48
For those of you who have smelly shoes, you’ll find this post useful. I have a pair of Vibram Five Finger shoes that I LOVE MORE THAN ANY SHOE EVER, but they get foul once in a while. There are a lot of expensive ways to remedy smelly shoes, but the number one way on my list is with a white vinegar bath.
Vinegar is amazing when it comes to cleaning and, or killing odors. Burn a pizza and smoke up the apartment? Vinegar. Have stone tile and don’t want to ruin the new seal you just had put on? Vinegar. Have funky-corn-chip-smelling feet and want your shoes to smell better? VINEGAR!
- Mix a solution consisting of 25% white vinegar, 75% distilled water
- Let them soak for a minimum of 4 hours; overnight is better, but it depends on the stank : )
- Take them out of the solution and let them dry in the sun if possible.
If the weather is crap, then dry them by hanging them from a line, or standing them up, heel down.
DO NOT USE HEAT! (the sun’s heat is fine, but nothing else!)
- After they dry toss them in the washing machine with very little, or no detergent.
This should get the vinegar smell out.
- Repeat your drying process, and you’re ready for the next round of use.
NOTE: You’re not required to use distilled water, but some cities have a higher amount of purifying chemicals that may react weird with the vinegar, or have a bleaching effect all on it’s own. You make the call.
Ever go to update WordPress and received this error?
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2516357 bytes) in /home/edm/public_html/wp-includes/http.php on line 1363
That’s because the php.ini is setup to only allocate so much memory to script execution. In this case, my .ini file was set to only allocate 32MB; hence 33554432… 33554432 byte = 32 megabytes. We only need another ~2.5MB to run the script (according to the error) but I think it’s better to be safe than sorry and aim high so you don’t have to dick with it again. You can change this at runtime, or in the php.ini file. Here’s how to do both…
Change at runtime:
- Go to the file listed in the error message (in this case, http.php)
- At the top of the file inside the opening PHP tag (say, line 2) paste the following snippet
- ini_set(“memory_limit”, “64MB”);
- substitute 64 for whatever you want, within reason
- Save the file and re-run the updater/script
Change in php.ini (my preferred method)
- Locate the php.ini file
- if you don’t know where it is, or don’t have access to it contact your host
- Inside the file, do a find on “memory_limit”
- mine was line 232, default value of 32MB…
- Replace the old value [32MB] with your value of choice… I chose 128
- you can go as high as you want…
- IMHO, not more than 128MB should be needed for a WP… you’d have to have some thing rendering images/pdf’s or something to need more
- Save the file and re-run the updater/script
If you change this in the .ini file, you *shouldn’t* run into this when you update next time. If you’re using the runtime method, you’ll probably need to make this change each time you update. Basically, if you have the option, just bump it up in the .ini file. It will save you a grumble and 30 seconds the next time you go to update WordPress. If you don’t have the option of updating the .ini file, you’re stuck with changing it at runtime. If you get sick of editing http.php every update, talk to your host about updating/locating the .ini file.
As always, comments and questions are welcome!
