Update solana version and other minor fixes (project-serum#6)

* Update Solana version, 1.4.9 is no longer supported

* Replace ssh address of origin repo with http address

* Force the snapshot to be fetched on startup

* Remove the comments from api.sh and mention the issue in the README

README.md

@@ -69,9 +69,11 @@ Among other things, the above command will modify your new instance by
 - increasing the file descriptor limit for processes managed by supervisor to 600000
 - creating a `tmpfs` device for the accounts store mounted at `/mnt/accounts`
 
-After running the `setup.yaml` script, a reboot is necessary to pick up various system configs. Post-reboot, supervisor 
-should start up the validator using the `sol/api.sh` script. The validator will be listening on port 8899 for rest 
-requests, so issuing a curl to the `/health` path will return the health status of the validator.
+After running the `setup.yaml` script, a reboot is necessary to pick up various system configs. If it is the first time
+that the validator starts, it is possible that it thinks that a local ledger is present when there is not: commenting out the
+lines 64-66 of `deploy/api.sh` will prevent this. Post-reboot, supervisor should start up the validator using the
+`sol/api.sh` script. The validator will be listening on port 8899 for rest requests, so issuing a curl to the `/health`
+path will return the health status of the validator.
 ```
 $ curl http://localhost:8899
 ``` 

deploy/hosts.yaml

@@ -1,7 +1,7 @@
 all:
   vars:
     validator_user: sol
-    solana_version: v1.4.9
+    solana_version: v1.4.24
     run_validator: true
     nginx_sites:
       - validator.conf

deploy/setup.yaml

@@ -155,7 +155,7 @@
   tasks:
     - name: update git
       git:
-        repo: git@github.com:project-serum/validators.git
+        repo: https://github.com/project-serum/validators.git
         dest: "~/{{ validator_user }}"
         version: "{{ commit | default('HEAD')}}"