rename deployments redirect component

astriaorg · Jan 2, 2024 · c256f8c · c256f8c
1 parent e11c8f3
commit c256f8c
Show file tree

Hide file tree

Showing 13 changed files with 24 additions and 24 deletions.
diff --git a/docs/components/_deployments.mdx → ...nts/_deployment-instructions-redirect.mdx b/docs/components/_deployments.mdx → ...nts/_deployment-instructions-redirect.mdx
diff --git a/docs/dusk-faq/1-information.mdx b/docs/dusk-faq/1-information.mdx
@@ -4,9 +4,9 @@ sidebar_position: 5
 
 # FAQ and Debugging
 
-import Deployments from '../components/_deployments.mdx';
+import DeploymentsRedirect from '../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 ## Endpoints
 

diff --git a/docs/overview/1-introduction.mdx b/docs/overview/1-introduction.mdx
@@ -4,9 +4,9 @@ sidebar_position: 1
 
 # Introduction
 
-import Deployments from '../components/_deployments.mdx';
+import DeploymentsRedirect from '../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 Astria is a shared sequencing network that allows many rollups to share a single
 decentralized network of sequencers. These sequencers are simple and

diff --git a/docs/overview/2-why-decentralized-sequencers.mdx b/docs/overview/2-why-decentralized-sequencers.mdx
@@ -4,9 +4,9 @@ sidebar_position: 2
 
 # Why Decentralized Sequencers?
 
-import Deployments from '../components/_deployments.mdx';
+import DeploymentsRedirect from '../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 Centralization is antithetical to crypto. And yet, today’s rollups almost
 universally depend on a single sequencer. Centralized sequencers provide fast

diff --git a/docs/overview/3-cross-rollup-composability.mdx b/docs/overview/3-cross-rollup-composability.mdx
@@ -4,9 +4,9 @@ sidebar_position: 3
 
 # Cross-Rollup Composability
 
-import Deployments from '../components/_deployments.mdx';
+import DeploymentsRedirect from '../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 Because Astria handles the transaction ordering for multiple rollups, it’s able
 to provide guarantees that transactions are only included as part of an atomic

diff --git a/docs/overview/architecture/1-overview.mdx b/docs/overview/architecture/1-overview.mdx
@@ -4,9 +4,9 @@ sidebar_position: 1
 
 # Architecture Overview
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 At a high level, Astria breaks out all of the components that are historically
 combined together in monolithic blockchains into individual components. This

diff --git a/docs/overview/architecture/2-transaction-flow.mdx b/docs/overview/architecture/2-transaction-flow.mdx
@@ -4,9 +4,9 @@ sidebar_position: 2
 
 # Transaction Flow
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 The full transaction flow through the Astria stack is as follows:
 

diff --git a/docs/overview/architecture/3-rollup.mdx b/docs/overview/architecture/3-rollup.mdx
@@ -4,9 +4,9 @@ sidebar_position: 3
 
 # Rollups
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 Astria is designed for permissionless rollup integration and takes advantage of [lazy](https://en.wikipedia.org/wiki/Lazy_evaluation?ref=blog.astria.org) shared sequencing. This means that rollup developers have total sovereignty over their own execution state and can swap out sequencing layers without fear of being locked in. You do not need to ask for permission or go through a governance process to gain access. A rollup simply needs to satisfy the following interfaces:
 

diff --git a/docs/overview/architecture/4-composer.mdx b/docs/overview/architecture/4-composer.mdx
@@ -4,9 +4,9 @@ sidebar_position: 4
 
 # Composer
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 The Composer is an in-house abstraction over the potential actors in Astria's
 MEV supply chain. It currently contains a naive implementations of the role a

diff --git a/docs/overview/architecture/5-the-astria-sequencer.mdx b/docs/overview/architecture/5-the-astria-sequencer.mdx
@@ -4,9 +4,9 @@ sidebar_position: 5
 
 # The Astria Sequencer
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 The Astria Shared Sequencer is a decentralized network of nodes utilizing CometBFT that come to consensus on an ordered set of transactions (ie. it is a blockchain). The unique feature of the sequencer is that the transactions it includes are not executed (lazy sequencing), and are destined for another execution engine (ie. a rollup). This excludes “sequencer native” transactions, such as transfers of tokens within the sequencer chain. Transactions from any given rollup are only ordered on the sequencer, not executed.
 

diff --git a/docs/overview/architecture/6-relayer.mdx b/docs/overview/architecture/6-relayer.mdx
@@ -4,9 +4,9 @@ sidebar_position: 6
 
 # Relayer
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 The Relayer's responsibility is to take validated blocks from the sequencer and
 pass them along to both the Conductor and the DA layer. Because the sequencer's

diff --git a/docs/overview/architecture/7-conductor.mdx b/docs/overview/architecture/7-conductor.mdx
@@ -4,9 +4,9 @@ sidebar_position: 7
 
 # Conductor
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 Conductor's role is to drive the deterministic execution of sequencer blocks to
 rollups. 

diff --git a/docs/overview/architecture/8-data-availability-layer.mdx b/docs/overview/architecture/8-data-availability-layer.mdx
@@ -4,9 +4,9 @@ sidebar_position: 8
 
 # Data Availability Layer
 
-import Deployments from '../../components/_deployments.mdx';
+import DeploymentsRedirect from '../../components/_deployment-instructions-redirect.mdx';
 
-<Deployments />
+<DeploymentsRedirect />
 
 The dev-cluster uses [Celestia](https://github.com/celestiaorg) as the data
 availability layer and is the ultimate destination of all data that has been