Since the AppEngine path changes from myserver.appspot.com to
myserver.mydomain.com, you will need to hand-edit a configuration file to
get this to work.
Within the ODK Aggregate directory that the installer produces, you will
find this file:
This is a Java jar file containing configuration files that were tailored
based upon the answers you provided to the installer.
A tool like 7-ZIP can open this file, and within it, you will find a
'security.properties' file. You will need to Edit this file.
Within that file, you will find a line:
Change this to myserver.mydomain.com or whatever is appropriate for you.
Save the changes, being sure that they are updated in this jar file (7-Zip
handles this for you; other tools, you must be very careful that the file
in the jar gets replaced/updated).
You should now be able to deploy to appspot and have the server behave as
if it is running on your custom domain.
I have no idea how doing this can/will work with https: connections (ODK
Aggregate when deployed on AppEngine, has all communications sent over
You may be required to purchase your own SSL certificate, and I don't know
what additional steps would be required to configure your appspot
deployment to use that certificate.
That would be a separate issue to address with Google.
If there are additional steps, I would appreciate it if you could document
those steps for the wider community.
On Thu, Aug 2, 2012 at 12:52 AM, Bashir Jahed wrote:
Been using ODK for a bit of time now in testing. I have got it up and
running on app engine using the standard domain name @appspot.com but
when i try nad direct the app to a custom domain the it breaks, looks like
the style sheets are not locatable and the initial redirect does not work
Any ideas on this, before i re-install it could it be that i need to
create the war file using the intended url when running the .bin file to
create the war?
University of Washington