Copasetic Flow

Let's say you have a deployed Google App Engine application you've been using for years like the ham radio practice exams we're updating here. You decide to output data the app is obviously using all the time. For us, it was the table of help topic links for each exam question. You think you're going to output the data easily, and then: NeedIndexError: no matching index found. recommended index is and nothing. This happened here today, (obviously right?) I had to walk through a series of documentation steps and log messages, but the answer in the end was simple. First, the message above doesn't turn up in your app, it turn up in your log message explorer. For us, that's at  https://console.cloud.google.com/logs/query;cursorTimestamp=2023-07-03T15:57:44.595552Z?project=hamdaise Next, that's where you'll find an actually very handy error message with this at the bottom (your data model will be different unless you forked the ham radio exam repo .) That...

Back in January, I started to simplify the free ham radio practice exams so they'd be easier for the gang—two of whom are learning to program—and I to update in the future. It. Was. Hard. I fought and fought and finally located the Google App Engine debug console where I could change a file at a time, (and actually see a listing of files.) That console has since been deprecated and dropped, (unbeknownst to me.) Consequently, when 12 year-old Daize and I tried to add a simple fix to a misformatted question this morning… Nope! Oh well. I went through the 7 stages of grieving, but really fast this time, and then went to look for Google App Engine deployment too for Python . Fortunately, it still exists! Now it’s called the Google Cloud CLI . Installation was actually straightforward, and since I stored the entire applciation in github including the app.yaml file, deployment was pretty easy as well. We're back up and running! Refererces Free ham radio exam practice app

I've been porting the ham radio practice exams to facebook lately. The process for this wasn't entirely obvious to me and there were quite a few issues. This series of posts will try to make the process more obvious and highlight the issues I hit so you can avoid them. For now, I'll just point you at a list of the posts that will slowly flush out and my list of stumbleupon bookmarks I accumulated while doing research for the project. Table of Contents Facebook on Google App Engine Resources

I've been working on an applciation utilizing Google's App Engine. The fist version of my application sent about 500 bytes of information along with each user POST request. The second version up this to around 100 bytes and the App Engine server started giving the error: Requested URI too long: ... HTTP/1.1" 414 – This is the http error returned when a post request is longer than the server is configured to accept. After a little research I found this excellent article: http://www.openjs.com/articles/ajax_xmlhttp_using_post.php that solved my problem. The short version of the article is: Don’t send the post parameters as part of the url, send them using the XMLHTTP object’s send method once the object has been opened using only the address, (everything before the ?), of the original post url. So, the original code that looked like: var my_url = "/myhandler?longstring=" + ...

Table of Contents Introduction Setup Authentication Flow Inviting Friends Appendix A: StumbleUpon Bookmarks