Closed andygolay closed 3 months ago
This link was supposed to go to the Aptos CLI installation instructions. Going forward we can have an installation instructions on this page itself with the new movement CLI.
Ok so I can add the installation instructions under the Aptos heading there?
Yeah that would be perfect. Let’s also clarify the movement CLI is analogous to the Aptos CLI and Sui is under development.
Alright, submitted PR https://github.com/movementlabsxyz/movement-docs/pull/18
@Rahat-ch @PrasoonPratham I'm getting ready to update the docs relating to Aptos CLI so they are relevant to the changes to Movement CLI (which replaces Aptos CLI).
On this page I see a link to Install Aptos CLI but the link goes to https://docs.movementnetwork.xyz/.
If you're not sure where it would go, may I suggest a Developer Tooling section?
https://github.com/movementlabsxyz/aptos-core/tree/movement/crates/aptos
for developers who want to dive into the source code
and the syntax is changed as follows:
Wherever you have the
aptos
command in Aptos CLI, simply substitutemovement
for it, in the docs.So
aptos move build
becomesmovement move build
.This is different than the old Movement CLI, where you would use
movement aptos move build
because both Aptos and Sui CLI were embedded into that one Movement CLI.Movement CLI now is focused on supporting Aptos Move exclusively at first, hence removing the need to specify
aptos
in specific CLI commands.movement
branch of https://github.com/movementlabsxyz/aptos-core/ and cd into it.Then run
cargo build -p movement
.This generates the
target/debug/movement
executable, which you can copy into yourbin
or add it to yourPATH
depending on your system config.Example of copying
movement
tobin
on Mac or Linux:Hope this helps. Please let me know if you'd like me to add any of it anywhere specifically in the docs.