- Available at '/help/'
- Loads and parses server config upon init and generates the necessary client config for access
- Links to 'Downloadable Tools' are not functional (task is not yet completed)
- A link was added to the default server page as well as a 'Help' option to the Piggy menu
Issue: #536
Change-Id: I10629de034c908ebc76f6feacbbfca1df7bf1c2b
Signhandler was moved from the ui to the root handler and genconfig
adjusted accordingly.
New discovery struct types to replace the JSON maps are defined in
pkg/types/camtypes. The changes are related to Issue #539.
Change-Id: Ib3f12feeaf6fa81107de2d468cab491723e590ae
Also, delete my old gce package from third_party and only use the
google metadata package (which my gce package became, and which was
also already vendored into third_party)
Fixes#596
Change-Id: I64fd6f1e9dc6f433466f91f81efd2ecbf039334f
I was getting bogus errors because I replicate to s3, but the
s3+blobpacked error should only come up if s3 is primary.
Also, document the database key used for blobpack's index when mysql
or another db is in use.
Change-Id: I21a1815715f70edc3f98abf7209744703aaf6d3b
Users need to set:
"packRelated": true,
... in their server config. This will probably become the default
value in the future.
This is currently mutually exclusive with diskpacked, which isn't good
at deleting things, and blobpacked loves to delete things (from the
loose blobs).
Updates #532
Change-Id: I8f4ea9406859b2705f26e9d1103d3acf9d1a8411
To avoid confusion, the previously named "memoryIndex" configuration
parameter, which actually meant to slurp the index into the memory
corpus, has been renamed to "copyIndexToMemory". "memoryIndex" is now
the parameter to enable a memory-only indexer.
http://camlistore.org/issue/416
Change-Id: I7026e5463fda3a1887a88e0b07d4e3431c60c8b7
The machine now boots with a new pair of cooperating systemd units:
1) cam-journal-gatewayd.service: a copy of the systemd-journal-gatewayd service,
which runs an HTTP interface to the systemd journal.
2) cam-journal-gatewayd.socket: a unix socket listener listening on unix
socket /run/camjournald.sock. Incoming connections will forward to 1).
Then the camlistored.service unit running camlistored under Docker now
passes -v /run/camjournald.sock:/run/camjournald.sock to make that unix socket
available to the Docker container.
Then in camlistored, a new handler at /debug/logs (wrapped in auth
checks) then opens that socket and makes an HTTP request to it,
copying its response (of log lines) back to the browser.
This will ease debugging, letting people only use their browser to
debug (or send logs to the Camlistore developers more likely), rather
than sshing in to CoreOS and learning CoreOS and systemd arcana.
Change-Id: Icd5967ae7e9946d36229bdbc5d37644a11ee5e9f
Part of Camlistore deploy to GCE easily. Will use paths like /gcs/bucket/foo or /gce-meta/attr for some
things previously-assumed to only be stored on the OS filesystem.
Change-Id: I2ed6cf5759c4d277f4e89a33a0fcfeee8bcbbf82
Context: http://camlistore.org/issue/479
This patch allows camlistored to wait for all the apps to be serving,
before printing its own listening address.
Change-Id: I4035b115a03ef6a2a43177b83b5b65ebc50a2188
Mario Russo