I'm not sure when you tried it but there have been a lot of improvements. I'd recommedn either use the default grasp servers or running https://gitworkshop.dev/danconwaydev.com/ngit-grasp let me know ...
Hey Dan, so I got a grasp server up ... whoop!
Small problem though. I am trying to avoid DNS and trying to move to TOR and FIPS, so subdomains are permissioned and problematic. I'm trying to get rid of them.
Unfortunately it looks like gitworkshop.dev won't let you add a grasp server like https://15.235.3.231/grasp/ which is my grasp server.
Is this just a front end issue, or is there something deeper?
From my agent:
The issue is that GitWorkshop.dev expects GRASP servers to be at the root of a domain, not at a subpath like /grasp/. The domain validation regex in grasp.ts:26 only accepts plain hostnames:
/^([a-z0-9.-]+\.[a-z]{2,})(?::(\d{1,5}))?$/
When you enter https://laantungir.net/grasp, it fails because:
The https:// protocol prefix is not matched
The /grasp path is not matched
Small problem though. I am trying to avoid DNS and trying to move to TOR and FIPS, so subdomains are permissioned and problematic. I'm trying to get rid of them.
Unfortunately it looks like gitworkshop.dev won't let you add a grasp server like https://15.235.3.231/grasp/ which is my grasp server.
Is this just a front end issue, or is there something deeper?
From my agent:
The issue is that GitWorkshop.dev expects GRASP servers to be at the root of a domain, not at a subpath like /grasp/. The domain validation regex in grasp.ts:26 only accepts plain hostnames:
/^([a-z0-9.-]+\.[a-z]{2,})(?::(\d{1,5}))?$/
When you enter https://laantungir.net/grasp, it fails because:
The https:// protocol prefix is not matched
The /grasp path is not matched