Well, that only took 29 days, but my blog has returned to the living!

At some point this week, this blog is finally making the migration to my web server, as my shared hosting expires early next week. Nothing like procrastination to help things get done early.

If the blog goes down, or stays down, then you know what happened.

Currently, my clientele consists of a very small site that someone paid me for, and a handful of personal projects.

I’m not really making enough money at this point to justify having 2 servers, but suddenly a backup seems quite nice. My web uptime the last 3 weeks has been something like 0.00001%, which has totally destroyed any sense of productivity.

I set up my entire workflow based on having access to my server that is as of now mostly useless. For example, my subversion repository is inaccessible, which throws a huge wrench in my source-coding. All of my current projects (including the one that might make me any money) demos are all down.

full time job + life crap = not getting the chance to take care of this stuff quickly

which could wind up costing me the one project with potential income

which means I can’t afford a backup server…

My main web server is still hosed. I managed to completely screw up the open directory config, and have 0 remote access to anything. And the web service is down.

Plan A* is to have my buddy attempt to re-create the open directory structure.

Plan *B is to have the server shipped to me so I can reinstall the OS

Plan C*, which is completely independent of the other two plans, is to kick myself in the ass for not taking the time to more throughly troubleshoot when I was *STANDING NEXT TO THE SERVER last week. Can I was only in town for 3 days be my excuse? I hope so, because that’s all I’ve got.

Just a short post to let everyone know that I’m still alive. My main web server has been down for a while, and I’ve had a full plate of personal crap to deal with. Posting from a rest area in West Texas, headed back to AZ after seeing my folks this weekend. Pics and details later/on my twitter.

I’ve updated the live WeeMap with the numerous minor changes in the last few days.

• Corrected email subjects
• User info bar (with username and logout link)
• Login redirects to Maps instead of Home
• Various tweaks

The BIGGEST change in this release is the addition of tag based filtering/searching.

And with that, I’m off to bed. Be sure to check back here or the lighthouse for support/feedback.

Oh, and I’ve created a topic on the WeeWar Tangler Group for the app as well. Trying to keep everyone up to date.

My simple little WeeWar maps app is live!

Check it out: WeeMap

DNS might still be updating, so check back if it’s down for you.

Man, I am getting warmed up to Leopard Server quick. Although I don’t think I’ll be replacing Simplelog just yet, the ability to use 3rd party apps to interface with the built-in blog system makes it that much more attractive.

To access your blog, use an applicatioin that works with the Metaweblog API. Use the following information to configure the editor:

RPC Access Point: http://serverDNSname/RPC2
Username or Blog ID: Your user name or the name of your group

I know I’ve posted about Ecto before, but I just wanted to say that I’m pretty happy with the direction it’s going. I’ve started using it again since the v3 beta, and haven’t been disappointed.

As expected, I received a ‘you’re not important, so we’re not updating our system gems’ message from GoDaddy.

While this sucks, I’ve resorted to plan ‘b’ ship my mini, Hobbes, out to be colocated a little earlier than planned.

I don’t plan on renewing my hosting contract with GoDaddy, and I haven’t since I bought the mini, so I’m not really that upset by their response. The biggest disappointment is not being able to publish my lil weemap app.

WeeWar custom map makers and players will just have to wait a little longer. Hobbes should be online in a week or so.

Ok. I’ve re-uploaded the gems. Still nothing. I switched over to development mode and CGI instead of fastCGI and finally started seeing error messages. Turns out GoDaddy is running old system GEMs, and needs to update.

The biggest problem here is that I’ve frozen my rails version to my app’s vendor/ directory. There should be nothing else (core Rails wise) that is needed to run my app. I’m not using any non-standard gems, and my plugins are all in the app itself.

For more details on the exact issue I’ve run up against, see this ticket

This ticket has been listed as ‘invalid’. Such a shame that the core developers disregard those of us who eek out a meager existence on shared servers.

Mostly for my benefit later, but maybe helpful to you other rails newbs: I always seem to not be able to find this quickly when I want to freeze mah gems. It isn’t that hard, I’m just that absent minded.

rake rails:freeze:edge TAG=rel_2-0-2

rake rails:update:configs

script/about

Most of this was stolen directly from the Readme

Since I stole everything else, I figured I’d duplicate the donation link as well.

If you find this plugin useful, please consider a donation to the author to show your support!

Author’s Email: jonathan.viney@gmail.com

Installation

ruby script/plugin install
http://svn.viney.net.nz/things/rails/plugins/acts_as_taggable_on_steroids

ruby script/generate acts_as_taggable_migration
rake db:migrate

more

One step closer to getting my server up to production!

After several mis-steps, I’ve finally configured subversion in leopard server, and have mostly gotten Warehouse running.

I can’t wait to migrate all of my sites over to the server and get it live!

What kind of how-to would this be if I just sat around cooing about my own accomplishments? After all, I just stole the work from other people. And here it is:

Subversion

This page was instrumental in getting subversion up and running properly. A lot of other pages helped/got me started, but in the end I just wiped all of that other crap, and started over from the top of this page. When I finished, Subversion worked. That simple.

One gotcha, noted in the comments, is that for some reason OS X Server Admin seems to be fond of changing the line DAV svn to DAV off. Some vigilance in TextMate prevented this from bringing me down!

I’ll be posting more specifics about my Warehouse experience as soon as it’s actually working ;)

So, apparently I’m that guy that has comments on his blog, but never checks them, much less replies. Well NO MORE. I’ve finally added my own comment feed to my feed reader, so I can be less of a jackass and more responsive. If you’ve left any comments before, I apologize for my ignorance and thank you for the feedback.

Thanks to John Siracusa for pointing me to Fancy Zoom

This seems to be similar to the javascript image library I’ve already set up, possibly better.

Continuing the saga started here, I now have a legitimate business need to get image uploading working. (Before, I was just screwing around.) I am running into a different problem.

To make matters worse, I some how managed to screw up my svn repository for my previous attempt, and lost enough of the app structure that what’s left is useless.

I’ll be updating this post with things that I (re)discover along the way. First off, for a detailed description (including code, this time) of the problem I’m having, see this post at RailsForum.

more

There’s a good how-to over at the RoR Wiki but I’m going to repost a quick & dirty reference here, mostly for my own benefit the next time I go through this.

The point is to ignore sensitive info in the database.yml file, and the ever-changing log & tmp directories. I’m no SVN guru, so feel free to point out flaws in this system.

more

My latest rails project involves uploading images, and having them automagically thumbnailed. So far, it isn’t looking so good.

Upload

Google pointed me at the attachment_fu plugin and a how-to by Mike Clark. Attachment Fu was a pretty simple install/config. Now I can upload images.

This is where the fun ends.

more

I spent most of this evening screwing around with iPhoto, going through some of my older pictures & editing/arranging them. Feeling rather adventurous, I started playing around with iWeb & dotMac. When I posted the pictures from last week’s road trip, I had my first experience with the new galleries, today I decided to play with iWeb’s photo pages.

I’ve fiddled with iWeb before, and to be quite honest, I find it very simplistic-both in use and capability. I’ve always preferred hand-coding my web sites, but the integration between the iLife programs makes them very easy to use for those “less technically snobbish” than I.

So, without further ado, I give you my iWeb site.

Ok, so I’ve gone live with my first simplelog theme. This theme is, obviously, inspired directly by my new site layout.

I alread know that I’m not 100% satisfied, but seeing it in use should focus my attention better.

Nothing to See Here

Just claiming my blog. Technorati Profile

Stolen from here, mostly because its a publicly editable wiki. I had to edit the page and revert a bunch of spammed changes to find anything useful!

Setting up Ecto

1. If you get the account creation wizard the first time you run ecto, just click cancel and dismiss the following error.
2. Click “Add” in the Account Manager.
3. Enter your site’s URL when prompted. Example: http://myweblog.com
4. ecto will attempt to get information about your weblog, but you’ll need to clarify a few things when it’s done as such
   System Other (select API)
   API Movable Type
5. The Access Point should be the same thing as your URL, but add /xmlrpc/api. Example: http://myweblog.com/xmlrpc/api
6. Click ‘Next’ and then enter your username and password (the same info you use to log in to the SimpleLog admin section).
7. Enter anything for the Profile Name. ecto will get your blog information and then ask you a few questions. UNCHECK ALL BOXES and click ‘Next’. Click ‘Finish’ and ecto will get all of your entries.

If you are asked which mode you want to edit in by default, you should choose HTML. You can also set this via the Preferences.

You can now edit, delete and post from ecto!

more

I’ll be using the space to put up info about how to abuse your phone, as well as maintaining a small repository of installer.app packages.

I’ll probably be reposting/moving my existing tutorials there, as well as adding a few new ones as new shits are added.

Registered a couple new domains in the last day or so, including feedthedroo.com, for my lil bro & bowermandeliveryservice.com,
my dad’s business.

Who knows, I might actually get my monies worth out of this hosting account after all!

Still having random Application failed to load properly errors. A refresh seems to fix it, but doesn’t give me a warm-fuzzy…

Also, I’m trying to install Beast Forums, and I’m having tons of issues with Godaddy’s DB admin page. Luckilly, it only seems to be affecting new databases.

Continued from Part 1

The Godaddy Config (Step 3)

I created a database & user for the SimpleLog program, and FTP’d the program to a subfolder of my hosting root.

At this point, http://bustikated.net/mysimplelogdir/ was giving me Permission Denied errors & http://bustikated.net/mysimplelogdir/public/ was giving me Bad Request errors.

Using the phpMyAdmin db management on Godaddy’s server, I was able to modify the domain preference in the simplelog db. Trial and error later revealed that /public/ had to be present @ the end of the url, for now I just left it blank.

Also, I had to get the IP address of the server from phpMyAdmin (I couldn’t find a server name).

All of this fixed nothing

more

Nothing to see here; just making sure all this crap works from my phone.

more

It almost killed me, but I got this bustikated ass blogging system installed. I’ve been up all nite screwing with the site in one form or another. Now that I’ve gotten this up and running, screw it. I’m going to bed.

I documented the arduous process of installing SimpleLog under Godaddy’s shared hosting. When I’ve regained the status “alive” I’ll post it here.