Did you publish the domain correctly with pages.sr.ht? When it works,
curl should print a hash. Also note that you need to use an OAuth 2.0
token, a legacy token will not work.
> Did you publish the domain correctly with pages.sr.ht? When it works,> curl should print a hash. Also note that you need to use an OAuth 2.0> token, a legacy token will not work.
Yes, publishing had been successful yesterday. I've re-run the
command again.
I needed to use -H "Authorization: Bearer $AUTH" to make it work,
(--oauth2-bearer "access token" wasn't enough). curl did indeed
return a hash:
% curl -H "Authorization: Bearer ${AUTHCODE}" -Fcontent=@site.tar.gzhttps://pages.sr.ht/publish/jkoshy.net
3815c0d71a69d59e4425c2388dff77d77f5103afa589e98931b0eef471593bca
This is the same hash as returned by yesterday's upload.
As of now 'curl https://jkoshy.net' has started working, which is
great. 'curl https://www.jkoshy.net' however continues to report
the SSL error.
Thanks,
Joseph Koshy
On Sat Feb 27, 2021 at 3:58 PM EST, wrote:
> As of now 'curl https://jkoshy.net' has started working, which is> great. 'curl https://www.jkoshy.net' however continues to report> the SSL error.
These are treated as separate sites, and you need to publish them
separately. I disrecommend using www. in $CURRENTYEAR, though.
Drew DeVault <sir@cmpwn.com> writes:
> On Sat Feb 27, 2021 at 3:58 PM EST, wrote:>> As of now 'curl https://jkoshy.net' has started working, which is>> great. 'curl https://www.jkoshy.net' however continues to report>> the SSL error.>> These are treated as separate sites, and you need to publish them> separately. I disrecommend using www. in $CURRENTYEAR, though.
curious about recommending against 'www.': why?