WeeWar Map App v0.01
Posted by BM5k on March 17, 2008 at 12:00 AM
I’ve thrown together a lil rails app for providing feedback on WeeWar maps.
I’ll be honest, right now it isn’t that great. But I’m still working on it. Besides, it’s my very first published rails app. Hell, it’s my first published web app in a LONG time.
Which is your favorite WeeMap?
Due to the instability of the app, I’ve decided to release as private beta, you’ll need a key to join. Also, the app requires your weewar api key. The way it works is you provide your weewar login and api key to guarantee that you have the same name here as in weewar. It’s just better that way.
Let me say it again, yes this is a VERY early release. Yes there are several features that I want to add or fix. If you have constructive criticism or bugs, please leave comments. I hope to have a better method of leaving feedback up shortly (looking into lighthouse for tickets, and beast for a forum)
I’m not responsible for anything other than amusement that comes out of this app!!!
Oh, and the only way to get an invite is to ask ;)
Comments
There are 6 comments on this post. Post yours →
If you’ve tried to access the app (and you can get there because the DNS is still new) you might have noticed that something isn’t quite right.
It appears that godaddy doesn’t support rails 2.0, which my app was written in. Not 100% sure if this is the problem yet, but the absence of an production log in the /log directory leads me to believe that the server isn’t ever starting.
I’ll look into this more after work.
Ok. Froze the Rails 2.0.2 gems. Apparently I also suck at Apache Mod Rewrite, because it still isn’t quite right.
Faced with the choice of physically moving the files or figuring out Apache Config, I’ve moved the files. It will take a while for the virtual domain to re-configure.
Shrug so much for a quick and easy release.
Ok, so still no joy from the web server. Not 100% sure why, the only error I’m getting is a timeout from my browser. Nothing in godaddy’s error log, nothing in my application’s log/. It appears that the server isn’t starting.
When I try to run in production mode from my dev machine, I get a DB failure trying to connect to godaddy’s mysql box. At least this still shows up in a log file.
Not really sure what to do. Been comparing the config with several of my other apps that seem to be running fine, and I can’t find the issue.
I can’t wait until I get my server live :( hopefully shit like this won’t happen.
I need all the help I can get so if it does get sorted out, I’ll ask!
Things are on hold until Wed, when I’ll have the time to straighten this mess out!
Just got off the phone with Godaddy support. Apparently everything on their end is working. My mysql/cgi/webserver is all good. Which means it’s just my app that’s hosed.
The rep suggested refreezing and uploading all of the gems. This is gunna take a while. I hope it works!
Post a comment
Required fields in bold.