ผมกำลังดำเนินการ
เริ่ม
ถ่ายทอดความรู้ที่มี
# CREATE DSA AT CLIENT
user1@client:~$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/Users/user1/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/user1/.ssh/id_dsa.
Your public key has been saved in /Users/user1/.ssh/id_dsa.pub.
The key fingerprint is:
9a:30:11:3c:3c:cf:89:01:3a:e1:5d:bd:49:c9:50:f4 user1@client
The key's randomart image is:
+--[ DSA 1024]----+
|. .+.o*o. |
|.o. B. =. |
|o. ..B..oE |
| . ..+o |
| o S |
| o o |
| o |
| |
| |
+-----------------+
# COPY PUBLIC DSA TO SERVER
user1@client:~$ scp ~/.ssh/id_dsa.pub user1@some.server.com:/home/user1/.ssh
user1@some.server.com's password:
id_dsa.pub 100% 642 0.6KB/s 00:00
# SETUP AUTHORIZED_KEY FROM CLIENT TO SERVER
user1@some.server.com:~$ cd ~/.ssh
user1@some.server.com:~$ touch authorized_keys
user1@some.server.com:~$ chmod 600 authorized_keys
user1@some.server.com:~$ cat id_dsa.pub >> authorized_keys
DONE!
Google App Engine: How to survive in Google's Ecosystem (#53)
Mr. Jodok Batlogg bio
30min ◊◊ Intermediate
Saturday 01:50pm, Ballroom II
categories: case study, django, gae, web, web servicesIt all started in 2003 with Plone, continued in 2005 with Zope3 and right now the road seems to go to the Cloud, namely Google App Engine.
In this talk the experiences building a community portal based on Google App Engine will be presented. The main parts are: the App Engine Python SDK, Google's Bigtable, the Admin AJAX interface based on Google Web Toolkit / ext GWT, the delivery frontend using Django, Amazon Webservices handling large files and Content Delivery and of course as mentioned beforehand business aspects.
ต้องลองไปสักครั้ง ว่ามั๋ย