Tag

CPU

Cloudmos Provider Dashboard: Choose the Best Akash Network Provider

By | Akash | No Comments
Cloudmos Provider Dashboard
Compare performance and reliability of Akash Network providers with Cloudmos real-time dashboard.

As the demand for decentralized cloud services continues to grow, the Akash Network has emerged as one of the leading platforms for deploying and hosting decentralized applications. With its unique features and user-friendly interface, the Akash Network has made it easier than ever for developers and businesses to build and host their applications on a decentralized cloud.

One of the key factors that contribute to the success of the Akash Network is the availability of a wide range of providers on the platform. These providers are responsible for offering the necessary resources, including CPU, memory, disk space, and uptime, to support the applications hosted on the Akash Network.

To ensure that users have the best possible experience on the platform, Cloudmos, a leading provider of decentralized cloud services, has launched a new provider dashboard that makes it easy to check the performance and reliability of providers on the Akash Network.

In this blog post, we will take a closer look at the new provider dashboard on Cloudmos deploy and explore how it can help users make informed decisions when choosing a provider on the Akash Network.

The Importance of Choosing the Right Provider

Choosing the right provider is crucial when it comes to deploying and hosting applications on the Akash Network. The performance and reliability of the provider can have a significant impact on the performance and uptime of the application.

There are several factors that users should consider when choosing a provider on the Akash Network, including:

  • CPU: The CPU is responsible for executing instructions and performing calculations. The higher the CPU, the faster the application can process data.
  • Memory: The memory is responsible for storing data that the application needs to access frequently. The more memory available, the faster the application can access data.
  • Disk Space: The disk space is responsible for storing the data and files required by the application. The more disk space available, the more data the application can store.
  • Uptime: Uptime refers to the amount of time that the provider is available and accessible. Providers with higher uptime are more reliable and less likely to experience downtime.

The New Provider Dashboard on Cloudmos Deploy

To help users choose the right provider on the Akash Network, Cloudmos has launched a new provider dashboard that provides real-time information on the performance and reliability of providers on the platform.

The dashboard provides users with a range of information, including:

  • CPU: The dashboard displays the total CPU available on the Akash Network, as well as the CPU available from the user’s selected providers. Users can easily compare the CPU available from different providers to make informed decisions.
  • Memory: The dashboard displays the total memory available on the Akash Network, as well as the memory available from the user’s selected providers. Users can easily compare the memory available from different providers to ensure that their applications have the necessary resources to perform optimally.
  • Disk Space: The dashboard displays the total disk space available on the Akash Network, as well as the disk space available from the user’s selected providers. Users can easily compare the disk space available from different providers to ensure that their applications have the necessary space to store data and files.
  • Uptime: The dashboard displays the uptime of each provider over the past seven days. Users can easily compare the uptime of different providers to ensure that they choose a provider with a high level of reliability.

In addition to these key metrics, the dashboard also allows users to search for providers based on location, audited status, and favorite status. Users can also sort providers by name, location, uptime, active leases, and more.

How to Use the Provider Dashboard on Cloudmos Deploy

Using the provider dashboard on Cloudmos Deploy is simple and straightforward. Here’s how to get started:

Step 1: Log in to your Cloudmos account and navigate to the provider dashboard.

Step 2: Select the providers that you want to compare by clicking on the checkboxes next to their names. You can select up to 10 providers at a time.

Step 3: Use the filters to narrow down your search based on location, audited status, and favorite status.

Step 4: Sort the providers by name, location, uptime, active leases, CPU, memory, or disk space by clicking on the respective column header.

Step 5: Review the data displayed on the dashboard to compare the performance and reliability of the selected providers.

Step 6: Use the information to make an informed decision when choosing a provider for your application.

The Benefits of Using the Provider Dashboard on Cloudmos Deploy

The provider dashboard on Cloudmos Deploy provides several benefits to users looking to deploy and host applications on the Akash Network. These benefits include:

  1. Real-time information: The dashboard provides real-time information on the performance and reliability of providers on the Akash Network. This information is updated regularly, ensuring that users have access to the most up-to-date data.
  2. Easy comparison: The dashboard allows users to compare the performance and reliability of multiple providers at once, making it easy to make informed decisions when choosing a provider for their application.
  3. User-friendly interface: The dashboard is designed with a user-friendly interface that makes it easy to navigate and understand the data presented.
  4. Customizable filters: The dashboard includes customizable filters that allow users to narrow down their search based on location, audited status, and favorite status.
  5. Detailed metrics: The dashboard provides detailed metrics on CPU, memory, disk space, and uptime, allowing users to make data-driven decisions when choosing a provider.
  6. Increased transparency: The provider dashboard increases transparency on the Akash Network by providing users with access to real-time data on provider performance and reliability.

Conclusion

The provider dashboard on Cloudmos Deploy is an essential tool for users looking to deploy and host applications on the Akash Network. The dashboard provides real-time information on the performance and reliability of providers, allowing users to make informed decisions when choosing a provider for their application.

By using the customizable filters and sorting options on the dashboard, users can quickly and easily compare the performance and reliability of multiple providers, ensuring that they choose the best provider for their needs.

Overall, the provider dashboard on Cloudmos Deploy is an excellent addition to the Akash Network, providing increased transparency and making it easier than ever for users to deploy and host their applications on a decentralized cloud.

Mastodon Hosting on Akash Network: Deploy in Minutes for Less Than $10/mo

By | Akash | No Comments

Why Akash?

This comprehensive guide will show you how to unlock the full potential of hosting Mastodon on Akash. Mastodon is an open-source social network platform that provides a powerful and secure way to communicate and collaborate with others. Akash is a decentralized cloud computing platform that allows users to deploy and manage distributed applications and services. By combining these two powerful technologies, you can benefit from a reliable, secure, and cost-effective hosting solution. This guide will provide you with the necessary information to get started and maximize the benefits of hosting Mastodon on Akash.

Requirements:

Setup Overview:

  1. Create secrets/keys locally and configure Mailjet for a domain/email.
  2. Update required variables in YAML
  3. Deploy in Cloudmos

On your local machine

We need to first create secrets and vapid keys before deploying. Start by copy and pasting the YAML below into your favorite text editor. We need to update the variables.

To create secrets you need to run a Dockerfile locally:

docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon generate-secret

Create 3 secrets and fill in PASSWORD=, SECRET_KEY_BASE=, and OTP_SECRET=

Now, for Vapid Keys Run

docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon generate-vapid

and fill in VAPID_PRIVATE_KEY= and VAPID_PUBLIC_KEY= with the values.

Mailjet

You need to setup a free Mailjet account to enable the SMTP server as configured below. Once you account is created, add a domain and verify it. Then get your API key credentials and update them in the YAML as required. You cannot register/verify a user without a working SMTP server! Update SMTP_FROM_ADDRESS=, SMTP_LOGIN=, and SMTP_PASSWORD=.

Cloudmos Deploy

Create Deployment

Using Cloudmos Deploy create a new blank deployment and copy and paste the YAML with the updated variables into the online editor.

First Run

When you run the app for the first time, it will create the databases and start the web server. However, a configuration change is needed, and it may take up to three minutes for the process to complete. Please be patient and let the process finish. If you click on the URI at this point you will see in the logs :

mastodon: [ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked host: o0ido8nb6lc8v04816ipu8vhss.ingress.america.computer 

Go to Cloudmos Deploy and find the deployment URI. This URI will be used to update the LOCAL_DOMAIN= and WEB_DOMAIN= environmental variables.

Edit the deployment YAML and locate the LOCAL_DOMAIN= and WEB_DOMAIN= environmental variables.

Update these variables with the full URI you copied from Cloudmos Deploy.

Click on “Update” to apply the changes to your deployment. Wait for the pod to be restarted. This may take a couple of minutes, so please be patient. Once the pod is restarted, try to access the URI. You may see an HTTPS warning, but it is safe to ignore it and proceed to the app. Finally, configure your DNS settings to point your domain to the URI.

version: "2.0"

services:
  mastodon:
    image: linuxserver/mastodon
    expose:
      - port: 443
        as: 443
        to:
          - global: true
      - port: 80
        as: 80
        to:
          - global: true
    env:
      - PUID=1000
      - PGID=1000
      - AWS_ACCESS_KEY_ID=
      - AWS_SECRET_ACCESS_KEY=
      - DB_HOST=db
      - DB_NAME=mastodon
      - DB_PASS=mastodon
      - DB_POOL=5
      - DB_PORT=5432
      - DB_USER=mastodon
      - ES_ENABLED=false
      - ES_HOST=es
      - ES_PASS=elastic
      - ES_PORT=9200
      - ES_USER=elastic
      - PASSWORD="" #Generated from (docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon generate-secret)
      - LOCAL_DOMAIN= #Full URI used after deployment
      - OTP_SECRET="" #Generated from (docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon generate-secret)
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - S3_ALIAS_HOST=
      - S3_BUCKET=
      - S3_ENABLED=false
      - SECRET_KEY_BASE=
      - SIDEKIQ_DEFAULT=false
      - SIDEKIQ_ONLY=false
      - SIDEKIQ_QUEUE=
      - SIDEKIQ_THREADS=5
      - SMTP_FROM_ADDRESS=mastodon@test.com #Signup for mailjet.com and setup email
      - SMTP_LOGIN= #mailjet API key
      - SMTP_PASSWORD= #mailjet secret 
      - SMTP_PORT=25
      - SMTP_SERVER=in-v3.mailjet.com
      - TZ=Etc/UTC
      - VAPID_PRIVATE_KEY="" #Generated from auth container (docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon generate-vapid)
      - VAPID_PUBLIC_KEY="" #Generated from auth container command
      - WEB_DOMAIN= #Full URI used after deployment
    depends_on:
      - db
      - redis
  redis:
    image: redis:7-alpine
    expose:
      - port: 6379
        proto: tcp
        to:
          - service: mastodon
  db:
    image: postgres:14-alpine
    expose:
      - port: 5432
        proto: tcp
        to:
          - service: mastodon
    env:
      - POSTGRES_HOST_AUTH_METHOD=trust
      - POSTGRES_PASSWORD=mastodon
      - POSTGRES_DB=mastodon
      - POSTGRES_USER=mastodon
profiles:
  compute:
    mastodon:
      resources:
        cpu:
          units: 4.0
        memory:
          size: 2.5Gi
        storage:
          size: 16Gi
    redis:
      resources:
        cpu:
          units: 1
        memory:
          size: 1Gi
        storage:
          - size: 1Gi
    db:
      resources:
        cpu:
          units: 1
        memory:
          size: 1Gi
        storage:
          - size: 1Gi

  placement:
    akash:
      attributes:
        host: akash
      signedBy:
        anyOf:
          - "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
          - "akash18qa2a2ltfyvkyj0ggj3hkvuj6twzyumuaru9s4"
      pricing:
        mastodon:
          denom: uakt
          amount: 100000
        redis:
          denom: uakt
          amount: 1000
        db:
          denom: uakt
          amount: 1000

deployment:
  mastodon:
    akash:
      profile: mastodon
      count: 1
  redis:
    akash:
      profile: redis
      count: 1
  db:
    akash:
      profile: db
      count: 1      

Extra Resources

https://hub.docker.com/r/linuxserver/mastodon