I've written a small connector for the deployment scripts to upload to neocities.com, a static site hosting provider. The API that I used is detailed here: https://neocities.org/api. Because the API for neocities is entirely REST based (and pretty different from the bucket approach of s3/gcs/rackspace), I had to do a lot of adjustments to the architecture of the deployment packages, especially around the BaseDeploymentEngine and BaseFile.
The deployment mechanics are fairly primitive right now (to do a full deployment, it deletes all server files and re-uploads), but this might be preferable than trying to compare updated times. This will keep it more "deployment" driven than "sync latest changes" driven.
You can set this up in the config by specifying in the config.json:
Hey!
I've written a small connector for the deployment scripts to upload to neocities.com, a static site hosting provider. The API that I used is detailed here: https://neocities.org/api. Because the API for neocities is entirely REST based (and pretty different from the bucket approach of s3/gcs/rackspace), I had to do a lot of adjustments to the architecture of the deployment packages, especially around the BaseDeploymentEngine and BaseFile.
The deployment mechanics are fairly primitive right now (to do a full deployment, it deletes all server files and re-uploads), but this might be preferable than trying to compare updated times. This will keep it more "deployment" driven than "sync latest changes" driven.
You can set this up in the config by specifying in the config.json:
{ "provider": "neocities" }Shoot me any feedback.