Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 0 additions & 78 deletions docs/archival/run-archival-node-with-nearup.md

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,24 +1,24 @@
---
id: run-archival-node-without-nearup
id: run-archival-node
title: Run an Archival Node
sidebar_label: Run a Node 🚀
sidebar_position: 2
description: How to run an Archival Node without nearup
description: How to run an Archival Node
---
## This page is DEPRECATED in favor of split storage archival. Please Use [Run a Split Storage Archival](/archival/split-storage-archival)

The following instructions are applicable across localnet, testnet, and mainnet.

If you are looking to learn how to compile and run a NEAR Archival node natively for one of the following networks, this guide is for you.

- [`testnet`](/archival/run-archival-node-without-nearup#testnet)
- [`mainnet`](/archival/run-archival-node-without-nearup#mainnet)
- [`testnet`](/archival/run-archival-node#testnet)
- [`mainnet`](/archival/run-archival-node#mainnet)


<blockquote class="info">
<strong>Heads up</strong><br /><br />

Running an archival node is very similar to running a [validator node](/validator/running-a-node) as both types of node use the same `nearcore` release. The main difference for running an archival node is a modification to the `config.json` by changing `archive` to `true`. See below for more details.
Running an archival node is very similar to running a [validator node](/validator/compile-and-run-a-node) as both types of node use the same `nearcore` release. The main difference for running an archival node is a modification to the `config.json` by changing `archive` to `true`. See below for more details.

</blockquote>

Expand Down
85 changes: 0 additions & 85 deletions docs/rpc/run-rpc-node-with-nearup.md

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,23 +1,23 @@
---
id: run-rpc-node-without-nearup
id: run-rpc-node
title: Run an RPC Node
sidebar_label: Run a Node 🚀
sidebar_position: 2
description: How to run an RPC Node without nearup
description: How to run an RPC Node
---

The following instructions are applicable across localnet, testnet, and mainnet.

If you are looking to learn how to compile and run a NEAR RPC node natively for one of the following networks, this guide is for you.

- [`testnet`](/rpc/run-rpc-node-without-nearup#testnet)
- [`mainnet`](/rpc/run-rpc-node-without-nearup#mainnet)
- [`testnet`](/rpc/run-rpc-node#testnet)
- [`mainnet`](/rpc/run-rpc-node#mainnet)


<blockquote class="info">
<strong>Heads up</strong><br /><br />

Running a RPC node is very similar to running a [validator node](/validator/running-a-node) as both types of node use the same `nearcore` release. The main difference for running a validator node is requiring `validator_key.json` to be used by the validator node to support its work of validating blocks and chunks on the network.
Running a RPC node is very similar to running a [validator node](/validator/compile-and-run-a-node) as both types of node use the same `nearcore` release. The main difference for running a validator node is requiring `validator_key.json` to be used by the validator node to support its work of validating blocks and chunks on the network.

</blockquote>

Expand Down
Loading
Loading