I assume you want to encrypt some files using your public GPG key. I’ll focus on simplicity rather than completeness (minimal steps required to implement encryption).
First you have to generate key pair:
$ mkdir -p ~/.gnupg
$ gpg --gen-key
Then see your new key ID and export it to public key storage:
$ gpg --list-keys # get KEY_ID from output
$ gpg --keyserver "hkp://subkeys.pgp.net" --send-key <KEY_ID>
On remote machine import the key and make it trusted (to avoid warnings during encryption):
$ gpg --keyserver "hkp://subkeys.pgp.net" --recv-keys <KEY_ID>
$ gpg --edit-key <KEY_ID>
> trust
Then you can used this key to encrypt files and delete original (if needed):
$ gpg -r <KEY_ID> --output <FILE>.gpg --encrypt <FILE>
$ rm <FILE>
And the decryption (on host where private key is stored):
$ gpg -r <KEY_ID> --output <FILE> --decrypt <FILE>.gpg
I’ve been using many different Python Web Frameworks so far:
All frameworks have its strengths and weakness. For new project that will handle appointments using existing calendar I decided to give web2py a try, rationale:
- all stuff included on board, no manual integration of 3rd party libraries
- stable API
- small and elegant
- integrates with GAE (with subset of DB layer)
- template selection separated from controller (easier unit testing)
- easy template syntax (reuses Python code embedded into markup language)
After first phase of product I’ll report if my expectations above were correct and what kind of problems were located (if any).
We, Aplikacja.info are delivering online booking services for Polish customers using med.aplikacja.info service since 2008. The service is mainly targeted at small/medium medical businesses and allows to integrate seamlessly with existing webpage.
I was asked recently about integration with hosted Microsoft Exchange calendar. Customer (also medical business) is using currently iPhone to record visits and would like to use existing contacts and calendar events and allow his customers to book online.
Our current persistence mechanism is local SQL database. In order to integrate with external contact / event source we have the following options:
(more…)
