diff --git a/src/content/Docs/assets/akashAudit.png b/src/content/Docs/assets/akashAudit.png new file mode 100644 index 00000000..3de92eb4 Binary files /dev/null and b/src/content/Docs/assets/akashAudit.png differ diff --git a/src/content/Docs/assets/applyAudit.png b/src/content/Docs/assets/applyAudit.png new file mode 100644 index 00000000..b0ec4771 Binary files /dev/null and b/src/content/Docs/assets/applyAudit.png differ diff --git a/src/content/Docs/assets/basicSettings.png b/src/content/Docs/assets/basicSettings.png new file mode 100644 index 00000000..4805239c Binary files /dev/null and b/src/content/Docs/assets/basicSettings.png differ diff --git a/src/content/Docs/assets/congratsScreen.png b/src/content/Docs/assets/congratsScreen.png new file mode 100644 index 00000000..e1b80a25 Binary files /dev/null and b/src/content/Docs/assets/congratsScreen.png differ diff --git a/src/content/Docs/assets/connect-keplr-wallet.jpg b/src/content/Docs/assets/connect-keplr-wallet.jpg new file mode 100644 index 00000000..8a4365ec Binary files /dev/null and b/src/content/Docs/assets/connect-keplr-wallet.jpg differ diff --git a/src/content/Docs/assets/controlAccess.png b/src/content/Docs/assets/controlAccess.png new file mode 100644 index 00000000..9987273d Binary files /dev/null and b/src/content/Docs/assets/controlAccess.png differ diff --git a/src/content/Docs/assets/createVM.png b/src/content/Docs/assets/createVM.png new file mode 100644 index 00000000..1e23001c Binary files /dev/null and b/src/content/Docs/assets/createVM.png differ diff --git a/src/content/Docs/assets/creatingScript.png b/src/content/Docs/assets/creatingScript.png new file mode 100644 index 00000000..8be56eff Binary files /dev/null and b/src/content/Docs/assets/creatingScript.png differ diff --git a/src/content/Docs/assets/dashboard.png b/src/content/Docs/assets/dashboard.png new file mode 100644 index 00000000..22975b21 Binary files /dev/null and b/src/content/Docs/assets/dashboard.png differ diff --git a/src/content/Docs/assets/harddiskSize.png b/src/content/Docs/assets/harddiskSize.png new file mode 100644 index 00000000..497fa04c Binary files /dev/null and b/src/content/Docs/assets/harddiskSize.png differ diff --git a/src/content/Docs/assets/importWallet.png b/src/content/Docs/assets/importWallet.png new file mode 100644 index 00000000..778acd66 Binary files /dev/null and b/src/content/Docs/assets/importWallet.png differ diff --git a/src/content/Docs/assets/installDependencies.png b/src/content/Docs/assets/installDependencies.png new file mode 100644 index 00000000..4f3f0877 Binary files /dev/null and b/src/content/Docs/assets/installDependencies.png differ diff --git a/src/content/Docs/assets/kubernetesBuild.png b/src/content/Docs/assets/kubernetesBuild.png new file mode 100644 index 00000000..42d89978 Binary files /dev/null and b/src/content/Docs/assets/kubernetesBuild.png differ diff --git a/src/content/Docs/assets/kubernetesReady.png b/src/content/Docs/assets/kubernetesReady.png new file mode 100644 index 00000000..abc3a9ff Binary files /dev/null and b/src/content/Docs/assets/kubernetesReady.png differ diff --git a/src/content/Docs/assets/loadImage.png b/src/content/Docs/assets/loadImage.png new file mode 100644 index 00000000..12c41990 Binary files /dev/null and b/src/content/Docs/assets/loadImage.png differ diff --git a/src/content/Docs/assets/manualMode.png b/src/content/Docs/assets/manualMode.png new file mode 100644 index 00000000..ff2713fa Binary files /dev/null and b/src/content/Docs/assets/manualMode.png differ diff --git a/src/content/Docs/assets/memorySize.png b/src/content/Docs/assets/memorySize.png new file mode 100644 index 00000000..e78911e6 Binary files /dev/null and b/src/content/Docs/assets/memorySize.png differ diff --git a/src/content/Docs/assets/networkSettings.png b/src/content/Docs/assets/networkSettings.png new file mode 100644 index 00000000..8599cdbf Binary files /dev/null and b/src/content/Docs/assets/networkSettings.png differ diff --git a/src/content/Docs/assets/portDNS.png b/src/content/Docs/assets/portDNS.png new file mode 100644 index 00000000..6cd70c33 Binary files /dev/null and b/src/content/Docs/assets/portDNS.png differ diff --git a/src/content/Docs/assets/praetor-app-login-home.jpg b/src/content/Docs/assets/praetor-app-login-home.jpg new file mode 100644 index 00000000..b3d09db2 Binary files /dev/null and b/src/content/Docs/assets/praetor-app-login-home.jpg differ diff --git a/src/content/Docs/assets/praetor-app-login.jpg b/src/content/Docs/assets/praetor-app-login.jpg new file mode 100644 index 00000000..b3d09db2 Binary files /dev/null and b/src/content/Docs/assets/praetor-app-login.jpg differ diff --git a/src/content/Docs/assets/praetorMode.png b/src/content/Docs/assets/praetorMode.png new file mode 100644 index 00000000..dfc90d0f Binary files /dev/null and b/src/content/Docs/assets/praetorMode.png differ diff --git a/src/content/Docs/assets/praetorRoot.png b/src/content/Docs/assets/praetorRoot.png new file mode 100644 index 00000000..01500dd7 Binary files /dev/null and b/src/content/Docs/assets/praetorRoot.png differ diff --git a/src/content/Docs/assets/privateIP.png b/src/content/Docs/assets/privateIP.png new file mode 100644 index 00000000..6419d3be Binary files /dev/null and b/src/content/Docs/assets/privateIP.png differ diff --git a/src/content/Docs/assets/processorNumber.png b/src/content/Docs/assets/processorNumber.png new file mode 100644 index 00000000..4e1364e1 Binary files /dev/null and b/src/content/Docs/assets/processorNumber.png differ diff --git a/src/content/Docs/assets/providerAttributes.png b/src/content/Docs/assets/providerAttributes.png new file mode 100644 index 00000000..3ed2576a Binary files /dev/null and b/src/content/Docs/assets/providerAttributes.png differ diff --git a/src/content/Docs/assets/providerConfig.png b/src/content/Docs/assets/providerConfig.png new file mode 100644 index 00000000..cdb1f581 Binary files /dev/null and b/src/content/Docs/assets/providerConfig.png differ diff --git a/src/content/Docs/assets/providerDeployments.png b/src/content/Docs/assets/providerDeployments.png new file mode 100644 index 00000000..baa44e63 Binary files /dev/null and b/src/content/Docs/assets/providerDeployments.png differ diff --git a/src/content/Docs/assets/providerPricing.png b/src/content/Docs/assets/providerPricing.png new file mode 100644 index 00000000..52d62020 Binary files /dev/null and b/src/content/Docs/assets/providerPricing.png differ diff --git a/src/content/Docs/assets/providerSettings.png b/src/content/Docs/assets/providerSettings.png new file mode 100644 index 00000000..468f0f06 Binary files /dev/null and b/src/content/Docs/assets/providerSettings.png differ diff --git a/src/content/Docs/assets/serverAccess.png b/src/content/Docs/assets/serverAccess.png new file mode 100644 index 00000000..06c2b724 Binary files /dev/null and b/src/content/Docs/assets/serverAccess.png differ diff --git a/src/content/Docs/assets/sign-message.jpg b/src/content/Docs/assets/sign-message.jpg new file mode 100644 index 00000000..30ed3ff0 Binary files /dev/null and b/src/content/Docs/assets/sign-message.jpg differ diff --git a/src/content/Docs/assets/virutalbox.png b/src/content/Docs/assets/virutalbox.png new file mode 100644 index 00000000..8b7355a7 Binary files /dev/null and b/src/content/Docs/assets/virutalbox.png differ diff --git a/src/content/Docs/deployments/praetor-app/akash-provider/build-cloud-provider/index.mdx b/src/content/Docs/deployments/praetor-app/akash-provider/build-cloud-provider/index.mdx new file mode 100644 index 00000000..d7dc5d1a --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/akash-provider/build-cloud-provider/index.mdx @@ -0,0 +1,51 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 6 +title: "Build a Cloud Provider" +linkTitle: "Build a Cloud Provider" +--- + +# Build a Cloud Provider + +## Prerequisites of an Akash Provider + +### Wallet Funding - Minimum of 5 AKT + +To place a bid on an order, a deposit of 5 AKT is required. This deposit is fully refunded regardless of whether the bid is won or lost. + +For detailed steps on creating an Akash account, please refer to our [documentation](/docs/deployments/akash-cli/installation/). + +### Kubernetes Cluster Hardware Requirements and Recommendations + +Kubernetes Master Node Requirements + +* Minimum Specifications: + + * 8 CPUs + * 16 GB RAM + * 50 GB Disk + + +* Recommended Specifications: + + * 16 CPUs + * 32 GB RAM + * 100 GB Disk + + +Kubernetes Worker Node Requirements + +* Minimum Specifications: + + * 4 CPUs + * 8 GB RAM + * 100 GB Disk + +* Recommendations: + + * The more resources available, the better the performance, especially for handling a higher number of concurrent deployments. + * It is crucial to maximize CPU capacity. For instance, with 8 CPUs, 100 GB RAM, and 2 TB storage, the CPU would likely be the bottleneck. Since people tend to deploy at least 1 CPU per deployment, the server could only host 8 deployments maximum and likely about 6 deployments as other ~2 CPUs will be reserved by the Kubernetes system components. + +Ready to become an Akash Cloud Provider and start earning? Visit the [Praetor Application](https://akash.praetorapp.com/) now. + diff --git a/src/content/Docs/deployments/praetor-app/akash-provider/build-windows-provider/index.mdx b/src/content/Docs/deployments/praetor-app/akash-provider/build-windows-provider/index.mdx new file mode 100644 index 00000000..60e11929 --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/akash-provider/build-windows-provider/index.mdx @@ -0,0 +1,111 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 6 +title: "Build a Cloud Provider (Windows)" +linkTitle: "Build a Cloud Provider (Windows)" +--- + +# Build a Cloud Provider (Windows Machine) + +If you have a Windows machine and want to become a Provider, follow these steps: + +## Step 1: Download and Install Oracle VirtualBox + +1. Download VirtualBox by [here](https://www.virtualbox.org/wiki/Downloads). Select "Windows host" to download the Windows version. + +2. Install VirtualBox by double-clicking the downloaded file. + +## Step 2a: Create a New VM and Install an OS + +1. Open VirtualBox and click on Machine > New. + + + +2. Provide a name and path for the VM. Select the operating system type "Linux" and the version "Ubuntu" based on your computer's architecture. + +![](../../../../assets/virutalbox.png) + +3. Click Next and set the memory size (minimum required is 4096 MB). + +![](../../../../assets/memorySize.png) + +4. Click Next and select the "Create a virtual hard disk now" radio button. + +5. Click Create and choose the "VDI (VirtualBox Disk Image)" radio button. + +6. Click Next and select the "Dynamically allocated" radio button. + +7. Click Next and set the virtual hard disk size (minimum required is 30 GB). + +![](../../../../assets/harddiskSize.png) + +8. Click Create to finalize the new VM setup. + +![](../../../../assets/createVM.png) + +## Step 2b: Configure the VM + +1. Select the newly created VM and click Settings. + +2. In the System section, go to the Processor tab and set the Processor(s) to at least 2 CPUs. + +![](../../../../assets/processorNumber.png) + +3. In the Network section, go to the Adapter 1 tab and select "Bridged Adapter" under the "Attached to" label. + +4. Under Advanced settings: + * Set "Promiscuous Mode" to "Allow All". + + *Click the Refresh icon to refresh your MAC Address. + + *Ensure the "Cable Connected" checkbox is checked. + + +5. Click OK to save your settings. + +![](../../../../assets/networkSettings.png) + +## Step 2c: Start the VM and Install the OS + +1. Click Start to launch your VM. + +2. Provide an image of the OS you want to install in the VM. + +![](../../../../assets/loadImage.png) + +3. Follow the prompts to complete the OS installation (this typically takes 10-15 minutes). + +4. After installation, restart the VM. + +## Step 2d: Configure the OS + +1. If the user is a sudo user, refer to the [sudo user requirements](../sudo-user-reqs/). + +2. Open the terminal and type `ip a` to get your private IPv4 address. + +![](../../../../assets/privateIP.png) + +## Step 3: Port Forwarding + +1. Access your router's configuration page and set up port forwarding to the IPv4 address obtained earlier. + * Port 8443, 8444: For running Akash Provider service. + + * Port 80, 443: For applications deployed under your provider. + + * Port 22: For SSH connections. + + * Ports 30000-32767: For other TCP/UDP connections. + +![](../../../../assets/basicSettings.png) + +> Note: The configuration settings in the above screenshot are just for reference, and may vary depending on your ISP. + +You are now ready to become an Akash cloud provider. First, you will need to know your public IP address. + +## Support + +If you have any issues or trouble getting the provider machine up and running, you may reach out to the [Praetor](https://praetorapp.com) team on [Discord](https://discord.com/invite/uzUCHTF93D) or [Twitter/X](https://x.com/praetor_app). + + + diff --git a/src/content/Docs/deployments/praetor-app/akash-provider/decomission-provider/index.mdx b/src/content/Docs/deployments/praetor-app/akash-provider/decomission-provider/index.mdx new file mode 100644 index 00000000..023c62cc --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/akash-provider/decomission-provider/index.mdx @@ -0,0 +1,21 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 6 +title: "Decomission a Provider" +linkTitle: "Decomission a Provider" +--- + +# Decomission a Provider + +## Single Server Provider + + +To execute the following commands, first SSH into your machine using the credentials you used for Praetor. + + +`/usr/local/bin/k3s-uninstall.sh` + +and: + +`rm -rf ~/.akash/ ~/bin/ ~/.kube/ ~/.praetor/ ~/ingress-nginx-custom.yaml` \ No newline at end of file diff --git a/src/content/Docs/deployments/praetor-app/akash-provider/existing-cluster/index.mdx b/src/content/Docs/deployments/praetor-app/akash-provider/existing-cluster/index.mdx new file mode 100644 index 00000000..e1b82174 --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/akash-provider/existing-cluster/index.mdx @@ -0,0 +1,254 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 6 +title: "Existing Kubernetes Cluster" +linkTitle: "Existing Kubernetes Cluster" +--- + +# Existing Kubernetes Cluster +If you answered "yes," follow the guide below to become an Akash Cloud Provider. If "no," please refer to the [Single Server Provider](docs/deployments/praetor-app/akash-provider/single-server-provider/index.mdx) documentation for assistance. + + + +> NOTICE! It is now recommended that you use `chrony` instead of `systemd`. You can see instructions on how to install `chrony` on the [Time Sybnchronization Documentation page](docs/providers/build-a-cloud-provider/time-synchronization/index.md) + + +## Prerequisites: + +1. A complete Kubernetes cluster. +2. Open the SSH port (usually 22) for the IP Address "68.250.12.64" (Praetor App's IP). +3. An existing Akash wallet with a minimum balance of 5 AKT. +4. The Kubernetes config file of the cluster you wish to provide. +5. A valid domain name to perform DNS changes, pointing specific domains to your cluster's machines/IP addresses. + + +## Step 1: Check the Kubernetes Cluster + +Ensure your cluster is ready by executing the following command: + +``` +debian@node1:~$ kubectl get nodes -o wide + +NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME +node1 Ready control-plane,master 13d v1.23.6 10.0.10.114 Debian GNU/Linux 10 (buster) 4.19.0-20-amd64 containerd://1.6.3 + +node2 Ready control-plane,master 13d v1.23.6 10.0.10.115 Debian GNU/Linux 10 (buster) 4.19.0-20-amd64 containerd://1.6.3 + +node3 Ready 13d v1.23.6 10.0.10.116 Debian GNU/Linux 10 (buster) 4.19.0-20-amd64 containerd://1.6.3 +``` + +Notice the CONTAINER-RUNTIME column's value must be "containerd". + +Ensure that the Kubernetes cluster's runtime class is "gVisor." You can verify this by running the following command. + +``` +debian@node1:~$ kubectl get runtimeclass + +NAME HANDLER AGE +gvisor runsc 13d + +``` + +## Step 2: Praetor App Login + +Go to the [Praetor Application](https://akash.praetorapp.com/) to become an Akash Cloud Provider + + +![](../../../../assets/praetor-app-login-home.jpg) + +Click on the "Connect" button. It will ask you to connect your Akash wallet using the Keplr browser extension. + +> NOTICE! This address will be used to become a cloud provider on the network. + +![](../../../../assets/connect-keplr-wallet.jpg) + +Keplr will request your permission to connect the wallet with Praetor App. Click "Approve" to continue. + +![](../../../../assets/sign-message.jpg) + + +Kelpr wallet would ask you to approve the transaction by approving your signature. +This signature would be used to make secure communication between the services. + +![](../../../../assets/kubernetesBuild.png) + +You would be redirected to a page where you select the number of servers you want to provide to Akash. As you already have you already have an existing Kubernetes cluster, click on the "Skip this step if you have Kubernetes" button. + +## Step 3: Control Machine Access + + +![](../../../../assets/controlAccess.png) + +> NOTE! If you have GPUs, select "Yes" and you will see two options for your GPU selection. Please choose the appropriate answer and click the "Verify" button. + + +To install the Akash software and connect with your Kubernetes cluster, Praetor requires access to your server. This process needs a user with sudo access or root user privileges. + +### Prerequisites: + +**Open SSH Port:** Open the SSH port (usually 22) for the IP addresses "185.209.177.59, 185.209.177.46, 185.209.176.35" (Praetor App's IP). + +### Inputs Required: + +**Hostname:** Your server's hostname (either IP or web address without HTTP or HTTPS). If you use an IP address, it must be your public IPv4 address. + +**Username:** The server username to log in (e.g., root, admin, ubuntu, debian, etc.). + +### Password or File: + +**Password:** Enter the login password for the user. +**File:** Upload the SSH private key file. If your key file is encrypted, you can also provide a passphrase. +**Kube Config File:** Upload a valid Kubernetes configuration file. + +Upon clicking "verify," the following pop-up screen will open. + +![](../../../../assets/kubernetesReady.png) + +This alert message asks if you have the necessary dependencies for the Akash Network already installed. The required dependencies for Akash Network are Akash Software, hostname operator, network policy, and Ingress NGINX. + +* Clicking "No" will install the Akash Network dependencies on the server. +* Clicking "Yes" indicates that all dependencies are already installed on the server and skips the Akash installation process. + +## Step 4: Import Akash Wallet + +You need to import a wallet to be able to run your provider as well as to receive lease payouts in AKT. + +![](../../../../assets/importWallet.png) + +There are two ways to import your Akash wallet, namely: + +1. Praetor Mode(Recommended) + +![](../../../../assets/praetorMode.png) + +Praetor will verify a seed phrase for an existing account and create a Keystore file in your server. + +**Input** +* Seed Phrase: Wallet Seed phrase (e.g. apple create carpet grain juice) +* Password: 8 letter password of your choice. The app will use the password to encrypt the Keystore file. + +> IMPORTANT! Praetor uses end-to-end encryption on both your password and seed phrase, so you can rest assured that they are safe. That said, if you don’t want to provide your seed phrase here, you can switch to manual mode by clicking on the “Switch to Manual Mode” button. + +2. Manual Mode + +![](../../../../assets/manualMode.png) + +Run the following steps on your server: + +(i) Login to the control machine using the username you used in the **Step 2** + +(ii) Create a Keyring file using the command + +`~/bin/akash — keyring-backend file keys add wallet_name — recover` + +(iii) Enter your mnemonic seed phrase and password + +(iv) Run the following command and enter the same passphrase you have used in (ii) + +`echo {passphrase} > ~/.praetor/wallet_phrase_password.txt` + +## Step 5a: Provider Configuration + +![](../../../../assets/providerConfig.png) + +You one step are closer to becoming a provider on the Akash Network. + +On the `Provider Configuration` page, provide your Domain name and Organization Name, after which you then click "Next." + + +**Input** + +* Domain Name: Please enter your domain name. Please make sure you have access to the domain name as you'll need the DNS details later on. + +* Organization Name: Choose a unique name for your machine on the Akash Network (e.g. Praetor App). + +## Step 5b: Provider Pricing + + +![](../../../../assets/providerPricing.png) + +On the "Provider Pricing" page, you would be required to enter your system configuration. Praetor will use the information provided to generate a server certificate, aand turn on your provider service on Akash. + +Under advanced settings, you can set the pricing you wish to lease out your machine. It would also allow you to see the estimated earnings you would receive from your provider. + +**Input** + +* CPU Scale Bid Price: CPU scale pricing in USD per thread per month. +* Memory Scale Bid Price: Memory scale pricing in USD per GB per month. +* Storage Scale Bid Price: Storage scale pricing in USD per GB per month. +* Persistent Storage Scale Bid Price: Persistent Storage scale pricing in USD per GB per month. + +**Advanced Settings** + +* IP Scale Price: IP Scale price in USD per IP per month. +* Endpoint Scale Bid Price: Endpoint pricing in USD per porth per month. +* Bid Deposit: Bid deposit in uakt (e.g. 5000000 uakts = 5 AKTs). + +## Step 5c: Provider Attributes + +![](../../../../assets/providerAttributes.png) + +On the "Provider Attributes" page, you can add custom attributes to your provider. To do so, you would need to enter the attributes as a key-value pair, and then click on the "Next" button. + +> NOTE! Adding extra attributes may incur additional charges. + +Once you have filled in all the necessary information, click on "Next". The process of becoming provider on chain will then begin. + +![](../../../../assets/creatingScript.png) + +Wait a few minutes as the progress screen keeps you updated as Praetor runs a script to make you an Akash provider. + +![](../../../../assets/congratsScreen.png) + +Once the process is completed you'll be redirected to a page congratulating you on became a provider on Akash Network. + +## Step 6: Port & DNS Configuration + +All the ports listed in the port table have to open for 0.0.0.0(Anywhere IPv4). + +Ensure your provider domain and ingress domain point to the correct IP Address shown in the image below. + +![](../../../../assets/portDNS.png) + +## Step 7: Akash Audit + +Akash is audited by security professionals trusted by the Akash community. They are responsible for auditing providers' technical proficiency so as to provide ansurance to consumers about the minimum quality of service you can provide. + +![](../../../../assets/akashAudit.png) + +To begin the auditing process, click on the "Apply for Audit" button as shown in the image above. +You would then be required to provide basic information about your provider. + +![](../../../../assets/applyAudit.png) + +Complete the form and submit. You may also decide to skip the audit process if you want to, but that means you would not be considered a reliable provider by most potential customers. + + +## Step 8: Dashboard + +![](../../../../assets/dashboard.png) + +Congratulations! You are now a provider, and should be able to receive leases on your machine. The Dashboard will provide information about your machine's server statistics, as well as show hactive, available, and pending resources. + +![](../../../../assets/providerSettings.png) + +Click on "Provider Settings" if you want to modify various settings for your provider. These include attributes, pricing, domain name, provider url and provider node. You can also restart or upgrade your provider,as well as send a message to your deployers. + +![](../../../../assets/providerDeployments.png) + +Click on "Provider Deployments" to see active and inactive deployments in your provider. + +## Support + +If you have any issues or trouble getting the provider machine up and running, you may reach out to the [Praetor](https://praetorapp.com) team on [Discord](https://discord.com/invite/uzUCHTF93D) or [Twitter/X](https://x.com/praetor_app). + + + + + + + + + + diff --git a/src/content/Docs/deployments/praetor-app/akash-provider/single-server-provider/index.mdx b/src/content/Docs/deployments/praetor-app/akash-provider/single-server-provider/index.mdx new file mode 100644 index 00000000..9c1e9f39 --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/akash-provider/single-server-provider/index.mdx @@ -0,0 +1,181 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 6 +title: "Single Server Provider" +linkTitle: "Single Server Provider" +--- + +# Single Server Provider + +If you have a single server and wish to become a cloud provider on the Akash Network, this guide will help you set up Kubernetes and become an Akash provider using the Praetor App. + +**Prerequisites** + +* Keplr Wallet: Ensure the Keplr wallet extension is enabled in your web browser. + +* Akash Wallet: You need at least 5 AKT in your Akash wallet to become a provider. +* Domain Name: A valid domain name is required to make DNS changes and point it to your server's IP address. + +**GPU Testnet** + +If you're joining the Testnet, select "Testnet" from the dropdown. Note that only the latest Nvidia GPUs are currently supported by the Akash Network. + + +## Step 1: Praetor App Login + +1. Access Praetor App: + +![](../../../../assets/praetor-app-login.jpg) + + +* Go to the [Praetor Application](https://akash.praetorapp.com/) to begin the setup. + + + +2. Connect Wallet: + +![](../../../../assets/connect-keplr-wallet.jpg) + +* Click "Connect" and connect your Akash wallet using the Keplr extension. + +* Select "Testnet" if applicable. + + +3. Authorize Connection: + +![](../../../../assets/sign-message.jpg) + +* Approve the connection request from Keplr to connect your wallet to Praetor App. + +* Sign the message in Keplr to secure communication with the backend. + + +4. Server Provisioning: + +![](../../../../assets/kubernetesBuild.png) + +* Select the number of servers to provide to Akash. For a single server, select "1 Server". + + +## Step 2: Server Access + +1. Server Details: + +![](../../../../assets/serverAccess.png) + +> NOTE!: If you have a GPU then select "Yes" and you will see two new options for your GPU selection. Please choose the appropriate answer and click "Next". + +* Provide your server's hostname (IP or web address without HTTP/HTTPS). + +* Enter the username (e.g., root, admin) and either the login password or upload the SSH private key file. + +2. Install Dependencies: + +![](../../../../assets/installDependencies.png) + +* The application will access your server to install Kubernetes, Akash software, and necessary dependencies. Ensure SSH port 22 is open. + +## Step 3: Import Akash Wallet + +You need to import a wallet to be able to run your provider as well as to receive lease payouts in AKT. + +![](../../../../assets/importWallet.png) + +There are two ways to import your Akash wallet, namely: + + +1. Praetor Mode (Recommended): + +![](../../../../assets/praetorMode.png) + +* Input your wallet seed phrase and password. The app will verify the seed phrase and create a keystore file on your server. + + +> IMPORTANT! Praetor uses end-to-end encryption on both your password and seed phrase, so you can rest assured that they are safe. That said, if you don’t want to provide your seed phrase here, you can switch to manual mode by clicking on the “Switch to Manual Mode” button. + + +2. Manual Mode: + +![](../../../../assets/manualMode.png) + +* Log in to your server. + +* Use the command `~/bin/akash — keyring-backend file keys add wallet_name — recover` to create a keyring file. + +* Enter your seed phrase and password, run ```echo {passphrase} > ~/.praetor/wallet_phrase_password.txt```. + + +## Step 4a: Provider Configuration + + +![](../../../../assets/providerConfig.png) + + +* Domain Name: Enter your domain name. + +* Organization Name: Provide a unique name representing your machine on Akash Network. + +## Step 4b Provider Pricing + +![](../../../../assets/providerPricing.png) + +* CPU, Memory, Storage Pricing: Set your pricing in USD per month for each resource. + +* Advanced Settings: Configure additional pricing for IPs, endpoints, and bid deposits in uakt (e.g. 5000000 uakts = 5 AKTs). + +## Step 4c Provider Attributes + +![](../../../../assets/providerAttributes.png) + +* Custom Attributes: Add any custom attributes in key-value pairs. + +> NOTE! Adding extra attributes may incur additional charges. + +![](../../../../assets/creatingScript.png) + +Wait a few minutes as the progress screen keeps you updated as Praetor runs a script to make you an Akash provider. + +![](../../../../assets/congratsScreen.png) + +Once the process is completed you'll be redirected to a page congratulating you on became a provider on Akash Network. + + +## Step 5: Port & DNS Configuration + +![](../../../../assets/portDNS.png) + +* Ensure all required ports are open for IPv4 (0.0.0.0). + +* Update your DNS settings to point your domain to the correct IP address shown in the image above. + + +## Step 6: Akash Audit + + +![](../../../../assets/akashAudit.png) + +* Apply for Audit: Provide basic information to apply for an Akash audit. + +![](../../../../assets/applyAudit.png) + +* Skip Audit: You can choose to skip the audit and proceed to the dashboard. + +## Step 7: Dashboard + +![](../../../../assets/dashboard.png) + +* Dashboard Overview: Monitor your server's statistics, including active, available, and pending resources. + +![](../../../../assets/providerSettings.png) + +* Provider Settings: Modify settings, restart, or upgrade your provider. + +![](../../../../assets/providerDeployments.png) + +* Provider Deployments: View and manage active and inactive deployments. + +## Support + +If you have any issues or trouble getting the provider machine up and running, you may reach out to the [Praetor](https://praetorapp.com) team on [Discord](https://discord.com/invite/uzUCHTF93D) or [Twitter/X](https://x.com/praetor_app). + diff --git a/src/content/Docs/deployments/praetor-app/akash-provider/sudo-user-reqs/index.mdx b/src/content/Docs/deployments/praetor-app/akash-provider/sudo-user-reqs/index.mdx new file mode 100644 index 00000000..d89efe99 --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/akash-provider/sudo-user-reqs/index.mdx @@ -0,0 +1,45 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 6 +title: "Sudo User Requirements" +linkTitle: "Sudo User Requirements" +--- + +# Sudo User Requirements + +This document explains how to grant sudo rights to a user before using the Praetor App. + +## Steps to Grant Sudo Rights + +1. Connect to Your Server + +First, connect to your server using SSH. + +2. Edit the Sudoers File + +After logging in to the server, type the following command: + +`sudo visudo` + +This command opens the sudoers file for editing. + +3. Update the Sudoers File + +Locate the following lines in the sudoers file and update them as shown to enable sudo access for the current user: + +``` +%admin ALL=(ALL) NOPASSWD: ALL +%sudo ALL=(ALL:ALL) NOPASSWD: ALL + ALL=(ALL) NOPASSWD: ALL + +``` + +Replace `` with the username you wish to grant sudo rights to, if it is not already an admin or root user. For example, if the user is `praetor`, the line should read: + +``` +praetor ALL=(ALL) NOPASSWD: ALL + +``` + +![](../../../../assets/praetorRoot.png) diff --git a/src/content/Docs/deployments/praetor-app/what-is/index.mdx b/src/content/Docs/deployments/praetor-app/what-is/index.mdx new file mode 100644 index 00000000..1787648e --- /dev/null +++ b/src/content/Docs/deployments/praetor-app/what-is/index.mdx @@ -0,0 +1,18 @@ +--- +categories: ["Praetor App"] +tags: ["Praetor App"] +weight: 5 +title: "What is Praetor App?" +linkTitle: "What is Praetor App?" +--- + +# What is Praetor App? + +Praetor App simplifies the process of becoming a cloud provider for the Akash Network. Instead of using a Command-line Interface, you can manage everything through our user-friendly interface. Once you set up as a provider, deployers who choose your services will pay you in AKT. + +With Praetor App, you can offer a single server or multiple servers, supporting operating systems like Ubuntu, Debian, and CentOS. + +Got underutilized Kubernetes? You can also integrate it with the Akash Network through Praetor App. Our app helps you configure your existing Kubernetes setup for Akash Network compatibility and initiates the Provider Service necessary to accept bids and manifests. + +Have questions or need assistance? You may reach out to us on [Discord](http://discord.gg/uzUCHTF93D). +