Specifically:
* Update references to `camtool`, which has been renamed to just `pk`.
* Fix a couple of nearby grammar mistakes.
Change-Id: I60af05879c09d59f7136466dfc1f88d95e4eb919
And vendor in a compatible GopherJS version
(bd77b112433e999447bf4bc599e36214ba494a99).
In addition, since GopherJS:
1) Still does not support Go modules for now
2) Seems to be dying (https://github.com/gopherjs/gopherjs/issues/894)
3) Has been hard to maintain for Perkeep
we decided to gradually move away from it, and to remove it from go.mod. As a
result, in this PR, we repurposed the skipGopherJS option into buildWebUI,
which, in combination with the GO111MODULE env value gives the 4 following
possible behaviours (GO111MODULE=auto omitted on purpose).
1) GO111MODULE=off, -buildWebUI=true:
-old behaviour, i.e. use vendored in gopherjs to rebuild (gophejs itself and then)
the web UI
2) GO111MODULE=off, -buildWebUI=false:
-fetch the JS code for the web UI and the publisher from the Google Cloud bucket
of the Perkeep project. That code was previously built by the scenario 1) and
uploaded there.
3) GO111MODULE=on, -buildWebUI=false:
-same as 2)
4) GO111MODULE=on, -buildWebUI=true:
-forces GO111MODULE=off behind the scenes when rebuilding GopherJS and the
web UI code with it.
Finally, we also modified the checks regarding where we are (i.e.
whether in $GOPATH/src/perkeep.org). Because even though go modules will
in theory allow to build from anywhere, since we disable modules when
the Web UI is rebuilt, we can therefore only do it from within the
GOPATH.
Change-Id: Iee66d7ee882c6d408b5996fd26178bcd7426e3f8
So now when we get the e-mail on a website restart, we'll actually
know what version of it is running.
Also,
make.go: skip gopherjs checks when we only build the website or
camnetdns.
Change-Id: I3f6985afc8931fe478cc4f7caba2b1fc31bc815b
I mistakenly added the files directly in vendor/go4.org instead of
vendor/go4.org/rollsum in 2a85cb7142
Neither running 'go run make.go', nor running 'go test' (in e.g.
pkg/schema) caught that the package was missing in vendor, because i
happened to also have the package in my GOPATH.
Iirc, before modules existed it would have been enough to run 'go run
make.go' to catch that, whereas now 'go run make.go' ran happily for me,
even with GO111MODULE=off, which is somewhat annoying.
Change-Id: I97805c924700fa159a14fd33014dabc423a4fc60
I'm getting reminders from Let's Encrypt that perkeep.org is using a
cert obtained with TLS-SNI-01, which is now deprecated.
I think this change would be enough to switch to TLS-ALPN-01.
Change tested on the staging instance at https://staging.camlistore.net
Change-Id: I19dc51171228e6598846a778aadb8497d3406446
A working importer for the Instapaper service. The importer imports
bookmarks, full text articles, and highlights. A blob item handler for
Instapaper highlight permanodes is included to show summarized highlight
content from the server UI.
Also, this CL updates github.com/garyburd.com/go-auth to rev
bca2e7f09a178fd36b034107a00e2323bca6a82e in order to get support for
XAuth requests.
Fixes#1208
Change-Id: I72e0c40b245c7eec4a44bb475fcaa96a0ee9a1c5
The javascript code was taking into account the OmitAuthToken signal
that there should be no auth, but it hadn't been done in the gopherjs
code yet as well.
Fixes#1221
Change-Id: I3eda0cc12c99664739d6073cc1aeba1aeed8a88a
Because it is mandatory as of nov 2018:
https://android-developers.googleblog.com/2017/12/improving-app-security-and-performance.html
As the default Notification.Builder constructor is deprecated in API 26,
this change also adds the use of the new constructor, which requires a
notification channel Id.
Note: since the users are now in full-control of the notifications,
they can now choose to completely block the auto-upload notification
channel. Given that the main goal of the notification was to keep the
app in memory in order for auto-upload to work, one could expect that
blocking the channel would defeat the notification's purpose. However,
as far as I could test, auto-uploading seems to still be working even
after disabling the channel, and letting the activity die (tip: in
devoloper options, one can tick "Don't keep activities"). In fact,
Perkeep Uploader still always runs as a service.
Also build pk-put shipped in the app with Go 1.11.
Fixes#1202
Change-Id: I8f98e0df742915cb504b6c1cfaa42ca6dc7b6189
The ref: predicate was treated as a special case, to make it correspond
to navigating to a "blobRef URL", e.g.
http://localhost:3179/ui/sha224-b6a88695e3a9178d45fdfb1fa888939d5adc090f866aaa1d7b5ec3a5
However, we should not do that when the query is only for the prefix of
a blobRef, e.g. "ref:sha224-b6a88695".
This CL therefore adds a check to make sure we're in the presence of a
full blobRef before navigating to the special case.
Fixes#1119
Change-Id: Ib92b43adbb2316c1607d617eb03de132c38de85f
In 5894af5196 we chose not to vendor
sqlite3-binding.c and sqlite3-binding.h in, because we rely on the
system's libsqlite3 instead. But we never told devcam test to use the
corresponding necessary "libsqlite3" tag, which is now done in this CL.
Also, comment properly about it in .gitignore.
And make Travis CI use the devcam installed in $GOPATH/bin, instead of
specifically building one in tree.
Change-Id: I4b7bb1305669037f84063c7cf6c7f356c99f3edc
Wich also means updating github.com/gopherjs/gopherjs to
rev 0210a2f0f73c96103378b0b935f39868e5731809
Fixes#1211
Change-Id: I9ae580bffda523237d471942f39ae157ff4bd303