3 ms·
I like the idea of having a git backend for site data, but in the case of the author: why not just use a regular host? There are some pay-for-what-you-use hosts
by rb2k_ 16y ago
I like the idea of having a git backend for site data, but in the case of the author: why not just use a regular host?
There are some pay-for-what-you-use hosts (e.g. https://www.nearlyfreespeech.net/ https://www.nearlyfreespeech.net/).
- JoachimSchipper 16y agoI'm using NFS for my personal site. It works perfectly fine, and has cost me $0.08 for this month (so far). Yes, I should write more.
- MindTwister 16y agoWell, https://www.nearlyfreespeech.net/ https://www.nearlyfreespeech.net/ supports git, bash, sh etc, if you follow the instructions from the comments further down you can use git as a backend ^^
- MindTwister 16y agoActually I was wrong, I read it here: http://stackoverflow.com/questions/279169/deploy-php-using-git http://stackoverflow.com/questions/279169/deploy-php-using-g...
- ryankanno 16y agoI think the point of this setup was to get a free solution for those sites that get infrequent hits - that still fit into a git developer's workflow. We all have those sites. I noes! :) Not to mention, while some have mentioned that you could create a github page, does that mean you'd have to create a separate repo for every page? (Not sure how github pages work at that level). This solution would allow for a single repo that holds all the sites - whereas not polluting your repo space. I think this solution is for a particular niche of devs who control N number of domains - who want minimal maintenance and most importantly - no cost. ;)