You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Copy and paste the SDL from [this site](https://github.com/ovrclk/cosmos-omnibus/blob/master/akash/deploy.yml) into the Cloudmos SDL editor window
29
+
* Copy and paste the SDL from [this site](https://github.com/akash-network/cosmos-omnibus/blob/master/akash/deploy.yml) into the Cloudmos SDL editor window
30
30
***NOTE -** the SDL within GitHub currently has a storage > size value of 120Gi. Omnibus uses a compressed snapshot of the blockchain and when expanded 120GB of storage for the deployment will not be enough. At the time of this writing adjusting the storage size to 350GB will suffice and allow some growth. Please adjust the storage appropriately and as shown in the screenshot below.
* The list of public RPC nodes recommended at the time of this writing are listed in the Available Nodes section
19
-
* While we seek to ensure that this documentation is always up to date, visit the [`Akash RPC list`](https://raw.githubusercontent.com/ovrclk/net/master/mainnet/rpc-nodes.txt)in our GitHub repo for possible recent additions
19
+
* While we seek to ensure that this documentation is always up to date, visit the [`Akash RPC list`](https://raw.githubusercontent.com/akash-network/net/main/mainnet/rpc-nodes.txt)in our GitHub repo for possible recent additions
Copy file name to clipboardExpand all lines: akash-nodes/run-an-akash-node/additional-information.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Akash Node configurations are found within these files:
18
18
19
19
## Akash Networks
20
20
21
-
Within this guide the Akash mainnet is used and as specified in the AKASH\_NET value. To launch a node on the testnet or edgenet and for additional network information, use this [guide](https://github.com/ovrclk/net).
21
+
Within this guide the Akash mainnet is used and as specified in the AKASH\_NET value. To launch a node on the testnet or edgenet and for additional network information, use this [guide](https://github.com/akash-network/net).
*[provider-services add-genesis-account](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_add-genesis-account.md) - Add a genesis account to genesis.json
19
-
*[provider-services auth-server](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_auth-server.md) - Run the authentication server to issue JWTs to tenants
20
-
*[provider-services collect-gentxs](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_collect-gentxs.md) - Collect genesis txs and output a genesis.json file
21
-
*[provider-services debug](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_debug.md) - Tool for helping with debugging your application
22
-
*[provider-services events](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_events.md) - Prints out akash events in real time
23
-
*[provider-services hostname-operator](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_hostname-operator.md) - kubernetes operator interfacing with k8s nginx ingress
*[provider-services ip-operator](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_ip-operator.md) - kubernetes operator interfacing with Metal LB
26
-
*[provider-services keys](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_keys.md) - Manage your application's keys
27
-
*[provider-services lease-events](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_lease-events.md) - get lease events
28
-
*[provider-services lease-logs](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_lease-logs.md) - get lease logs
29
-
*[provider-services lease-shell](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_lease-shell.md) - do lease shell
30
-
*[provider-services lease-status](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_lease-status.md) - get lease status
*[provider-services migrate-endpoints](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_migrate-endpoints.md) - migrate endpoints between deployments on the same provider
33
-
*[provider-services migrate-hostnames](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_migrate-hostnames.md) - migrate hostnames between deployments on the same provider
34
-
*[provider-services node](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_node.md) - operations with akash RPC node
35
-
*[provider-services operator](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_operator.md) - kubernetes operators control
*[provider-services run](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_run.md) - run akash provider
38
-
*[provider-services run-resource-server](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_run-resource-server.md) - Run the resource server which authenticates tenants based on JWT before providing access to resources
39
-
*[provider-services send-manifest](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_send-manifest.md) - Submit manifest to provider(s)
40
-
*[provider-services service-status](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_service-status.md) - get service status
41
-
*[provider-services show-cluster-ns](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_show-cluster-ns.md) - print cluster namespace for given lease ID
42
-
*[provider-services status](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_status.md) - get provider status
*[provider-services validate-genesis](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_validate-genesis.md) - validates the genesis file at the default location or at the location passed as an arg
45
-
*[provider-services version](https://github.com/ovrclk/docs/blob/master/cli/provider-services\_version.md) - Print the application binary version information
*[provider-services add-genesis-account](https://github.com/akash-network/docs/blob/master/cli/provider-services\_add-genesis-account.md) - Add a genesis account to genesis.json
19
+
*[provider-services auth-server](https://github.com/akash-network/docs/blob/master/cli/provider-services\_auth-server.md) - Run the authentication server to issue JWTs to tenants
20
+
*[provider-services collect-gentxs](https://github.com/akash-network/docs/blob/master/cli/provider-services\_collect-gentxs.md) - Collect genesis txs and output a genesis.json file
21
+
*[provider-services debug](https://github.com/akash-network/docs/blob/master/cli/provider-services\_debug.md) - Tool for helping with debugging your application
22
+
*[provider-services events](https://github.com/akash-network/docs/blob/master/cli/provider-services\_events.md) - Prints out akash events in real time
23
+
*[provider-services hostname-operator](https://github.com/akash-network/docs/blob/master/cli/provider-services\_hostname-operator.md) - kubernetes operator interfacing with k8s nginx ingress
*[provider-services ip-operator](https://github.com/akash-network/docs/blob/master/cli/provider-services\_ip-operator.md) - kubernetes operator interfacing with Metal LB
26
+
*[provider-services keys](https://github.com/akash-network/docs/blob/master/cli/provider-services\_keys.md) - Manage your application's keys
27
+
*[provider-services lease-events](https://github.com/akash-network/docs/blob/master/cli/provider-services\_lease-events.md) - get lease events
28
+
*[provider-services lease-logs](https://github.com/akash-network/docs/blob/master/cli/provider-services\_lease-logs.md) - get lease logs
29
+
*[provider-services lease-shell](https://github.com/akash-network/docs/blob/master/cli/provider-services\_lease-shell.md) - do lease shell
30
+
*[provider-services lease-status](https://github.com/akash-network/docs/blob/master/cli/provider-services\_lease-status.md) - get lease status
*[provider-services migrate-endpoints](https://github.com/akash-network/docs/blob/master/cli/provider-services\_migrate-endpoints.md) - migrate endpoints between deployments on the same provider
33
+
*[provider-services migrate-hostnames](https://github.com/akash-network/docs/blob/master/cli/provider-services\_migrate-hostnames.md) - migrate hostnames between deployments on the same provider
34
+
*[provider-services node](https://github.com/akash-network/docs/blob/master/cli/provider-services\_node.md) - operations with akash RPC node
35
+
*[provider-services operator](https://github.com/akash-network/docs/blob/master/cli/provider-services\_operator.md) - kubernetes operators control
*[provider-services run](https://github.com/akash-network/docs/blob/master/cli/provider-services\_run.md) - run akash provider
38
+
*[provider-services run-resource-server](https://github.com/akash-network/docs/blob/master/cli/provider-services\_run-resource-server.md) - Run the resource server which authenticates tenants based on JWT before providing access to resources
39
+
*[provider-services send-manifest](https://github.com/akash-network/docs/blob/master/cli/provider-services\_send-manifest.md) - Submit manifest to provider(s)
40
+
*[provider-services service-status](https://github.com/akash-network/docs/blob/master/cli/provider-services\_service-status.md) - get service status
41
+
*[provider-services show-cluster-ns](https://github.com/akash-network/docs/blob/master/cli/provider-services\_show-cluster-ns.md) - print cluster namespace for given lease ID
42
+
*[provider-services status](https://github.com/akash-network/docs/blob/master/cli/provider-services\_status.md) - get provider status
*[provider-services validate-genesis](https://github.com/akash-network/docs/blob/master/cli/provider-services\_validate-genesis.md) - validates the genesis file at the default location or at the location passed as an arg
45
+
*[provider-services version](https://github.com/akash-network/docs/blob/master/cli/provider-services\_version.md) - Print the application binary version information
Copy file name to clipboardExpand all lines: command-line/install.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ v0.1.0
55
55
{% tab title="Linux" %}
56
56
### Linux
57
57
58
-
Download the archive for your system from the [release page](https://github.com/ovrclk/akash/releases), extract it, and install the `akash` binary into your path.
58
+
Download the archive for your system from the [release page](https://github.com/akash-network/node/releases), extract it, and install the `akash` binary into your path.
59
59
60
60
**GoDownloader**
61
61
@@ -81,7 +81,7 @@ Installing Akash suite from source
81
81
```
82
82
$ go get -d github.com/akash-network/provider
83
83
$ cd $GOPATH/src/github.com/akash-network/provider
Copy file name to clipboardExpand all lines: decentralized-cloud/marketplace.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Contents:
12
12
13
13
The Akash Marketplace revolves around [Deployments](marketplace.md#deployment), which fully describe the resources that a tenant is requesting from the network. [Deployments](marketplace.md#deployment) contain [Groups](marketplace.md#group), which is a grouping of resources that are meant to be leased together from a single provider.
14
14
15
-
Deploying applications onto [Akash](https://github.com/ovrclk/akash) involves two types of users:
15
+
Deploying applications onto [Akash](https://github.com/akash-network/node) involves two types of users:
16
16
17
17
1. The **Tenant**: the entity that deploys the application.
18
18
2. The **Provider**: the entity that hosts the application.
1. Install [**Keplr**](https://chrome.google.com/webstore/detail/keplr/dmkamcknogkgcdfhhbddcghachkejeap?hl=en)\*\*\*\* wallet as a browser plugin
16
16
2. Install [**Cloudmos Deploy**](https://cloudmos.io/cloud-deploy)\*\*\*\* and import your AKT wallet address from Keplr
17
-
3.[**Fund your wallet**](https://github.com/ovrclk/awesome-akash/blob/raptoreum/raptoreum-miner/README.md#Quickest-way-to-get-more-AKT)
17
+
3.[**Fund your wallet**](https://github.com/akash-network/awesome-akash/blob/raptoreum/raptoreum-miner/README.md#Quickest-way-to-get-more-AKT)
18
18
19
19
For additional help we recommend you [**follow our full deployment guide**](https://docs.akash.network/guides/deploy)\*\*\*\* in parallel with this guide.
Copy file name to clipboardExpand all lines: deploy/multi-tier-app.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ In this guide, we will deploy a multi-tier web application on Akash. The example
6
6
7
7
### Before We Begin
8
8
9
-
This guide is to be considered an extension of the [Deploy an Application](https://github.com/ovrclk/docs/blob/master/deploy/broken-reference/README.md) guide. Please ensure you have successfully completed all steps leading up to the "Create the Deployment Configuration" step in said guide, as they will not be discussed here.
9
+
This guide is to be considered an extension of the [Deploy an Application](https://github.com/akash-network/docs/blob/master/deploy/broken-reference/README.md) guide. Please ensure you have successfully completed all steps leading up to the "Create the Deployment Configuration" step in said guide, as they will not be discussed here.
10
10
11
11
## Create the Deployment Configuration
12
12
@@ -153,7 +153,7 @@ profiles:
153
153
154
154
The `profiles` entries contain named compute and placement profiles to be used in the deployment.
155
155
156
-
Since we have 2 services to deploy, details for each of them must be specified here. This section is very similar to a standard deployment, so it won't be covered in detail here. An important item to note, however, is that the named compute/placement profiles here (`redis` and `goosebin`) must match the names we had specified in the `services` section. [Additional mappings](https://github.com/ovrclk/docs/tree/a8e7a472b43ec742a03bc5063f6c5a82ca3ca2ea/sdl/README.md#profiles) can also be specified within `profiles` such as audited attributes and data center attributes.
156
+
Since we have 2 services to deploy, details for each of them must be specified here. This section is very similar to a standard deployment, so it won't be covered in detail here. An important item to note, however, is that the named compute/placement profiles here (`redis` and `goosebin`) must match the names we had specified in the `services` section. [Additional mappings](https://github.com/akash-network/docs/tree/a8e7a472b43ec742a03bc5063f6c5a82ca3ca2ea/sdl/README.md#profiles) can also be specified within `profiles` such as audited attributes and data center attributes.
157
157
158
158
#### Deployments
159
159
@@ -175,7 +175,7 @@ Similar to the `profiles` entries, we must specify deployment criteria for both
175
175
176
176
#### Deployment
177
177
178
-
Now that we have the SDL configured, let's deploy this application and see what happens. A more detailed guide on this process can be found in the [Deploy an Application](https://github.com/ovrclk/docs/blob/master/deploy/broken-reference/README.md) guide.
178
+
Now that we have the SDL configured, let's deploy this application and see what happens. A more detailed guide on this process can be found in the [Deploy an Application](https://github.com/akash-network/docs/blob/master/deploy/broken-reference/README.md) guide.
0 commit comments