Update Ord To New Release
Last updated
Last updated
In this example, Ord 0.5.2 was updated to Ord 0.6.1
Determine the current release of your Ord server:
CTRL-C to stop your Ord server
Now is a good time to make sure all your backups are up-to-date
Download the latest compiled Ord release from . If on Mac with M1 or M2 processor, choose the AArch tar.gz package
Double-click the .gz file to extract its contents
Open another Finder window and press Command+Shift+Dot to view hidden files
Navigate to where your current Ord binary is located: /Users/yourusername/.cargo/bin
Rename the current ord file like ord.052.old
Drag the new ‘ord’ binary file to the same folder as the old binary file
The following command may prompt macOS with a security warning. If so, go to Settings > Privacy & Security and scroll to find where it says Ord was blocked. Click to Allow Anyway. Keep doing this Version command until you stop getting warnings and it responds to indicate the new version. Alternately you can try to simply right-click on the Ord binary in Finder and then proceed to terminal.
Note: The upgrade from Ord 0.5.2 to 0.6.1 introduced handling for Cursed Inscriptions. As a result, Ord must build a completely new index file. Therefore, the next step is not typically necessary for a basic Ord upgrade.
To force Ord to build a completely new index file, rename the current index.redb file to index.redb.old
Run the index command
Note: As of Ord 0.7.0 you need to add 'run' to the end of the index command.
Wait as long as it takes for the index build to complete
This indexing took approximately 1.5 hours while indexing to an external SSD drive.
In Terminal, use CTRL-C at any point to stop the process (it can be restarted later)
When the index build completes, start your Ord server