Thanks to help from @bobwyman and @termie I have a pretty thorough walkthrough on setting up your own Jaiku Engine instance. I'd appreciate it if people could try it out and let me know if it worked for them. I've also attached my app.yaml and settings.py so that you can see what I had at the end of the process.
======Walkthrough================= Walkthrough: replace exampleku and exampleku.appspot with your Jaiku Engine instance's name ########################################################################### ###################
Set up the new application via the AppEngine dashboard here: http://appengine.google.com/start In my case I'm setting up an instance called Exampleku at http://exampleku.appspot.com svn checkout http://jaikuengine.googlecode.com/svn/trunk/ jaikuengine Open app.yaml and change the first line to the name of your application. In this case: exampleku Open settings.py and change the following: Add your name and a valid email address to the list of ADMINS on lines 26-28 Change the SECRET_KEY on line 61 to something secure. I recommend a good passphrase. Not "I am so secret" This will be used for API authentication so it's important that it's kept secure. Checking it into your public Github repository would be a bad idea. On line 132 change the SITE_NAME. I'm using "Exampleku" On line 133 change the default support channel. I prefer to call it after the site so I've renamed it from "support" to "exampleku" Every JaikuEngine installation has a special user who is automatically added to every other user's contact list and is used to provide access for unauthenticated users. On line 136 you should define that user for your site. The name you choose will get concatenated onto your appspot domain. In my case I'm choosing "exampleku" Note that I did not use an email address. Just the user's name. This user doesn't exist yet and we will have to create it later. On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com On line 150 change your HOSTED_DOMAIN to appspot.com This says that you're not planning to deploy the site to your own domain like jaiku.com or somemicrobloggingsite.com but will instead by hosting on one of the *.appspot.com sub-domains. On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This will later be concatenated with your HOSTED_DOMAIN to give your site's address. On line 155 change your NSDOMAIN to exampleku.appspot.com or the equivalent for your site's address. On line 225 change API_DISABLE_VERIFICATION to True. This is a temporary removal of all security so that you can set up your default user who will authorise all later users. On line 304 switch off the support for using queuing to handle large numbers of users unless you want to set up a cron somewhere to trigger the background processing. You switch off the queuing by setting QUEUE_ENABLED = False Replace lines 366 to 370 with the following: def default_email_sender(): return 'your_em...@domain.com' Then replace the string 'your_em...@domain.com' with your actual email address or whatever email address you want all emails from your Jaiku Engine instance to look like they're sent from. Given that if your instance gets popular you'll be sending quite a lot of email (and possibly receiving replies) I recommend that you don't use your personal email address. You should probably use an email address that's named after your site. In this case "exampleku". Make sure it's a real email address or it will be rejected as an unauthorised sender. Then run the following commands cd jaikuengine make clean make zip_all && python manage.py update Now look at http://exampleku.appspot.com but do NOT sign up for an account yet. Everything should work except: http://exampleku.appspot.com/channel At this point you have a working application but not enough data for it to be useful. Now go to: http://appengine.google.com/dashboard?&app_id=exampleku This is your JaikuEngine instance's dashboard. Click on the Data Viewer in the left-hand navbar. It should be empty because you don't have any data in your database. Now go to: http://exampleku.appspot.com/join and create a user with a screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this should work rather than fall over when it tries to authorise the sending of email. Make sure this user is set up with a real email address as it will send you a confirmation email. Click on the confirmation email and finish setting up the exampleku user. Now look at http://exampleku.appspot.com/explore It should have an auto-generated post from your exampleku user saying that they've joined.
Now go to settings.py and change line 225 to say API_DISABLE_VERIFICATION = False Then redeploy with following commands: make clean make zip_all && python manage.py update
Your JaikuEngine instance should now be ready for end-users. Enjoy.
Hi Adewale, thanks for the howto. Maybe someone got some hint for me.
It should be ok to simply use the deploy command in the
GoogleAppEngineLauncher instead of:
cd jaikuengine
make clean
make zip_all && python manage.py update
I guess the make command is probably not standard on a mac. However my
page installation keeps white at inundumuns.appspot.com. At least the
favicon seems to be ready - lol!
On Mar 16, 1:31 am, Adewale Oshineye <adew...@gmail.com> wrote:
> Thanks to help from @bobwyman and @termie I have a pretty thorough
> walkthrough on setting up your own Jaiku Engine instance. I'd
> appreciate it if people could try it out and let me know if it worked
> for them. I've also attached my app.yaml and settings.py so that you
> can see what I had at the end of the process.
> ======Walkthrough=================
> Walkthrough: replace exampleku and exampleku.appspot with your Jaiku
> Engine instance's name
> ########################################################################### ###################
> Set up the new application via the AppEngine dashboard here:http://appengine.google.com/startIn my case I'm setting up an
> instance called Exampleku athttp://exampleku.appspot.com > svn checkouthttp://jaikuengine.googlecode.com/svn/trunk/jaikuengine > Open app.yaml and change the first line to the name of your
> application. In this case: exampleku
> Open settings.py and change the following:
> Add your name and a valid email address to the list of ADMINS on lines 26-28
> Change the SECRET_KEY on line 61 to something secure. I recommend a
> good passphrase. Not "I am so secret" This will be used for API
> authentication so it's important that it's kept secure. Checking it
> into your public Github repository would be a bad idea.
> On line 132 change the SITE_NAME. I'm using "Exampleku"
> On line 133 change the default support channel. I prefer to call it
> after the site so I've renamed it from "support" to "exampleku"
> Every JaikuEngine installation has a special user who is
> automatically added to every other user's contact list and is used to
> provide access for unauthenticated users. On line 136 you should
> define that user for your site. The name you choose will get
> concatenated onto your appspot domain. In my case I'm choosing
> "exampleku" Note that I did not use an email address. Just the user's
> name. This user doesn't exist yet and we will have to create it later.
> On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com
> On line 150 change your HOSTED_DOMAIN to appspot.com This says that
> you're not planning to deploy the site to your own domain like
> jaiku.com or somemicrobloggingsite.com but will instead by hosting on
> one of the *.appspot.com sub-domains.
> On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This
> will later be concatenated with your HOSTED_DOMAIN to give your site's
> address.
> On line 155 change your NSDOMAIN to exampleku.appspot.com or the
> equivalent for your site's address.
> On line 225 change API_DISABLE_VERIFICATION to True. This is a
> temporary removal of all security so that you can set up your default
> user who will authorise all later users.
> On line 304 switch off the support for using queuing to handle large
> numbers of users unless you want to set up a cron somewhere to trigger
> the background processing. You switch off the queuing by setting
> QUEUE_ENABLED = False
> Replace lines 366 to 370 with the following:
> def default_email_sender():
> return 'your_em...@domain.com'
> Then replace the string 'your_em...@domain.com' with your actual
> email address or whatever email address you want all emails from your
> Jaiku Engine instance to look like they're sent from. Given that if
> your instance gets popular you'll be sending quite a lot of email (and
> possibly receiving replies) I recommend that you don't use your
> personal email address. You should probably use an email address
> that's named after your site. In this case "exampleku". Make sure it's
> a real email address or it will be rejected as an unauthorised sender.
> Then run the following commands
> cd jaikuengine
> make clean
> make zip_all && python manage.py update
> Now look athttp://exampleku.appspot.combut do NOT sign up for an
> account yet. Everything should work except:http://exampleku.appspot.com/channel > At this point you have a working application but not enough data for
> it to be useful.
> Now go to:http://appengine.google.com/dashboard?&app_id=exampleku > This is your JaikuEngine instance's dashboard.
> Click on the Data Viewer in the left-hand navbar. It should be empty
> because you don't have any data in your database.
> Now go to:http://exampleku.appspot.com/joinand create a user with a
> screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this
> should work rather than fall over when it tries to authorise the
> sending of email. Make sure this user is set up with a real email
> address as it will send you a confirmation email. Click on the
> confirmation email and finish setting up the exampleku user.
> Now look athttp://exampleku.appspot.com/exploreIt should have an
> auto-generated post from your exampleku user saying that they've
> joined.
> Now go to settings.py and change line 225 to say
> API_DISABLE_VERIFICATION = False
> Then redeploy with following commands:
> make clean
> make zip_all && python manage.py update
> Your JaikuEngine instance should now be ready for end-users. Enjoy.
I had the same probably and then switched to an Ubuntu machine. If you
look at the logs via the AppEngine Dashboard:
http://appengine.google.com/ you should be able to see the exception.
JE needs various folders to be zipped up in order for them to be
deployed. The OSX GUI launcher tool doesn't seem to support this. You
can either install something like DarwinPorts in order to be able to
install make or replicate the functionalty of Make. In this case that
means:
> Hi Adewale, thanks for the howto. Maybe someone got some hint for me.
> It should be ok to simply use the deploy command in the
> GoogleAppEngineLauncher instead of:
> cd jaikuengine
> make clean
> make zip_all && python manage.py update
> I guess the make command is probably not standard on a mac. However my
> page installation keeps white at inundumuns.appspot.com. At least the
> favicon seems to be ready - lol!
> On Mar 16, 1:31 am, Adewale Oshineye <adew...@gmail.com> wrote:
>> Thanks to help from @bobwyman and @termie I have a pretty thorough
>> walkthrough on setting up your own Jaiku Engine instance. I'd
>> appreciate it if people could try it out and let me know if it worked
>> for them. I've also attached my app.yaml and settings.py so that you
>> can see what I had at the end of the process.
>> ======Walkthrough=================
>> Walkthrough: replace exampleku and exampleku.appspot with your Jaiku
>> Engine instance's name
>> ########################################################################### ###################
>> Set up the new application via the AppEngine dashboard here:http://appengine.google.com/startIn my case I'm setting up an
>> instance called Exampleku athttp://exampleku.appspot.com >> svn checkouthttp://jaikuengine.googlecode.com/svn/trunk/jaikuengine >> Open app.yaml and change the first line to the name of your
>> application. In this case: exampleku
>> Open settings.py and change the following:
>> Add your name and a valid email address to the list of ADMINS on lines 26-28
>> Change the SECRET_KEY on line 61 to something secure. I recommend a
>> good passphrase. Not "I am so secret" This will be used for API
>> authentication so it's important that it's kept secure. Checking it
>> into your public Github repository would be a bad idea.
>> On line 132 change the SITE_NAME. I'm using "Exampleku"
>> On line 133 change the default support channel. I prefer to call it
>> after the site so I've renamed it from "support" to "exampleku"
>> Every JaikuEngine installation has a special user who is
>> automatically added to every other user's contact list and is used to
>> provide access for unauthenticated users. On line 136 you should
>> define that user for your site. The name you choose will get
>> concatenated onto your appspot domain. In my case I'm choosing
>> "exampleku" Note that I did not use an email address. Just the user's
>> name. This user doesn't exist yet and we will have to create it later.
>> On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com
>> On line 150 change your HOSTED_DOMAIN to appspot.com This says that
>> you're not planning to deploy the site to your own domain like
>> jaiku.com or somemicrobloggingsite.com but will instead by hosting on
>> one of the *.appspot.com sub-domains.
>> On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This
>> will later be concatenated with your HOSTED_DOMAIN to give your site's
>> address.
>> On line 155 change your NSDOMAIN to exampleku.appspot.com or the
>> equivalent for your site's address.
>> On line 225 change API_DISABLE_VERIFICATION to True. This is a
>> temporary removal of all security so that you can set up your default
>> user who will authorise all later users.
>> On line 304 switch off the support for using queuing to handle large
>> numbers of users unless you want to set up a cron somewhere to trigger
>> the background processing. You switch off the queuing by setting
>> QUEUE_ENABLED = False
>> Replace lines 366 to 370 with the following:
>> def default_email_sender():
>> return 'your_em...@domain.com'
>> Then replace the string 'your_em...@domain.com' with your actual
>> email address or whatever email address you want all emails from your
>> Jaiku Engine instance to look like they're sent from. Given that if
>> your instance gets popular you'll be sending quite a lot of email (and
>> possibly receiving replies) I recommend that you don't use your
>> personal email address. You should probably use an email address
>> that's named after your site. In this case "exampleku". Make sure it's
>> a real email address or it will be rejected as an unauthorised sender.
>> Then run the following commands
>> cd jaikuengine
>> make clean
>> make zip_all && python manage.py update
>> Now look athttp://exampleku.appspot.combut do NOT sign up for an
>> account yet. Everything should work except:http://exampleku.appspot.com/channel >> At this point you have a working application but not enough data for
>> it to be useful.
>> Now go to:http://appengine.google.com/dashboard?&app_id=exampleku >> This is your JaikuEngine instance's dashboard.
>> Click on the Data Viewer in the left-hand navbar. It should be empty
>> because you don't have any data in your database.
>> Now go to:http://exampleku.appspot.com/joinand create a user with a
>> screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this
>> should work rather than fall over when it tries to authorise the
>> sending of email. Make sure this user is set up with a real email
>> address as it will send you a confirmation email. Click on the
>> confirmation email and finish setting up the exampleku user.
>> Now look athttp://exampleku.appspot.com/exploreIt should have an
>> auto-generated post from your exampleku user saying that they've
>> joined.
>> Now go to settings.py and change line 225 to say
>> API_DISABLE_VERIFICATION = False
>> Then redeploy with following commands:
>> make clean
>> make zip_all && python manage.py update
>> Your JaikuEngine instance should now be ready for end-users. Enjoy.
i don't have a make on windows,
how to deploy in gae launcher to make it work just like
cd jaikuengine
make clean
make zip_all && python manage.py update
On Mar 16, 5:05 pm, Rom <roman9...@googlemail.com> wrote:
> Hi Adewale, thanks for the howto. Maybe someone got some hint for me.
> It should be ok to simply use the deploy command in the
> GoogleAppEngineLauncher instead of:
> cd jaikuengine
> make clean
> make zip_all && python manage.py update
> I guess the make command is probably not standard on a mac. However my
> page installation keeps white at inundumuns.appspot.com. At least the
> favicon seems to be ready - lol!
> On Mar 16, 1:31 am, Adewale Oshineye <adew...@gmail.com> wrote:
> > Thanks to help from @bobwyman and @termie I have a pretty thorough
> > walkthrough on setting up your own Jaiku Engine instance. I'd
> > appreciate it if people could try it out and let me know if it worked
> > for them. I've also attached my app.yaml and settings.py so that you
> > can see what I had at the end of the process.
> > ======Walkthrough=================
> > Walkthrough: replace exampleku and exampleku.appspot with your Jaiku
> > Engine instance's name
> > ########################################################################### ###################
> > Set up the new application via the AppEngine dashboard here:http://appengine.google.com/startInmy case I'm setting up an
> > instance called Exampleku athttp://exampleku.appspot.com > > svn checkouthttp://jaikuengine.googlecode.com/svn/trunk/jaikuengine > > Open app.yaml and change the first line to the name of your
> > application. In this case: exampleku
> > Open settings.py and change the following:
> > Add your name and a valid email address to the list of ADMINS on lines 26-28
> > Change the SECRET_KEY on line 61 to something secure. I recommend a
> > good passphrase. Not "I am so secret" This will be used for API
> > authentication so it's important that it's kept secure. Checking it
> > into your public Github repository would be a bad idea.
> > On line 132 change the SITE_NAME. I'm using "Exampleku"
> > On line 133 change the default support channel. I prefer to call it
> > after the site so I've renamed it from "support" to "exampleku"
> > Every JaikuEngine installation has a special user who is
> > automatically added to every other user's contact list and is used to
> > provide access for unauthenticated users. On line 136 you should
> > define that user for your site. The name you choose will get
> > concatenated onto your appspot domain. In my case I'm choosing
> > "exampleku" Note that I did not use an email address. Just the user's
> > name. This user doesn't exist yet and we will have to create it later.
> > On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com
> > On line 150 change your HOSTED_DOMAIN to appspot.com This says that
> > you're not planning to deploy the site to your own domain like
> > jaiku.com or somemicrobloggingsite.com but will instead by hosting on
> > one of the *.appspot.com sub-domains.
> > On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This
> > will later be concatenated with your HOSTED_DOMAIN to give your site's
> > address.
> > On line 155 change your NSDOMAIN to exampleku.appspot.com or the
> > equivalent for your site's address.
> > On line 225 change API_DISABLE_VERIFICATION to True. This is a
> > temporary removal of all security so that you can set up your default
> > user who will authorise all later users.
> > On line 304 switch off the support for using queuing to handle large
> > numbers of users unless you want to set up a cron somewhere to trigger
> > the background processing. You switch off the queuing by setting
> > QUEUE_ENABLED = False
> > Replace lines 366 to 370 with the following:
> > def default_email_sender():
> > return 'your_em...@domain.com'
> > Then replace the string 'your_em...@domain.com' with your actual
> > email address or whatever email address you want all emails from your
> > Jaiku Engine instance to look like they're sent from. Given that if
> > your instance gets popular you'll be sending quite a lot of email (and
> > possibly receiving replies) I recommend that you don't use your
> > personal email address. You should probably use an email address
> > that's named after your site. In this case "exampleku". Make sure it's
> > a real email address or it will be rejected as an unauthorised sender.
> > Then run the following commands
> > cd jaikuengine
> > make clean
> > make zip_all && python manage.py update
> > Now look athttp://exampleku.appspot.combutdo NOT sign up for an
> > account yet. Everything should work except:http://exampleku.appspot.com/channel > > At this point you have a working application but not enough data for
> > it to be useful.
> > Now go to:http://appengine.google.com/dashboard?&app_id=exampleku > > This is your JaikuEngine instance's dashboard.
> > Click on the Data Viewer in the left-hand navbar. It should be empty
> > because you don't have any data in your database.
> > Now go to:http://exampleku.appspot.com/joinandcreate a user with a
> > screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this
> > should work rather than fall over when it tries to authorise the
> > sending of email. Make sure this user is set up with a real email
> > address as it will send you a confirmation email. Click on the
> > confirmation email and finish setting up the exampleku user.
> > Now look athttp://exampleku.appspot.com/exploreItshould have an
> > auto-generated post from your exampleku user saying that they've
> > joined.
> > Now go to settings.py and change line 225 to say
> > API_DISABLE_VERIFICATION = False
> > Then redeploy with following commands:
> > make clean
> > make zip_all && python manage.py update
> > Your JaikuEngine instance should now be ready for end-users. Enjoy.
Please excuse me if this ends up being a duplicate post not sure what
happened to the first message.
But I wanted to let you know that your instructions worked for me.
Thanks for the info.
On Mar 15, 7:31 pm, Adewale Oshineye <adew...@gmail.com> wrote:
> Thanks to help from @bobwyman and @termie I have a pretty thorough
> walkthrough on setting up your own Jaiku Engine instance. I'd
> appreciate it if people could try it out and let me know if it worked
> for them. I've also attached my app.yaml and settings.py so that you
> can see what I had at the end of the process.
> ======Walkthrough=================
> Walkthrough: replace exampleku and exampleku.appspot with your Jaiku
> Engine instance's name
> ########################################################################### ###################
> Set up the new application via the AppEngine dashboard here:http://appengine.google.com/startIn my case I'm setting up an
> instance called Exampleku athttp://exampleku.appspot.com > svn checkouthttp://jaikuengine.googlecode.com/svn/trunk/jaikuengine > Open app.yaml and change the first line to the name of your
> application. In this case: exampleku
> Open settings.py and change the following:
> Add your name and a valid email address to the list of ADMINS on lines 26-28
> Change the SECRET_KEY on line 61 to something secure. I recommend a
> good passphrase. Not "I am so secret" This will be used for API
> authentication so it's important that it's kept secure. Checking it
> into your public Github repository would be a bad idea.
> On line 132 change the SITE_NAME. I'm using "Exampleku"
> On line 133 change the default support channel. I prefer to call it
> after the site so I've renamed it from "support" to "exampleku"
> Every JaikuEngine installation has a special user who is
> automatically added to every other user's contact list and is used to
> provide access for unauthenticated users. On line 136 you should
> define that user for your site. The name you choose will get
> concatenated onto your appspot domain. In my case I'm choosing
> "exampleku" Note that I did not use an email address. Just the user's
> name. This user doesn't exist yet and we will have to create it later.
> On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com
> On line 150 change your HOSTED_DOMAIN to appspot.com This says that
> you're not planning to deploy the site to your own domain like
> jaiku.com or somemicrobloggingsite.com but will instead by hosting on
> one of the *.appspot.com sub-domains.
> On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This
> will later be concatenated with your HOSTED_DOMAIN to give your site's
> address.
> On line 155 change your NSDOMAIN to exampleku.appspot.com or the
> equivalent for your site's address.
> On line 225 change API_DISABLE_VERIFICATION to True. This is a
> temporary removal of all security so that you can set up your default
> user who will authorise all later users.
> On line 304 switch off the support for using queuing to handle large
> numbers of users unless you want to set up a cron somewhere to trigger
> the background processing. You switch off the queuing by setting
> QUEUE_ENABLED = False
> Replace lines 366 to 370 with the following:
> def default_email_sender():
> return 'your_em...@domain.com'
> Then replace the string 'your_em...@domain.com' with your actual
> email address or whatever email address you want all emails from your
> Jaiku Engine instance to look like they're sent from. Given that if
> your instance gets popular you'll be sending quite a lot of email (and
> possibly receiving replies) I recommend that you don't use your
> personal email address. You should probably use an email address
> that's named after your site. In this case "exampleku". Make sure it's
> a real email address or it will be rejected as an unauthorised sender.
> Then run the following commands
> cd jaikuengine
> make clean
> make zip_all && python manage.py update
> Now look athttp://exampleku.appspot.combut do NOT sign up for an
> account yet. Everything should work except:http://exampleku.appspot.com/channel > At this point you have a working application but not enough data for
> it to be useful.
> Now go to:http://appengine.google.com/dashboard?&app_id=exampleku > This is your JaikuEngine instance's dashboard.
> Click on the Data Viewer in the left-hand navbar. It should be empty
> because you don't have any data in your database.
> Now go to:http://exampleku.appspot.com/joinand create a user with a
> screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this
> should work rather than fall over when it tries to authorise the
> sending of email. Make sure this user is set up with a real email
> address as it will send you a confirmation email. Click on the
> confirmation email and finish setting up the exampleku user.
> Now look athttp://exampleku.appspot.com/exploreIt should have an
> auto-generated post from your exampleku user saying that they've
> joined.
> Now go to settings.py and change line 225 to say
> API_DISABLE_VERIFICATION = False
> Then redeploy with following commands:
> make clean
> make zip_all && python manage.py update
> Your JaikuEngine instance should now be ready for end-users. Enjoy.
> Please excuse me if this ends up being a duplicate post not sure what
> happened to the first message.
> But I wanted to let you know that your instructions worked for me.
> Thanks for the info.
> On Mar 15, 7:31 pm, Adewale Oshineye <adew...@gmail.com> wrote:
>> Thanks to help from @bobwyman and @termie I have a pretty thorough
>> walkthrough on setting up your own Jaiku Engine instance. I'd
>> appreciate it if people could try it out and let me know if it worked
>> for them. I've also attached my app.yaml and settings.py so that you
>> can see what I had at the end of the process.
>> ======Walkthrough=================
>> Walkthrough: replace exampleku and exampleku.appspot with your Jaiku
>> Engine instance's name
>> ########################################################################### ###################
>> Set up the new application via the AppEngine dashboard here:http://appengine.google.com/startIn my case I'm setting up an
>> instance called Exampleku athttp://exampleku.appspot.com >> svn checkouthttp://jaikuengine.googlecode.com/svn/trunk/jaikuengine >> Open app.yaml and change the first line to the name of your
>> application. In this case: exampleku
>> Open settings.py and change the following:
>> Add your name and a valid email address to the list of ADMINS on lines 26-28
>> Change the SECRET_KEY on line 61 to something secure. I recommend a
>> good passphrase. Not "I am so secret" This will be used for API
>> authentication so it's important that it's kept secure. Checking it
>> into your public Github repository would be a bad idea.
>> On line 132 change the SITE_NAME. I'm using "Exampleku"
>> On line 133 change the default support channel. I prefer to call it
>> after the site so I've renamed it from "support" to "exampleku"
>> Every JaikuEngine installation has a special user who is
>> automatically added to every other user's contact list and is used to
>> provide access for unauthenticated users. On line 136 you should
>> define that user for your site. The name you choose will get
>> concatenated onto your appspot domain. In my case I'm choosing
>> "exampleku" Note that I did not use an email address. Just the user's
>> name. This user doesn't exist yet and we will have to create it later.
>> On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com
>> On line 150 change your HOSTED_DOMAIN to appspot.com This says that
>> you're not planning to deploy the site to your own domain like
>> jaiku.com or somemicrobloggingsite.com but will instead by hosting on
>> one of the *.appspot.com sub-domains.
>> On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This
>> will later be concatenated with your HOSTED_DOMAIN to give your site's
>> address.
>> On line 155 change your NSDOMAIN to exampleku.appspot.com or the
>> equivalent for your site's address.
>> On line 225 change API_DISABLE_VERIFICATION to True. This is a
>> temporary removal of all security so that you can set up your default
>> user who will authorise all later users.
>> On line 304 switch off the support for using queuing to handle large
>> numbers of users unless you want to set up a cron somewhere to trigger
>> the background processing. You switch off the queuing by setting
>> QUEUE_ENABLED = False
>> Replace lines 366 to 370 with the following:
>> def default_email_sender():
>> return 'your_em...@domain.com'
>> Then replace the string 'your_em...@domain.com' with your actual
>> email address or whatever email address you want all emails from your
>> Jaiku Engine instance to look like they're sent from. Given that if
>> your instance gets popular you'll be sending quite a lot of email (and
>> possibly receiving replies) I recommend that you don't use your
>> personal email address. You should probably use an email address
>> that's named after your site. In this case "exampleku". Make sure it's
>> a real email address or it will be rejected as an unauthorised sender.
>> Then run the following commands
>> cd jaikuengine
>> make clean
>> make zip_all && python manage.py update
>> Now look athttp://exampleku.appspot.combut do NOT sign up for an
>> account yet. Everything should work except:http://exampleku.appspot.com/channel >> At this point you have a working application but not enough data for
>> it to be useful.
>> Now go to:http://appengine.google.com/dashboard?&app_id=exampleku >> This is your JaikuEngine instance's dashboard.
>> Click on the Data Viewer in the left-hand navbar. It should be empty
>> because you don't have any data in your database.
>> Now go to:http://exampleku.appspot.com/joinand create a user with a
>> screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this
>> should work rather than fall over when it tries to authorise the
>> sending of email. Make sure this user is set up with a real email
>> address as it will send you a confirmation email. Click on the
>> confirmation email and finish setting up the exampleku user.
>> Now look athttp://exampleku.appspot.com/exploreIt should have an
>> auto-generated post from your exampleku user saying that they've
>> joined.
>> Now go to settings.py and change line 225 to say
>> API_DISABLE_VERIFICATION = False
>> Then redeploy with following commands:
>> make clean
>> make zip_all && python manage.py update
>> Your JaikuEngine instance should now be ready for end-users. Enjoy.
> Then run the following commands > cd jaikuengine > make clean > make zip_all && python manage.py update
> Here I got no idea what do to. Can you please specify a little more?
I'm sorry. I made the assumption that you were using a Linux machine that would have make and various other tools on it. We should eventually replace the Makefile with a python program. I've added this to the issue tracker: http://code.google.com/p/jaikuengine/issues/detail?id=53
In the meantime you need to have the unix tool called make installed on your machine in order to build and deploy JaikuEngine. Then from your machine's command line or dos prompt you need to run the commands specified there in the directory that you checked out the code to.
If you followed the part of the instructions about checking out the code from Subversion you should be able to use the same window to build the code.
Hi Adewale! Thanks for the detailed guide, but I'm using MS Windows,
how to run the "make" command? I also only got a white page after I
run the appcfg.py update.
On Mar 17, 4:30 am, Adewale Oshineye <adew...@gmail.com> wrote:
> > Then run the following commands
> > cd jaikuengine
> > make clean
> > make zip_all && python manage.py update
> > Here I got no idea what do to. Can you please specify a little more?
> I'm sorry. I made the assumption that you were using a Linux machine
> that would have make and various other tools on it.
> We should eventually replace the Makefile with a python program. I've
> added this to the issue tracker:http://code.google.com/p/jaikuengine/issues/detail?id=53
> In the meantime you need to have the unix tool called make installed
> on your machine in order to build and deploy JaikuEngine. Then from
> your machine's command line or dos prompt you need to run the commands
> specified there in the directory that you checked out the code to.
> If you followed the part of the instructions about checking out the
> code from Subversion you should be able to use the same window to
> build the code.
> > Then run the following commands
> > cd jaikuengine
> > make clean
> > make zip_all && python manage.py update
> > Here I got no idea what do to. Can you please specify a little more?
> I'm sorry. I made the assumption that you were using a Linux machine
> that would have make and various other tools on it.
> We should eventually replace the Makefile with a python program. I've
> added this to the issue tracker:http://code.google.com/p/jaikuengine/issues/detail?id=53
> In the meantime you need to have the unix tool called make installed
> on your machine in order to build and deploy JaikuEngine. Then from
> your machine's command line or dos prompt you need to run the commands
> specified there in the directory that you checked out the code to.
> If you followed the part of the instructions about checking out the
> code from Subversion you should be able to use the same window to
> build the code.
> This installation still does not work for Mac users :-(
> On Mar 16, 1:30 pm, Adewale Oshineye <adew...@gmail.com> wrote:
>> 2009/3/16 stmons...@gmail.com <stmons...@gmail.com>:
>> > I was following you untill:
>> > Then run the following commands
>> > cd jaikuengine
>> > make clean
>> > make zip_all && python manage.py update
>> > Here I got no idea what do to. Can you please specify a little more?
>> I'm sorry. I made the assumption that you were using a Linux machine
>> that would have make and various other tools on it.
>> We should eventually replace the Makefile with a python program. I've
>> added this to the issue tracker:http://code.google.com/p/jaikuengine/issues/detail?id=53
>> In the meantime you need to have the unix tool called make installed
>> on your machine in order to build and deploy JaikuEngine. Then from
>> your machine's command line or dos prompt you need to run the commands
>> specified there in the directory that you checked out the code to.
>> If you followed the part of the instructions about checking out the
>> code from Subversion you should be able to use the same window to
>> build the code.
> > This installation still does not work for Mac users :-(
> > On Mar 16, 1:30 pm, Adewale Oshineye <adew...@gmail.com> wrote:
> >> 2009/3/16 stmons...@gmail.com <stmons...@gmail.com>:
> >> > I was following you untill:
> >> > Then run the following commands
> >> > cd jaikuengine
> >> > make clean
> >> > make zip_all && python manage.py update
> >> > Here I got no idea what do to. Can you please specify a little more?
> >> I'm sorry. I made the assumption that you were using a Linux machine
> >> that would have make and various other tools on it.
> >> We should eventually replace the Makefile with a python program. I've
> >> added this to the issue tracker:http://code.google.com/p/jaikuengine/issues/detail?id=53
> >> In the meantime you need to have the unix tool called make installed
> >> on your machine in order to build and deploy JaikuEngine. Then from
> >> your machine's command line or dos prompt you need to run the commands
> >> specified there in the directory that you checked out the code to.
> >> If you followed the part of the instructions about checking out the
> >> code from Subversion you should be able to use the same window to
> >> build the code.
> > > This installation still does not work for Mac users :-(
> > > On Mar 16, 1:30 pm, Adewale Oshineye <adew...@gmail.com> wrote:
> > >> 2009/3/16 stmons...@gmail.com <stmons...@gmail.com>:
> > >> > I was following you untill:
> > >> > Then run the following commands
> > >> > cd jaikuengine
> > >> > make clean
> > >> > make zip_all && python manage.py update
> > >> > Here I got no idea what do to. Can you please specify a little more?
> > >> I'm sorry. I made the assumption that you were using a Linux machine
> > >> that would have make and various other tools on it.
> > >> We should eventually replace the Makefile with a python program. I've
> > >> added this to the issue tracker:
> http://code.google.com/p/jaikuengine/issues/detail?id=53
> > >> In the meantime you need to have the unix tool called make installed
> > >> on your machine in order to build and deploy JaikuEngine. Then from
> > >> your machine's command line or dos prompt you need to run the commands
> > >> specified there in the directory that you checked out the code to.
> > >> If you followed the part of the instructions about checking out the
> > >> code from Subversion you should be able to use the same window to
> > >> build the code.
> > > > This installation still does not work for Mac users :-(
> > > > On Mar 16, 1:30 pm, Adewale Oshineye <adew...@gmail.com> wrote:
> > > >> 2009/3/16 stmons...@gmail.com <stmons...@gmail.com>:
> > > >> > I was following you untill:
> > > >> > Then run the following commands
> > > >> > cd jaikuengine
> > > >> > make clean
> > > >> > make zip_all && python manage.py update
> > > >> > Here I got no idea what do to. Can you please specify a little more?
> > > >> I'm sorry. I made the assumption that you were using a Linux machine
> > > >> that would have make and various other tools on it.
> > > >> We should eventually replace the Makefile with a python program. I've
> > > >> added this to the issue tracker:
> >http://code.google.com/p/jaikuengine/issues/detail?id=53
> > > >> In the meantime you need to have the unix tool called make installed
> > > >> on your machine in order to build and deploy JaikuEngine. Then from
> > > >> your machine's command line or dos prompt you need to run the commands
> > > >> specified there in the directory that you checked out the code to.
> > > >> If you followed the part of the instructions about checking out the
> > > >> code from Subversion you should be able to use the same window to
> > > >> build the code.
> On Apr 6, 12:21 am, kevin Wei <kevin2...@gmail.com> wrote: >> i think it is this issue: You do not have permission to modify this app >> (app_id=u'localfunfriend'). > Yeah, I agree. But I don't know why that happens.
>> so you need put the right APPSPOT application name. >> or the gmail account you provide doesnot have a 'localfunfriend' in appspot
> I provided the gmail account that I registered for my domain > (localfunfriend.appspot.com), so I guess it should not be this > problem.
> Any other thought?
Go to: http://appengine.google.com/ does it list localfunfriend as one of your applications? If so which account name does it have in the top right hand corner? Is it the same as the one you are using to try to deploy the application?
> > On Apr 6, 12:21 am, kevin Wei <kevin2...@gmail.com> wrote:
> >> i think it is this issue: You do not have permission to modify this app
> >> (app_id=u'localfunfriend').
> > Yeah, I agree. But I don't know why that happens.
> >> so you need put the right APPSPOT application name.
> >> or the gmail account you provide doesnot have a 'localfunfriend' in appspot
> > I provided the gmail account that I registered for my domain
> > (localfunfriend.appspot.com), so I guess it should not be this
> > problem.
> > Any other thought?
> Go to:http://appengine.google.com/does it list localfunfriend as one
> of your applications? If so which account name does it have in the top
> right hand corner? Is it the same as the one you are using to try to
> deploy the application?
> "Application Status " > "localfunfriend None Deployed "
Can you provide the local config file that was generated when you ran the script: python manage.py config --write-to-file Also your error message indicates that you don't have PIL installed. You should install that. There's a good set of instructions for installing PIL on the Mac here: http://aralbalkan.com/1454
> Can you provide the local config file that was generated when you ran
> the script: python manage.py config --write-to-file
> Also your error message indicates that you don't have PIL installed.
> You should install that. There's a good set of instructions for
> installing PIL on the Mac here:http://aralbalkan.com/1454
Thanks, and after installing the PIL, everything seems to work.
> Hi, I'm having trouble while trying to sing up or creating the user > because i get an "invalid nick" while trying to create a new user with > the application name. Any ideas?
> thanks!
> On Mar 15, 9:31 pm, Adewale Oshineye <adew...@gmail.com> wrote: >> Thanks to help from @bobwyman and @termie I have a pretty thorough >> walkthrough on setting up your own Jaiku Engine instance. I'd >> appreciate it if people could try it out and let me know if it worked >> for them. I've also attached my app.yaml and settings.py so that you >> can see what I had at the end of the process.
>> ======Walkthrough================= >> Walkthrough: replace exampleku and exampleku.appspot with your Jaiku >> Engine instance's name >> ########################################################################### ###################
>> Set up the new application via the AppEngine dashboard here:http://appengine.google.com/startIn my case I'm setting up an >> instance called Exampleku athttp://exampleku.appspot.com >> svn checkouthttp://jaikuengine.googlecode.com/svn/trunk/jaikuengine >> Open app.yaml and change the first line to the name of your >> application. In this case: exampleku >> Open settings.py and change the following: >> Add your name and a valid email address to the list of ADMINS on lines 26-28 >> Change the SECRET_KEY on line 61 to something secure. I recommend a >> good passphrase. Not "I am so secret" This will be used for API >> authentication so it's important that it's kept secure. Checking it >> into your public Github repository would be a bad idea. >> On line 132 change the SITE_NAME. I'm using "Exampleku" >> On line 133 change the default support channel. I prefer to call it >> after the site so I've renamed it from "support" to "exampleku" >> Every JaikuEngine installation has a special user who is >> automatically added to every other user's contact list and is used to >> provide access for unauthenticated users. On line 136 you should >> define that user for your site. The name you choose will get >> concatenated onto your appspot domain. In my case I'm choosing >> "exampleku" Note that I did not use an email address. Just the user's >> name. This user doesn't exist yet and we will have to create it later. >> On line 141 change the GAE_DOMAIN. In my case that is exampleku.appspot.com >> On line 150 change your HOSTED_DOMAIN to appspot.com This says that >> you're not planning to deploy the site to your own domain like >> jaiku.com or somemicrobloggingsite.com but will instead by hosting on >> one of the *.appspot.com sub-domains. >> On line 153 change the DEFAULT_HOSTED_SUBDOMAIN to exampleku. This >> will later be concatenated with your HOSTED_DOMAIN to give your site's >> address. >> On line 155 change your NSDOMAIN to exampleku.appspot.com or the >> equivalent for your site's address. >> On line 225 change API_DISABLE_VERIFICATION to True. This is a >> temporary removal of all security so that you can set up your default >> user who will authorise all later users. >> On line 304 switch off the support for using queuing to handle large >> numbers of users unless you want to set up a cron somewhere to trigger >> the background processing. You switch off the queuing by setting >> QUEUE_ENABLED = False >> Replace lines 366 to 370 with the following: >> def default_email_sender(): >> return 'your_em...@domain.com' >> Then replace the string 'your_em...@domain.com' with your actual >> email address or whatever email address you want all emails from your >> Jaiku Engine instance to look like they're sent from. Given that if >> your instance gets popular you'll be sending quite a lot of email (and >> possibly receiving replies) I recommend that you don't use your >> personal email address. You should probably use an email address >> that's named after your site. In this case "exampleku". Make sure it's >> a real email address or it will be rejected as an unauthorised sender. >> Then run the following commands >> cd jaikuengine >> make clean >> make zip_all && python manage.py update >> Now look athttp://exampleku.appspot.combut do NOT sign up for an >> account yet. Everything should work except:http://exampleku.appspot.com/channel >> At this point you have a working application but not enough data for >> it to be useful. >> Now go to:http://appengine.google.com/dashboard?&app_id=exampleku >> This is your JaikuEngine instance's dashboard. >> Click on the Data Viewer in the left-hand navbar. It should be empty >> because you don't have any data in your database. >> Now go to:http://exampleku.appspot.com/joinand create a user with a >> screen name of "exampleku" Since API_DISABLE_VERIFICATION = True this >> should work rather than fall over when it tries to authorise the >> sending of email. Make sure this user is set up with a real email >> address as it will send you a confirmation email. Click on the >> confirmation email and finish setting up the exampleku user. >> Now look athttp://exampleku.appspot.com/exploreIt should have an >> auto-generated post from your exampleku user saying that they've >> joined.
>> Now go to settings.py and change line 225 to say >> API_DISABLE_VERIFICATION = False >> Then redeploy with following commands: >> make clean >> make zip_all && python manage.py update
>> Your JaikuEngine instance should now be ready for end-users. Enjoy.
|
