Filebase
Search…
Akash Network
Learn about the Akash network and their partnership with Filebase.
A core goal of decentralized web, also known as dWeb, is to help people and organizations regain control of their computing and storage.
To break down barriers when it comes to building the dWeb, Akash Network, an open-source, decentralized cloud has teamed up with Filebase.

What is Akash?

Akash is an open source cloud platform that lets you quickly deploy a Docker container to any cloud provider of your choice for less than the cost of AWS, right from the command-line.
Akash's typical workflow is as follows:
  • Define your Docker image, CPU, Memory, and Storage in a deploy.yaml file.
  • Set your price, receive bids from providers in seconds, and select the lowest price.
  • Deploy your application without having to set up, configure, or manage servers.
  • Scale your application from a single container to hundreds of deployments.

What does this mean?

Access Decentralized Compute and Storage together, as one.

Through this partnership between Akash and Filebase, developers and enterprises now have the ability to pair dWeb applications with the thousands of existing backup tools, application SDKs and frameworks that they already know and love. By offering open-source dWeb compute and petabyte-scale object storage, Akash and Filebase can help to reduce cloud costs by up to 85 percent, compared to traditional cloud services.

Community Projects with Akash

Receive $100 in Akash Credit and 1TB of S3 Compatible Object Storage by visiting https://filebase.com/akash‚Äč

Below is a short setup guide that will help you to quickly configure and setup Akash for success. For more questions please visit the Akash documentation site.

1. Setup Akash

  • Set the environment variables in the deploy.yml and deploy on Akash.
  • Use the URL and port Akash gives you to connect to the Postgres server with the credentials you provided in the environment variables. For example cluster.ewr1p0.mainnet.akashian.io:31234

2. Using Akash with an App Container

Alternatively, you can add your own app container to the deploy.yml and expose the Postgres 5432 port to your application only for a local server.
For example, your deploy.yml file would look something like:
1
services:
2
app:
3
image: myappimage:v1
4
depends_on:
5
- service: postgres
6
cron:
7
image: ghcr.io/ovrclk/akash-postgres-restore:v0.0.4
8
env:
9
- POSTGRES_PASSWORD=password
10
...
11
depends_on:
12
- service: postgres
13
postgres:
14
image: postgres:12.6
15
env:
16
- POSTGRES_PASSWORD=password
17
expose:
18
- port: 5432
19
to:
20
- service: app
21
- service: cron
Copied!

Environment variables and definitions:

1
POSTGRES_USER=postgres - your Postgres server username
2
POSTGRES_PASSWORD=password - your Postgres server password
3
POSTGRES_HOST=postgres - Postgres server host (this will be whatever you named it in deploy.yml)
4
POSTGRES_PORT=5432 - Postgres port, will be 5432 unless you aliased it in deploy.yml
5
POSTGRES_DATABASE=akash_postgres - name of your database
6
BACKUP_PATH=bucketname/path - bucket and path for your deployments (make sure directories exist first)
7
BACKUP_KEY=key - your Filebase access key
8
BACKUP_SECRET=secret - your Filebase secret key
9
BACKUP_PASSPHRASE=secret - a passphrase to encrypt your backups with
10
BACKUP_HOST=https://s3.filebase.com - the S3 backup host, this defaults to Filebase but can be any S3 compatible host
11
BACKUP_SCHEDULE=*/15 * * * * - the cron schedule for backups (defaults to every 15 minutes)
12
BACKUP_RETAIN=7 days - how many days to keep backups for
Copied!

3. Deployment

You can run the application locally using Docker Compose. Copy the .env.sample file to .env and populateRun docker-compose up to build and run the application.
Please visit the Akash documentation site or email us at [email protected] if you have any questions.
Last modified 1mo ago