The os/user package nowadays says:
When cgo is available, and the required routines are implemented
in libc for a particular platform, cgo-based (libc-backed) code
is used. This can be overridden by using osusergo build tag,
which enforces the pure Go implementation.
So we don't need to work around it anymore.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
Sadly I did this all once (and more completely) but then lost the
commit. So this is a re-do. The sharing demo stuff isn't yet complete.
Updates #1658 etc
I moved the website to run on Fly.io some 6 months ago but lost the
git commit that did so. So now I'm redoing it from memory (sigh).
But we don't need any of this GCE or Mailgun stuff now. People can
subscribe to git commits via other means.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
These were all part of an earlier effort to let it be easy for people
to easily deploy their own Perkeep servers and get them on the
internet. The idea was that we'd run a small DNS server which would
map from GPG public keys to their rented cloud IPs which users would
prove to us with the gpgchallenge stuff.
The recently added Tailscale support (see 43f34e5cc5, #1668) makes
most of this redundant.
Also I'd stopped running this infrastructure ages ago and removed the
launcher code recently in b5823a65b9 (and disabled it in
c9f78d02ad). So this was all basically dead code.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
The publisher app required GopherJS which has been behind upstream Go
for many years. This just removes all GopherJS stuff, breaking the publisher
app in the process. We'll have to rewrite it.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
AppEngine lets you do just about anything these days. No need to cater
to the ancient limited version.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
We used to have a web-based Perkeep launcher at perkeep.org/launch
that created a GCE-based Perkeep instance for users, where they pay
Google for compute time. (One of those "one click deploy" template things)
Unfortunately, Google broke their APIs for doing the third party VM
creations and we disabled it some years ago. But the code remains. And
now, updating it again, we find that they've broken it again:
Error: pkg/deploy/gce/deploy.go:358:4: servicemanagement.NewServicesService(s).Enable undefined (type *servicemanagement.ServicesService has no field or method Enable)
It's not worth fighting Google's API breakages. Just remove the GCE
launcher support as it's been unused for years.
We can always resurrect this code from git if really needed. But a
Digital Ocean or Fly launcher would probably be much easier.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
Index:
- Handle bad signatures on permanodes just like we handled them on
claims.
Importer tests:
- Make pkg/client's UploadPublicKey method public so that we can ensure
that the key was uploaded before uploading permanodes in importer
tests. This would otherwise be done automatically by methods such as
UploadNewPermanode but the importer uses the Blobserver API, it
uploads blobs with ReceiveBlob. ReceiveBlob does not know if blobs
are schemas or regular blobs, so it couldn't know if it is
appropriate to upload the key.
Brad Fitzpatrick