Skip to content
Docsgr cloud

Command line

gr cloud

Your cloud projects, and building a local graph from one

From the help of gr 0.2.16. gr help cloud prints it in full.

gr cloud [command]

gr cloud code

Show this project's cloud code copy

Show the copy of this project's code Graphide keeps on its servers, and this machine's upload of it. Every cloud project has one; deleting the project's cloud copy deletes it.

gr cloud code [flags]

gr cloud delete

Delete a cloud project of yours from Graphide's servers (nothing on any computer is touched)

Deletes the project's copy on Graphide's servers: its synced graph, the stored copy of its code, its rank scores and its run records. It cannot be undone, and everyone it is shared with loses it too. Nothing on any computer is touched: a clone keeps its code and its local graph, and opening one again while signed in makes a new cloud copy. It also makes room on your account for another project.

gr cloud delete <project> [flags]
FlagWhat it does
--owner stringwhose project, when two share a name: me, or the owner's email
-y, --yesdelete without asking

gr cloud invite

Invite a teammate to a cloud project (default: the one this folder is linked to)

Adds the Graphide account with this email to the project. The project shows in their gr cloud projects (and in :cloud in the app) at once, and gr cloud open there gives their clone the project's graph, re-linking a clone they already have. They need a Graphide account first: signing in once makes one.

gr cloud invite <email> [project] [flags]
FlagWhat it does
--jsonprint the daemon's answer as JSON
--owner stringwhose project, when two share a name: me, or the owner's email

gr cloud members

List who is in a cloud project (default: the one this folder is linked to)

gr cloud members [project] [flags]
FlagWhat it does
--jsonprint the daemon's answer as JSON
--owner stringwhose project, when two share a name: me, or the owner's email

gr cloud open

Build this machine's graph of a cloud project from its cloud graph

Finds this machine's clone of the project (or the folder --root names), checks with git that its code is the project's, and downloads the cloud graph instead of building one: the graph of your commit when the cloud has it, else the nearest older one, updated to your code. When your code is behind the cloud graph it says to pull first (--older takes the older graph it offers instead). With no clone here, --clone clones it first; --cache0 keeps no local graph at all.

gr cloud open <project> [flags]
FlagWhat it does
--cache0keep no local graph: agents' graph tools ask the cloud
--cloneclone the project first when this machine has no clone
--dest stringwhere --clone clones to (default ~/graphide/<repo>)
--drop-unsentre-link a clone even when changes for its old project cannot be sent now (they stay in the set-aside graph)
--jsonprint the daemon's answer as JSON
--olderwhen your code is behind, take the older cloud graph offered
--owner stringwhose project, when two share a name: me, or the owner's email
--root stringthe clone to use (default: this machine's clone of the project)
--url stringwhat --clone clones from (default the project's https remote)

gr cloud projects

List the projects on your account and this machine's clone of each

Lists every project on your Graphide account, owned or shared with you, with the clone of it this machine has and how that clone's code relates to the project's cloud graph. Open one with gr cloud open <name>.

gr cloud projects [flags]
FlagWhat it does
--jsonprint the daemon's answer as JSON

gr cloud remove

Take someone out of a cloud project (default: the one this folder is linked to)

Removes the member with this email from the project: it leaves their cloud projects, and their graph branches there are deleted. What they landed on main stays. Only the project's owner removes someone else; anyone may remove themself.

gr cloud remove <email> [project] [flags]
FlagWhat it does
--owner stringwhose project, when two share a name: me, or the owner's email

Every command also takes --root <folder>, the project to act on. Without it, gr uses the git repository you are in, or else the current folder.

These docs describe Graphide 0.2.16, the latest release. Something wrong or missing? Tell us onDiscord or at hello@graphide.com.