Gaah!

Posted on By admin 7 Comments on Gaah!

I hate wasting my time like this…

I've been writing a lot of code on my laptop, which works perfectly. I must now merge this code on our dev server. Of course, the dev environment doesn't match the environment in which I've been slamming away. I know the environment on my laptop is sane, stable and well configured. I can't say the same for the dev env.

I've just spent the last 2 days trying to find out why the code I know works on my laptop explodes quite dramatically on the dev machine. So what do I do? I install the dev env on my laptop (basically, the Java Web Services development platform), which runs on Tomcat 5. Through hours of tedious testing, I fix bug after bug and setup everything properly.

I've just found out why the last thing wasn't working. The TLD parser of the input taglib was throwing a fit on initialization. In a nutshell, input1.0 – which works fine in Tomcat 4 – doesn't parse under Tomcat 5. Input-1.1 works hunky-dory.

Too bad it only took me the better part of a day to figure that one out.

Sheeeeeet.

uncategorized

Comments (7) on “Gaah!”

  4. Ok, I'm guessing that Rowdy is a server at UofT, and it's acting naughty? Can you clarify f'n mess? And if there's anything specific you need help on, I'll do my best to be of service :)

    I spend my waking hours playing in Java or PHP and MySql :)

    (http://livejournal.com/users/talisker)

  5. Hah. No, Rowdy is my website (www.rowdymedia.com), presently hosted at http://www.robotskull.com, and soon to be hosted … elsewhere. The UofT eng. groups agreed to add a functional MySql databased catalogue with PHP frontend to the site, which, unfortunately, got caught in some grinders and mistiming, and now it's up to me to do it. So. I'm just beginning to learn how to build effective small relational databases and then add PHP frontend manipulators to them so that I don't ever have to directly modify the DB once it's written. I think I have a pretty solid DB design on paper, and am just now beginning to implement it.
    I still have no clue how to properly use MySql Dump once my DB is successfully built and dataentered locally, and am presently dicking with my local copy of my site to find out why, exactly, it works live but not local (and am blaming Mozilla).

    Whew. That was a lot of stuff. I mostly just wanted to check if it was OK if I ask you questions, which I will try to phrase absolutely clearly. Oh. And in the tradition of ThinkGeek, I promise not to ask you to fix my computer. ;)

    (http://livejournal.com/users/pretentiousgit)

  6. teehee!

    I still have no clue how to properly use MySql Dump once my DB is successfully built and data entered locally

    mysqldump is fairly straightforward:

    mysqldump -u USERNAME -p -a DATABASE > data.sql

    -a: all db creation info (will add create table statements)
    -u: username (replace USERNAME by the user allowed to connect to the db)
    -p: will prompt for password

    replace DATABASE by the name of your database

    And then you can the data.sql file to load into mysql on the host you'll be using for your server.

    For your PHP coding, I seriously recommend you look into phplib (http://phplib.sourceforge.net/index.php3) and I can give you a hand to set it up, and provide some code examples, if you want. It's uber straightforward.

    For anything else, don't hesitate to ask. I'll do my best to answer, or provide avenues where you can find answers if I'm too busy to do it myself ;)

    (http://livejournal.com/users/talisker)

Comments are closed.