make ssh work again

Author: Weiwu

Makefile

@@ -36,4 +36,4 @@ prepare:
 
 
 upload:
-	scp -r ./ s01cd.syd6.hostingplatform.net.au:repo.tokenscript.org/
+	scp -P 2683 -r ./ net@s01cd.syd6.hostingplatform.net.au:repo.tokenscript.org/

README.md

@@ -12,41 +12,27 @@ Then, run this to upload the files. This will only work if you already configure
 
     $ make upload
 
-## How it works
+## Configure SSH access
 
-The Makfile generates a list of rewrite rules for accessing TokenScript files based on their token contract addresses. See more in [how_it_works.md](how_it_works.md)
-
-## When will it be used
-
-A user obtains a TokenScript in two ways.
-
-1. If the user accesses a token use-case through a website, the TokenScript for that use-case is offered through that web page[^1].
-
-2. If the user needs a TokenScriptn without going through a dapp website, (e.g. he receives a token from an exchange withdraw or restoring a wallet backup), the user-agent (wallet) tries to find the TokenScript for that token by accessing the `scriptURI()` repo server. Using this repo as a backup source if that function doesn't exist on the token contract.
+This is tricky.  You need 2 things: 
 
-## Submit a TokenScript to this repo
+1. Adding your IP address to the whitelist. [Official document](https://ventraip.com.au/faq/article/enabling-ssh-and-sftp-access-on-a-hosting-service/)
+2. Adding your key to [the cPanel](https://web23.hosting-cloud.net:2083/cpsess0722241000/frontend/paper_lantern/index.html?login=1&post_login=29808973384901).
 
-When you deploy your Tokenscript, please also send a copy to this repo in the form of a new Pull Request. By doing so:
+Note that the whitelist is not in the cPanel.
 
-1. If a user gets a token without going through any of the dapp websites with your TokenScript deployed, they can still get a copy from here.
+In reality, both are ticky.
 
-2. When we upgrade the schema, we know who to talk to for updating existing TokenScript.
+1. Adding your IP address to the whitelist - the whitelist only allows 3 entries, **you need to delete an old one to add a new one**.
+2. Adding SSH public key: It's better to add your SSH public key by asking a colleague to do the following, **avoid using cPanel at all**, since cPanel requires you to share your private key, which should not be shared in any case.
 
-When you submit the TokenScript, create a new directory following the convention [as specified](hier.md).
+    $ ssh -p 2683 net@s01cd.syd6.hostingplatform.net.au
+    $ cat >> .ssh/authorized_keys
 
-## When a user-agent (client) obtains a TokenScript from this repo
+## How the .htaccess file works
 
-- A user receives a token directly.
-- A user scans a QR code or opens a link that represents a token-holding smart-contract.
-- A user gets a "MagicLink" which allows him to redeem a token.
-- A user recovers a key backup, and the user-agent discovers that he/she owns a few Token.
-
-
-Check [user-agent behaviour](user-agent.md) for how a user-agent is supposed to communicate with a repo server.
-
-## Will namespace and schema always be updated at the same time?
-
-Likely so in 2019 and perhaps 2020 as well. In the first two years, TokenScript schema and namespace are versioned in the same way. A user-agent only works with TokenScripts whose schema and namespace are _both_ supported by the user-agent.
+The Makfile generates a list of rewrite rules for accessing TokenScript files based on their token contract addresses. See more in [how_it_works.md](how_it_works.md)
 
-Beyond 2020, a user-agent would work with any TokenScript whose namespace it supports, even if its schema is not supported. By such an arrangement, TokenScript schema can evolve at a faster pace than its namespace, by adding new elements and not removing old elements; but it leaves room for mistakes, resulting existing Tokenscript becomes invalidated. We think it's a fair trade-off.
+## Background: how user agents get tokenscripts
 
+See [how user agents get tokenscripts](how_user_agents_get_tokenscripts.md).

how_user_agents_get_tokenscripts.md

@@ -0,0 +1,32 @@
+A user obtains a TokenScript in two ways.
+
+1. If the user accesses a token use-case through a website, the TokenScript for that use-case is offered through that web page[^1].
+
+2. If the user needs a TokenScriptn without going through a dapp website, (e.g. he receives a token from an exchange withdraw or restoring a wallet backup), the user-agent (wallet) tries to find the TokenScript for that token by accessing the `scriptURI()` repo server. Using this repo as a backup source if that function doesn't exist on the token contract.
+
+## Submit a TokenScript to this repo
+
+When you deploy your Tokenscript, please also send a copy to this repo in the form of a new Pull Request. By doing so:
+
+1. If a user gets a token without going through any of the dapp websites with your TokenScript deployed, they can still get a copy from here.
+
+2. When we upgrade the schema, we know who to talk to for updating existing TokenScript.
+
+When you submit the TokenScript, create a new directory following the convention [as specified](hier.md).
+
+## When a user-agent (client) obtains a TokenScript from this repo
+
+- A user receives a token directly.
+- A user scans a QR code or opens a link that represents a token-holding smart-contract.
+- A user gets a "MagicLink" which allows him to redeem a token.
+- A user recovers a key backup, and the user-agent discovers that he/she owns a few Token.
+
+
+Check [user-agent behaviour](user-agent.md) for how a user-agent is supposed to communicate with a repo server.
+
+## Will namespace and schema always be updated at the same time?
+
+Likely so in 2019 and perhaps 2020 as well. In the first two years, TokenScript schema and namespace are versioned in the same way. A user-agent only works with TokenScripts whose schema and namespace are _both_ supported by the user-agent.
+
+Beyond 2020, a user-agent would work with any TokenScript whose namespace it supports, even if its schema is not supported. By such an arrangement, TokenScript schema can evolve at a faster pace than its namespace, by adding new elements and not removing old elements; but it leaves room for mistakes, resulting existing Tokenscript becomes invalidated. We think it's a fair trade-off.
+