- GraphQL playground will be available
- Logs will be more detailed
+
On the right side, you can see realtime information about the count of active instances of the application.
-#### ⏸️ Pause App
+### ⏸️ Pause App
If you like to make your application offline, you can pause the application. This will stop all the instances of the application and will free up the resources.
-#### ▶️ Resume App
+### ▶️ Resume App
If you like to make your application online, you can resume the application. This will start all the instances of the application and you will be able to access the application within a few seconds.
-#### 🏄♂️ Let's go through each section of the **Application Details** page.
-
-| Section | Page Link |
-|---------|-----------|
-| Deployments | [***Click Here***](/docs/dashboard/application_details/deployments) |
-| Runtime Logs | [***Click Here***](/docs/dashboard/application_details/runtime_logs) |
-| Ingress Rules | [***Click Here***](/docs/dashboard/application_details/ingress_rules) |
-| Update Source Code | [***Click Here***](/docs/dashboard/application_details/update_source_code) |
-| Environment Variables | [***Click Here***](/docs/dashboard/application_details/environment_variables) |
-| Persistent Volumes | [***Click Here***](/docs/dashboard/application_details/persistent_volumes) |
-| Deployment Configuration | [***Click Here***](/docs/dashboard/application_details/deployment_configuration) |
-| Webhook CI | [***Click Here***](/docs/dashboard/application_details/webhook_ci) |
-| Danger Zone | [***Click Here***](/docs/dashboard/application_details/danger_zone) |
\ No newline at end of file
+### 🏄♂️ Let's go through each section of the **Application Details** page.
+
+| Section | Page Link |
+| ------------------------ |------------------------------------------------|
+| Deployments | [***Click Here***](./deployments) |
+| Analytics | [***Click Here***](./analytics) |
+| Runtime Logs | [***Click Here***](./runtime_logs) |
+| Ingress Rules | [***Click Here***](./ingress_rules) |
+| Persistent Volumes | [***Click Here***](./persistent_volumes) |
+| Environment Variables | [***Click Here***](./environment_variables) |
+| Update App Source | [***Click Here***](./update_app_source) |
+| Deployment Configuration | [***Click Here***](./deployment_configuration) |
+| Webhook CI | [***Click Here***](./webhook_ci) |
+| Actions | [***Click Here***](./actions) |
+| Destroy | [***Click Here***](./destroy) |
\ No newline at end of file
diff --git a/docs/dashboard/application_details/ingress_rules.md b/docs/dashboard/application_details/ingress_rules.md
index 8d0dbc5..bd4a82a 100644
--- a/docs/dashboard/application_details/ingress_rules.md
+++ b/docs/dashboard/application_details/ingress_rules.md
@@ -1,13 +1,11 @@
---
id: ingress_rules
title: Ingress Rules
-sidebar_position: 3
+sidebar_position: 4
---
In **Ingress Rules** section, you can find out all the associated ingress rules for the application.
-
+
-To manage the ingress rules, click on `Manage Ingress Rules` button.
-
-This will take you to the **Ingress Rules** page where you can add, edit, and delete the ingress rules for the application. Check this docs for more details: [Ingress Rules](/docs/dashboard/ingress-rules).
\ No newline at end of file
+From V2, you can create or delete ingress rules for your application from this same page.
\ No newline at end of file
diff --git a/docs/dashboard/application_details/persistent_volumes.md b/docs/dashboard/application_details/persistent_volumes.md
index c8cf94e..6eb4118 100644
--- a/docs/dashboard/application_details/persistent_volumes.md
+++ b/docs/dashboard/application_details/persistent_volumes.md
@@ -1,15 +1,15 @@
---
id: persistent_volumes
title: Persistent Volumes
-sidebar_position: 6
+sidebar_position: 5
---
In **Persistent Volumes** section, you can see all the persistent volumes of the application. You can add new persistent volumes, edit existing persistent volumes, and also can delete persistent volumes.
-
+
You can choose pre-registered persistent volume and provide a mount path. After you change something, click on **`Apply Changes`** button to save the changes.
> **Mount Path** - The path where the persistent volume will be mounted inside the container of the application.
-If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can register a persistent volume by following [**this docs**](/docs/dashboard/persistent-volumes).
\ No newline at end of file
+If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can create a new persistent volume in that case by tapping on the **Create New Persistent Volume** button.
\ No newline at end of file
diff --git a/docs/dashboard/application_details/runtime_logs.md b/docs/dashboard/application_details/runtime_logs.md
index b0b3a99..f58003c 100644
--- a/docs/dashboard/application_details/runtime_logs.md
+++ b/docs/dashboard/application_details/runtime_logs.md
@@ -1,9 +1,13 @@
---
id: runtime_logs
title: Runtime Logs
-sidebar_position: 2
+sidebar_position: 3
---
In **Runtime Logs** section, you can see all the logs of the application. The logs are updated in realtime, so you don't have to refresh the page to check the latest logs.
-
\ No newline at end of file
+
+
+By default, it will show live logs. It includes logs from last 1 minute.
+
+So, from the provided dropdown, you can change the timeframe of the logs.
\ No newline at end of file
diff --git a/docs/dashboard/application_details/webhook_ci.md b/docs/dashboard/application_details/webhook_ci.md
index de5b348..a828670 100644
--- a/docs/dashboard/application_details/webhook_ci.md
+++ b/docs/dashboard/application_details/webhook_ci.md
@@ -1,14 +1,14 @@
---
id: webhook_ci
title: Webhook CI
-sidebar_position: 8
+sidebar_position: 9
---
You can manage the webhook CI of the application from the **Webhook CI** section.
This **Webhook** can be used to trigger re-deployment of the application when the source code of the application is updated.
-
+
**Regenerate Webhook Token** - You can regenerate the webhook URL by tapping on **Regenerate Webhook** button. If you have exposed the webhook URL to the public by mistake, then you can regenerate the webhook URL to make the old webhook URL invalid.
diff --git a/docs/dashboard/applications.md b/docs/dashboard/applications.md
index ba15a31..843d898 100644
--- a/docs/dashboard/applications.md
+++ b/docs/dashboard/applications.md
@@ -1,13 +1,13 @@
---
id: applications
title: 📦 Applications
-sidebar_position: 3
+sidebar_position: 6
---
In **Application List**, you can see all the applications that you have created. You can check the status of the application, last time when it was updated, and the number of instances running for that application.
-
+
You can click on **`View Details`** button to see more details about the application.
-Check out [**Application Details**](/docs/dashboard/application_details) to learn more about it.
\ No newline at end of file
+Check out [**Application Details**](./application_details) to learn more about it.
\ No newline at end of file
diff --git a/docs/dashboard/change_password.md b/docs/dashboard/change_password.md
index 6525a2c..fd894d1 100644
--- a/docs/dashboard/change_password.md
+++ b/docs/dashboard/change_password.md
@@ -1,11 +1,11 @@
---
id: change_password
title: 🔒 Change Password
-sidebar_position: 11
+sidebar_position: 15
---
-To **change your password**, you can click on **Change Password** button in the sidebar. You will see a form like this:
+To **change your password**, you can click on `Administration > Change Password` in the sidebar. You will see a form like this:
-
+
You need to enter your current password and new password. Then, click on **Change Password** button and your password will be changed.
\ No newline at end of file
diff --git a/docs/dashboard/deploy_new_application.md b/docs/dashboard/deploy_new_application.md
index 068f08e..669dd72 100644
--- a/docs/dashboard/deploy_new_application.md
+++ b/docs/dashboard/deploy_new_application.md
@@ -1,15 +1,13 @@
---
id: deploy_new_application
title: 🔨 Deploy New Application
-sidebar_position: 2
+sidebar_position: 3
---
-### 📝 Pre-requisites
-Deploying with SwiftWave is a breeze – just bring your application's source code, and SwiftWave handles everything else.
-**SwiftWave** effortlessly accommodates various application sources:
-- 📦 Git Repository
-- 🐳 Docker Image
+In **SwiftWave** you can deploy your application from various sources.
+- 📦 Git Repository (Supports both HTTP and SSH)
+- 🐳 Docker Image Repository
- If your code isn't on a Git or Image Repository, worry not! Simply choose your code folder and upload it. 📂
### 🚀 Deploy Application
@@ -17,20 +15,20 @@ Deploying with SwiftWave is a breeze – just bring your application's source co
2. Choose your application source (Git Repository, Docker Image, or Upload Code Folder) option.
3. Fill in the required details.
4. Click on `Generate Configuration` button.
-5. You can choose to edit generated Dockerfile by clicking on `View/Modify Dockerfile` button.
+5. You can choose to edit generated Dockerfile by clicking on `View/Modify Dockerfile` button. If you feel it detected some wrong services, you can change the detected service and choose another template.
6. Edit Build Arguments, if required.
-7. Click on `Confirm & Proceed to Next Step` button.
-8. At top, you can configure no of application instances you require. (You can also configure this later.)
-9. Configure your application's environment variables. (You can also configure this later.)
-10. You can also configure persistent storage for your application. (You can also configure this later.)
-11. Click on `Confirm & Proceed to Next` button.
-12. Click on `Click to Deploy` button.
+7. Put the command, if you need to override the default command of dockerfile.
+8. Click on `Confirm & Proceed to Next Step` button.
+9. At top, you can configure no of application instances you require. (You can also configure this later.)
+10. Configure your application's environment variables. (You can also configure this later.)
+11. You can also configure persistent storage for your application. (You can also configure this later.)
+12. Click on `Click to Confirm & Deploy` button.
13. Your application will be deployed in a few minutes. 🚀
14. You can check the build logs and status in the same page.
### 📚 Next Steps
-- [**How to check details and manage a deployed application**](/docs/dashboard/application_details/)
-- [**How to expose application to internet ?**](/docs/dashboard/ingress-rules)
-- [**How to configure persistent storage ?**](/docs/dashboard/application_details/persistent_volumes)
-- [**How to configure environment variables ?**](/docs/dashboard/application_details/environment_variables)
+- [**How to check details and manage a deployed application**](./application_details/)
+- [**How to expose application to internet ?**](./ingress-rules)
+- [**How to configure persistent storage ?**](./application_details/persistent_volumes)
+- [**How to configure environment variables ?**](./application_details/environment_variables)
diff --git a/docs/dashboard/deploy_stack.md b/docs/dashboard/deploy_stack.md
new file mode 100644
index 0000000..517b08d
--- /dev/null
+++ b/docs/dashboard/deploy_stack.md
@@ -0,0 +1,35 @@
+---
+id: deploy_stack
+title: 🔨 Deploy Stack
+sidebar_position: 4
+---
+
+
+
+In **SwiftWave**, you have also support to deploy multiple applications using stack file.
+
+This stack file has same format as docker stack file. Still it doesn't support all the features of docker stack file.
+
+#### Available Features
+
+| Name | Supported |
+| --------------------- | --------- |
+| services | Yes |
+| image name | Yes |
+| deploy mode | Yes |
+| command | Yes |
+| replicas | Yes |
+| volumes | Yes |
+| environment variables | Yes |
+| cap_add | Yes |
+| sysctls | Yes |
+| ports | No |
+| networks | No |
+| depends_on | No |
+| healthcheck | No |
+
+:::tip
+
+You can use ingress rules to expose your application to internet.
+
+:::
\ No newline at end of file
diff --git a/docs/dashboard/domains.md b/docs/dashboard/domains.md
index db0e468..6036f13 100644
--- a/docs/dashboard/domains.md
+++ b/docs/dashboard/domains.md
@@ -1,12 +1,12 @@
---
id: domains
title: 🌐 Domains
-sidebar_position: 7
+sidebar_position: 10
---
In **Domains** section, you can manage all the custom domains you have added to swiftwave.
-
+
### Register a new domain
You can click on `Register New` button and fill in the required details to register a new domain.
@@ -19,12 +19,18 @@ You can click on `Delete` button to delete a domain.
> - no redirect rules linked to it
### Verify DNS
-You can click on `Verify DNS` button to verify if domain is correctly pointing to swiftwave.
-> Note: You shouldn't use any DNS proxy service like Cloudflare, etc. for your domain. If you are using any such service, you should disable it before verifying DNS.
+You can click on `Verify DNS` button to verify if domain is correctly pointing to the proxy server.
+
+:::tip
+
+- If you are using cloudflare as your DNS provider, it is recommended to use DNS only mode while mapping your domain to the proxy server IP.
+- If you want to use Cloudflare Proxy Mode, go to `Domain SSL/TLS Mode` section and mark `Encryption Mode` to `Full`. After this, all your application hosted on swiftwave should use `https` protocol in all ingress rules.
+
+:::
### Issue SSL Certificate 🛡️
Swiftwave has Let's Encrypt integration. You can issue a SSL certificate for your domain by clicking on `Issue SSL` button.
### SSL Auto Renewal
-Swiftwave does not support SSL auto renewal yet. You will have to manually renew your SSL certificate every 90 days. You can do so by clicking on `Issue SSL` button. We will be adding SSL auto renewal feature soon.
+From V2, Swiftwave supports SSL auto renewal. You don't need to worry about renewing your SSL certificate manually.
diff --git a/docs/dashboard/git-credentials.md b/docs/dashboard/git-credentials.md
index f98a487..7dd618b 100644
--- a/docs/dashboard/git-credentials.md
+++ b/docs/dashboard/git-credentials.md
@@ -1,14 +1,40 @@
---
id: git-credentials
title: 🐙 Git Credentials
-sidebar_position: 5
+sidebar_position: 8
---
In **Git Credentials** section, you can check all the saved Git Credentials. You can use these credentials while deploying an application from a Git Repository.
-
+
+
+Git Credentials vault now supports both HTTP and SSH authentication key.
**You can**
- **Add** a new Git Credential by clicking on `Add New` button.
+- **View** a Git Credential by clicking on `View Details` button.
+- **Edit** a Git Credential by clicking on `Edit Details` button.
- **Delete** a Git Credential by clicking on `Delete` button.
- > Note : You can only delete a Git Credential if it is not being used by any application.
\ No newline at end of file
+ > Note : You can only delete a Git Credential if it is not being used by any application.
+
+#### Add HTTP Credential
+
+
+
+Choose the type as `HTTP` and fill in the required details.
+
+#### Add SSH Credential
+
+
+
+Choose the type as `SSH` and fill in the required details.
+- If you like to use your own private key, put that in OpenSSH format in the `Private Key` field.
+- Else, leave that field empty and a new key will be generated for you.
+
+**View the public key**
+
+To view the public key, hit the `View Details` button after creating your SSH Git credential.
+
+
+
+You can add this key to your GitHub account and use it to access the private repository.
\ No newline at end of file
diff --git a/docs/dashboard/image-credentials.md b/docs/dashboard/image-credentials.md
index baf99d2..3d58820 100644
--- a/docs/dashboard/image-credentials.md
+++ b/docs/dashboard/image-credentials.md
@@ -1,14 +1,15 @@
---
id: image-credentials
title: 🐳 Image Credentials
-sidebar_position: 6
+sidebar_position: 9
---
In **Image Credentials** section, you can check all the saved Image Registry Credentials. You can use these credentials while deploying an application from a Image Repository.
-
+
**You can**
- **Add** a new Image Registry Credential by clicking on `Add New` button.
+- **Edit** an existing Image Registry Credential by clicking on `Edit Details` button.
- **Delete** a Image Registry Credential by clicking on `Delete` button.
> Note : You can only delete a Image Registry Credential if it is not being used by any application.
\ No newline at end of file
diff --git a/docs/dashboard/index.md b/docs/dashboard/index.md
index 5062974..31cbd52 100644
--- a/docs/dashboard/index.md
+++ b/docs/dashboard/index.md
@@ -10,27 +10,31 @@ sidebar_position: 5
justifyContent: 'center',
marginBottom: '2rem'
}}>
- 
+ 
-SwiftWave Dashboard is a web-based interface to manage your applications, domains and all. It's the main management interface for SwiftWave.
+SwiftWave Dashboard is a web-based interface for controlling all resources, including apps, domains, persistent volumes, and more. It is SwiftWave's main management interface.
-> 📌 Note: SwiftWave Dashboard comes pre-bundled with SwiftWave. You don't need to install it separately.
## Sections of Dashboard
-| Section | Description | Link |
-| --- | --- | --- |
-| 🔒 Log In | Log in to SwiftWave Dashboard | [***Click Here***](/docs/dashboard/log_in) |
-| 🔨 Deploy New Application | Deploy new application on your server | [***Click Here***](/docs/dashboard/deploy_new_application) |
-| 📦 Applications | List of all applications deployed on your server & manage them | [***Click Here***](/docs/dashboard/applications) |
-| 📦 Persistent Volumes | List of all persistent volumes created on your server & manage them | [***Click Here***](/docs/dashboard/persistent-volumes) |
-| 🐙 Git Credentials | Manage git credentials for your applications | [***Click Here***](/docs/dashboard/git-credentials) |
-| 🐳 Image Credentials | Manage docker image credentials for your applications | [***Click Here***](/docs/dashboard/image-credentials) |
-| 🌐 Domains | Manage custom domains, SSL for your applications | [***Click Here***](/docs/dashboard/domains) |
-| 🚪 Ingress Rules | Manage exposed domains and routes for your applications | [***Click Here***](/docs/dashboard/ingress-rules) |
-| 🔄 Redirect Rules | Manage domain redirection and HTTPS redirection for your applications | [***Click Here***](/docs/dashboard/redirect-rules) |
-| 👥 Manage Users | Manage admin users for your hosted SwiftWave instance | [***Click Here***](/docs/dashboard/manage-users) |
-| 🔒 Change Password | Change password for currently logged In user | [***Click Here***](/docs/dashboard/change_password) |
+| Section | Description | Link |
+| ---------------------------- | --------------------------------------------------------------------- |----------------------------------------------|
+| 🔒 Log In | Log in to SwiftWave Dashboard | [***Click Here***](./log_in) |
+| 🏪 Swiftwave App Store | Install apps in one click from the SwiftWave App Store | [***Click Here***](./swiftwave_app_store) |
+| 🔨 Deploy Application | Deploy new application on your server | [***Click Here***](./deploy_new_application) |
+| 🔨 Deploy Stack | Deploy application using stack file | [***Click Here***](./deploy_stack) |
+| 📦 Persistent Volumes | List of all persistent volumes created on your server & manage them | [***Click Here***](./persistent-volumes) |
+| 📦 Applications | List of all applications deployed on your server & manage them | [***Click Here***](./applications) |
+| 📦 Application Details | View details of an application | [***Click Here***](./application_details) |
+| 🐙 Git Credentials | Manage git credentials for your applications | [***Click Here***](./git-credentials) |
+| 🐳 Image Registry Credentials | Manage docker image credentials for your applications | [***Click Here***](./image-credentials) |
+| 🌐 Domains | Manage custom domains, SSL for your applications | [***Click Here***](./domains) |
+| 🚪 Ingress Rules | Manage exposed domains and routes for your applications | [***Click Here***](./ingress-rules) |
+| 🔄 Redirect Rules | Manage domain redirection and HTTPS redirection for your applications | [***Click Here***](./redirect-rules) |
+| 🖥️ Manage Servers | Manage the onboarded servers for your SwiftWave instance | [***Click Here***](./manage-servers) |
+| 👥 Manage Users | Manage admin users for your hosted SwiftWave instance | [***Click Here***](./manage-users) |
+| 🔒 Change Password | Change password for currently logged In user | [***Click Here***](./change_password) |
+| 🖥️ Manage System | Manage the system settings for your SwiftWave instance | [***Click Here***](./manage-system) |
diff --git a/docs/dashboard/ingress-rules.md b/docs/dashboard/ingress-rules.md
index f88074c..20a7614 100644
--- a/docs/dashboard/ingress-rules.md
+++ b/docs/dashboard/ingress-rules.md
@@ -1,12 +1,12 @@
---
id: ingress-rules
title: 🚪 Ingress Rules
-sidebar_position: 8
+sidebar_position: 11
---
In **Ingress Rules** section you can manage your ingress rules. You can add or delete ingress rules.
-
+
### 😅 Don't know what ingress rules are ?
In layman's terms, ingress rules are the rules that will connect your domain to your application.
@@ -17,27 +17,48 @@ For example, you have an web application (named **myapp**) running on port 3000
myapp.com [https] -> myapp:3000
```
-### Add Ingress Rule
+### Add Ingress Rule for Deployed Application
To add an ingress rule, click on **Add New** button. You will see a form like this:
-
+
You can choose the protocol your application required.
- **HTTP**: You can choose any port for your application. It's recommended to use port 80 for HTTP.
- **HTTPS**: Currently, only port 443 is supported.
- > Note: To enable, **HTTPS Redirection**, you will have to create a redirect rule. You can follow [**this docs**](/docs/dashboard/redirect-rules#https-redirect) section to create a redirect rule.
+ > Note: To enable, **HTTPS Redirection**, you will have to create a redirect rule. You can follow [**this docs**](./redirect-rules#https-redirect) section to create a redirect rule.
- **TCP**: If your application relies on TCP protocol, you can choose this option. You can choose any port for your application.
> NOTE : In case of TCP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
- **UDP**: If your application relies on UDP protocol, you can choose this option. You can choose any port for your application.
> NOTE : In case of UDP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
-Then, you can choose the domain you want to connect to your application. If you don't have any domain, you can add it in [**Domains**](/docs/dashboard/domains) section.
+Then, you can choose the domain you want to connect to your application. If you don't have any domain, you can click on `Register New Domain` to add a new domain.
-**Finally**, you can choose the application you want to connect to your domain. If you don't have any application, you can deploy one by following [**this docs**](/docs/dashboard/deploy_new_application) section.
+**Finally**, you can choose the application you want to connect to your domain.
Hurrah! You have successfully created an ingress rule. Now, you can access your application via your domain.
It takes upto 1 minute to apply the changes.
-> **Note :** If you have created an ingress rule for port except 80 and 443, you will have to wait for upto ~30 seconds to apply the changes. This is because, we have to reload HAProxy or UDPProxy and other services to expose the port. You should open the port in your server's firewall too.
+> **Note :** If you have created an ingress rule for port except 80 and 443, you will have to wait for 1~2 minutes to see the effect. This is because, we have to reload HAProxy or UDPProxy and other services to expose the port. You should open the port in your server's firewall too.
+
+
+### Add Ingress Rule for External Application
+
+You can use the integrated proxy in Swiftwave to expose certain applications to the outside world if you are unable to deploy them in swiftwave for some reason.
+
+:::info
+
+That external application should use this docker overlay network > `swiftwave_network`
+
+:::
+
+For that, click on **Add New** button. In the form, you will see a label `Need to expose some external services ?`. Click on it and you will see a form like this:
+
+
+
+From here, you can type the container / service name of that external application and create an ingress rule for it.
+
+Hurrah!
+
### Delete Ingress Rule
-To delete an ingress rule, click on **Delete** button. You will see a confirmation dialog. Confirm it and your ingress rule will be deleted.
\ No newline at end of file
+To delete an ingress rule, click on **Delete** button. You will see a confirmation dialog. Confirm it and your ingress rule will be deleted.
+
diff --git a/docs/dashboard/log_in.md b/docs/dashboard/log_in.md
index 02d5698..d8ba9b8 100644
--- a/docs/dashboard/log_in.md
+++ b/docs/dashboard/log_in.md
@@ -6,17 +6,6 @@ sidebar_position: 1
When you will visit the dashboard for the first time, you will be asked to log in.
-
+
-You can log in using the credentials of the user you created while installing the application.
-
-You can also **Create New User** from the CLI (if you have access to the server where you have installed swiftwave).
-
-**Steps -**
-1. SSH into the server where you have installed swiftwave.
-2. Run the following command to create a new user.
- ```bash
- sudo swiftwave create-user --username
+ 
+
+
+
+
+From Swiftwave App Store, you can install any app in few clicks.
+
+### Steps to install any app from Swiftwave App Store
+1. Go to Swiftwave App Store
+2. Search for the app you want to install
+3. Click on the app you want to install
+4. Click the variant you want to install
+5. Click the install button
+6. Fill up the required details
+7. Configure the ingress rules. You can also ignore those by tapping on the cross icon
+8. Click on the install button
+9. That's it!
\ No newline at end of file
diff --git a/docs/development_setup.md b/docs/development_setup.md
index 38082b4..39876dc 100644
--- a/docs/development_setup.md
+++ b/docs/development_setup.md
@@ -7,87 +7,57 @@ sidebar_position: 7
Let's get started with SwiftWave Development Setup!
## 📦 Pre-requisites
-1. A Virtual Server with Debian, Ubuntu, Fedora OS or their derivatives installed.
-2. Virtual Server should have at least 1GB RAM and 1vCPU.
-3. Install curl, git, unzip and tar utilities.
+1. You need a linux system for development of SwiftWave.
+2. Install curl, git, unzip and tar utilities.
```bash
# For Debian/Ubuntu based distros:
- sudo apt install curl git unzip tar
+ sudo apt install curl git unzip tar make
# For Fedora based distros:
- sudo dnf install curl git unzip tar
+ sudo dnf install curl git unzip tar make
```
-4. Install docker (Skip this step if you already have docker installed)
+3. Install docker (Skip this step if you already have docker installed)
```bash
- curl -fsSL https://get.docker.com -o get-docker.sh
- sudo sh get-docker.sh
+ curl -fsSL https://get.docker.com | sudo bash -
```
- > 📌 Note: As RHEL doesn't support docker, SwiftWave doesn't support RHEL based distros.
-5. Install Golang by following [this guide](https://golang.org/doc/install)
-6. Install NodeJS by following [this guide](https://deb.nodesource.com/)
-7. You are all set! 🎉
+4. Install Golang by following [this guide](https://golang.org/doc/install)
+5. Install NodeJS by following [this guide](https://deb.nodesource.com/)
+6. You are all set! 🎉
## 📥 Local Installation
1. Fork and clone SwiftWave repository
```bash
git clone git@github.com:
+
+**Swiftwave's core components -**
-### 🚀 Deployment Options
-- **Source Freedom**: Deploy your app from any git source (Github, Gitlab, etc.) 🌐 (Supports public and private repositories)
-- **Container Convenience**: Deploy from any Docker image registry (Docker Hub, Github Container Registry, etc.) 🐳 (Supports public and private repositories)
-- **No Repo, No Problem**: Upload source code directly from your computer 🖥️
+- **Swiftwave Daemon** - This is the heart of the SwiftWave.
+- **HAProxy** - This is responsible for handling TCP/HTTP/HTTPS traffic, load balancing and SSL termination.
+- **UDPPRoxy** - This is [custom built tool](https://github.com/swiftwave-org/udpproxy) to handle UDP traffic.
+- **Volume Toolkit** - This is a [custom built tool](https://github.com/swiftwave-org/volume-toolkit) to perform various operations like size calculation, snapshot creation, restoration of persistent volumes, etc.
+- **Stats Ninja** - This is again a [custom built tool](https://github.com/swiftwave-org/stats-ninja) to record resource usage of server and deployed applications.
+- **App Store Metadata** - [https://github.com/swiftwave-org/app-store](https://github.com/swiftwave-org/app-store) . This contains all the metadata of one click apps.
-### ⚙️ Application Management
-- **Effortless Updates**: Update your application seamlessly with one click, no downtime ⏫
-- **Version Control**: Rollback to any previous version effortlessly with one click ⬅️
-- **Flexible Restart**: Restart your application at your convenience 🔄
-- **Scaling Made Easy**: Scale your application effortlessly with just one click 🔍
-- **Log Insight**: Easily check logs for your application 📋
-- **Backup & Restore**: Backup and restore your application with just one click 🔄
-
-### 🛣️ Traffic Control
-- **Custom Domains**: Add custom domains and auto-issue SSL certificates with just one click 🔒
-- **Traffic Routing**: Effortlessly route traffic to your application 🚦
-- **Redirect Magic**: Redirect a domain to another URL if needed ↩
\ No newline at end of file
+We will know more about each things in the next section.
\ No newline at end of file
diff --git a/docs/installation.md b/docs/installation.md
new file mode 100644
index 0000000..7d1e4b9
--- /dev/null
+++ b/docs/installation.md
@@ -0,0 +1,163 @@
+---
+id: installation
+title: ⚒️ Installation
+sidebar_position: 3
+---
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Let's get started with SwiftWave! It will not take more than 10 minutes to install SwiftWave on your server.
+
+## 📦 Pre-requisites
+
+1. A Linux System with at-least 1GB RAM and 1vCPU.
+2. Install some utilities like curl, git, unzip and tar.
+
{/* micro announcement bar */}
+
On the right side, you can see realtime information about the count of active instances of the application.
@@ -21,14 +21,14 @@ If you like to make your application online, you can resume the application. Thi
#### 🏄♂️ Let's go through each section of the **Application Details** page.
-| Section | Page Link |
-|---------|-----------|
-| Deployments | [***Click Here***](/docs/dashboard/application_details/deployments) |
-| Runtime Logs | [***Click Here***](/docs/dashboard/application_details/runtime_logs) |
-| Ingress Rules | [***Click Here***](/docs/dashboard/application_details/ingress_rules) |
-| Update Source Code | [***Click Here***](/docs/dashboard/application_details/update_source_code) |
-| Environment Variables | [***Click Here***](/docs/dashboard/application_details/environment_variables) |
-| Persistent Volumes | [***Click Here***](/docs/dashboard/application_details/persistent_volumes) |
-| Deployment Configuration | [***Click Here***](/docs/dashboard/application_details/deployment_configuration) |
-| Webhook CI | [***Click Here***](/docs/dashboard/application_details/webhook_ci) |
-| Danger Zone | [***Click Here***](/docs/dashboard/application_details/danger_zone) |
\ No newline at end of file
+| Section | Page Link |
+| ------------------------ |------------------------------------------------|
+| Deployments | [***Click Here***](./deployments) |
+| Runtime Logs | [***Click Here***](./runtime_logs) |
+| Ingress Rules | [***Click Here***](./ingress_rules) |
+| Update Source Code | [***Click Here***](./update_source_code) |
+| Environment Variables | [***Click Here***](./environment_variables) |
+| Persistent Volumes | [***Click Here***](./persistent_volumes) |
+| Deployment Configuration | [***Click Here***](./deployment_configuration) |
+| Webhook CI | [***Click Here***](./webhook_ci) |
+| Danger Zone | [***Click Here***](./danger_zone) |
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md b/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md
index 8d0dbc5..7001f5f 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md
@@ -6,8 +6,8 @@ sidebar_position: 3
In **Ingress Rules** section, you can find out all the associated ingress rules for the application.
-
+
To manage the ingress rules, click on `Manage Ingress Rules` button.
-This will take you to the **Ingress Rules** page where you can add, edit, and delete the ingress rules for the application. Check this docs for more details: [Ingress Rules](/docs/dashboard/ingress-rules).
\ No newline at end of file
+This will take you to the **Ingress Rules** page where you can add, edit, and delete the ingress rules for the application. Check this docs for more details: [Ingress Rules](../ingress-rules).
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md b/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md
index c8cf94e..89ed737 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md
@@ -6,10 +6,10 @@ sidebar_position: 6
In **Persistent Volumes** section, you can see all the persistent volumes of the application. You can add new persistent volumes, edit existing persistent volumes, and also can delete persistent volumes.
-
+
You can choose pre-registered persistent volume and provide a mount path. After you change something, click on **`Apply Changes`** button to save the changes.
> **Mount Path** - The path where the persistent volume will be mounted inside the container of the application.
-If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can register a persistent volume by following [**this docs**](/docs/dashboard/persistent-volumes).
\ No newline at end of file
+If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can register a persistent volume by following [**this docs**](../persistent-volumes).
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md b/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md
index b0b3a99..2b7f8ab 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md
@@ -6,4 +6,4 @@ sidebar_position: 2
In **Runtime Logs** section, you can see all the logs of the application. The logs are updated in realtime, so you don't have to refresh the page to check the latest logs.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md b/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md
index de5b348..0b2a43c 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md
@@ -8,7 +8,7 @@ You can manage the webhook CI of the application from the **Webhook CI** section
This **Webhook** can be used to trigger re-deployment of the application when the source code of the application is updated.
-
+
**Regenerate Webhook Token** - You can regenerate the webhook URL by tapping on **Regenerate Webhook** button. If you have exposed the webhook URL to the public by mistake, then you can regenerate the webhook URL to make the old webhook URL invalid.
diff --git a/versioned_docs/version-1.x.x/dashboard/applications.md b/versioned_docs/version-1.x.x/dashboard/applications.md
index ba15a31..56d8012 100644
--- a/versioned_docs/version-1.x.x/dashboard/applications.md
+++ b/versioned_docs/version-1.x.x/dashboard/applications.md
@@ -6,8 +6,8 @@ sidebar_position: 3
In **Application List**, you can see all the applications that you have created. You can check the status of the application, last time when it was updated, and the number of instances running for that application.
-
+
You can click on **`View Details`** button to see more details about the application.
-Check out [**Application Details**](/docs/dashboard/application_details) to learn more about it.
\ No newline at end of file
+Check out [**Application Details**](./application_details) to learn more about it.
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/change_password.md b/versioned_docs/version-1.x.x/dashboard/change_password.md
index 6525a2c..39ef0d8 100644
--- a/versioned_docs/version-1.x.x/dashboard/change_password.md
+++ b/versioned_docs/version-1.x.x/dashboard/change_password.md
@@ -6,6 +6,6 @@ sidebar_position: 11
To **change your password**, you can click on **Change Password** button in the sidebar. You will see a form like this:
-
+
You need to enter your current password and new password. Then, click on **Change Password** button and your password will be changed.
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md b/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md
index 068f08e..11a967d 100644
--- a/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md
+++ b/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md
@@ -30,7 +30,7 @@ Deploying with SwiftWave is a breeze – just bring your application's source co
### 📚 Next Steps
-- [**How to check details and manage a deployed application**](/docs/dashboard/application_details/)
-- [**How to expose application to internet ?**](/docs/dashboard/ingress-rules)
-- [**How to configure persistent storage ?**](/docs/dashboard/application_details/persistent_volumes)
-- [**How to configure environment variables ?**](/docs/dashboard/application_details/environment_variables)
+- [**How to check details and manage a deployed application**](./application_details/)
+- [**How to expose application to internet ?**](./ingress-rules)
+- [**How to configure persistent storage ?**](./application_details/persistent_volumes)
+- [**How to configure environment variables ?**](./application_details/environment_variables)
diff --git a/versioned_docs/version-1.x.x/dashboard/domains.md b/versioned_docs/version-1.x.x/dashboard/domains.md
index db0e468..6a7f215 100644
--- a/versioned_docs/version-1.x.x/dashboard/domains.md
+++ b/versioned_docs/version-1.x.x/dashboard/domains.md
@@ -6,7 +6,7 @@ sidebar_position: 7
In **Domains** section, you can manage all the custom domains you have added to swiftwave.
-
+
### Register a new domain
You can click on `Register New` button and fill in the required details to register a new domain.
diff --git a/versioned_docs/version-1.x.x/dashboard/git-credentials.md b/versioned_docs/version-1.x.x/dashboard/git-credentials.md
index f98a487..61422ad 100644
--- a/versioned_docs/version-1.x.x/dashboard/git-credentials.md
+++ b/versioned_docs/version-1.x.x/dashboard/git-credentials.md
@@ -6,7 +6,7 @@ sidebar_position: 5
In **Git Credentials** section, you can check all the saved Git Credentials. You can use these credentials while deploying an application from a Git Repository.
-
+
**You can**
- **Add** a new Git Credential by clicking on `Add New` button.
diff --git a/versioned_docs/version-1.x.x/dashboard/image-credentials.md b/versioned_docs/version-1.x.x/dashboard/image-credentials.md
index baf99d2..24fd654 100644
--- a/versioned_docs/version-1.x.x/dashboard/image-credentials.md
+++ b/versioned_docs/version-1.x.x/dashboard/image-credentials.md
@@ -6,7 +6,7 @@ sidebar_position: 6
In **Image Credentials** section, you can check all the saved Image Registry Credentials. You can use these credentials while deploying an application from a Image Repository.
-
+
**You can**
- **Add** a new Image Registry Credential by clicking on `Add New` button.
diff --git a/versioned_docs/version-1.x.x/dashboard/index.md b/versioned_docs/version-1.x.x/dashboard/index.md
index 5062974..bb7296b 100644
--- a/versioned_docs/version-1.x.x/dashboard/index.md
+++ b/versioned_docs/version-1.x.x/dashboard/index.md
@@ -10,7 +10,7 @@ sidebar_position: 5
justifyContent: 'center',
marginBottom: '2rem'
}}>
-
+ 
@@ -20,17 +20,17 @@ SwiftWave Dashboard is a web-based interface to manage your applications, domain
## Sections of Dashboard
-| Section | Description | Link |
-| --- | --- | --- |
-| 🔒 Log In | Log in to SwiftWave Dashboard | [***Click Here***](/docs/dashboard/log_in) |
-| 🔨 Deploy New Application | Deploy new application on your server | [***Click Here***](/docs/dashboard/deploy_new_application) |
-| 📦 Applications | List of all applications deployed on your server & manage them | [***Click Here***](/docs/dashboard/applications) |
-| 📦 Persistent Volumes | List of all persistent volumes created on your server & manage them | [***Click Here***](/docs/dashboard/persistent-volumes) |
-| 🐙 Git Credentials | Manage git credentials for your applications | [***Click Here***](/docs/dashboard/git-credentials) |
-| 🐳 Image Credentials | Manage docker image credentials for your applications | [***Click Here***](/docs/dashboard/image-credentials) |
-| 🌐 Domains | Manage custom domains, SSL for your applications | [***Click Here***](/docs/dashboard/domains) |
-| 🚪 Ingress Rules | Manage exposed domains and routes for your applications | [***Click Here***](/docs/dashboard/ingress-rules) |
-| 🔄 Redirect Rules | Manage domain redirection and HTTPS redirection for your applications | [***Click Here***](/docs/dashboard/redirect-rules) |
-| 👥 Manage Users | Manage admin users for your hosted SwiftWave instance | [***Click Here***](/docs/dashboard/manage-users) |
-| 🔒 Change Password | Change password for currently logged In user | [***Click Here***](/docs/dashboard/change_password) |
+| Section | Description | Link |
+| ------------------------ | --------------------------------------------------------------------- |----------------------------------------------|
+| 🔒 Log In | Log in to SwiftWave Dashboard | [***Click Here***](./log_in) |
+| 🔨 Deploy New Application | Deploy new application on your server | [***Click Here***](./deploy_new_application) |
+| 📦 Applications | List of all applications deployed on your server & manage them | [***Click Here***](./applications) |
+| 📦 Persistent Volumes | List of all persistent volumes created on your server & manage them | [***Click Here***](./persistent-volumes) |
+| 🐙 Git Credentials | Manage git credentials for your applications | [***Click Here***](./git-credentials) |
+| 🐳 Image Credentials | Manage docker image credentials for your applications | [***Click Here***](./image-credentials) |
+| 🌐 Domains | Manage custom domains, SSL for your applications | [***Click Here***](./domains) |
+| 🚪 Ingress Rules | Manage exposed domains and routes for your applications | [***Click Here***](./ingress-rules) |
+| 🔄 Redirect Rules | Manage domain redirection and HTTPS redirection for your applications | [***Click Here***](./redirect-rules) |
+| 👥 Manage Users | Manage admin users for your hosted SwiftWave instance | [***Click Here***](./manage-users) |
+| 🔒 Change Password | Change password for currently logged In user | [***Click Here***](./change_password) |
diff --git a/versioned_docs/version-1.x.x/dashboard/ingress-rules.md b/versioned_docs/version-1.x.x/dashboard/ingress-rules.md
index f88074c..35fd46c 100644
--- a/versioned_docs/version-1.x.x/dashboard/ingress-rules.md
+++ b/versioned_docs/version-1.x.x/dashboard/ingress-rules.md
@@ -6,7 +6,7 @@ sidebar_position: 8
In **Ingress Rules** section you can manage your ingress rules. You can add or delete ingress rules.
-
+
### 😅 Don't know what ingress rules are ?
In layman's terms, ingress rules are the rules that will connect your domain to your application.
@@ -19,20 +19,20 @@ myapp.com [https] -> myapp:3000
### Add Ingress Rule
To add an ingress rule, click on **Add New** button. You will see a form like this:
-
+
You can choose the protocol your application required.
- **HTTP**: You can choose any port for your application. It's recommended to use port 80 for HTTP.
- **HTTPS**: Currently, only port 443 is supported.
- > Note: To enable, **HTTPS Redirection**, you will have to create a redirect rule. You can follow [**this docs**](/docs/dashboard/redirect-rules#https-redirect) section to create a redirect rule.
+ > Note: To enable, **HTTPS Redirection**, you will have to create a redirect rule. You can follow [**this docs**](./redirect-rules#https-redirect) section to create a redirect rule.
- **TCP**: If your application relies on TCP protocol, you can choose this option. You can choose any port for your application.
> NOTE : In case of TCP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
- **UDP**: If your application relies on UDP protocol, you can choose this option. You can choose any port for your application.
> NOTE : In case of UDP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
-Then, you can choose the domain you want to connect to your application. If you don't have any domain, you can add it in [**Domains**](/docs/dashboard/domains) section.
+Then, you can choose the domain you want to connect to your application. If you don't have any domain, you can add it in [**Domains**](./domains) section.
-**Finally**, you can choose the application you want to connect to your domain. If you don't have any application, you can deploy one by following [**this docs**](/docs/dashboard/deploy_new_application) section.
+**Finally**, you can choose the application you want to connect to your domain. If you don't have any application, you can deploy one by following [**this docs**](./deploy_new_application) section.
Hurrah! You have successfully created an ingress rule. Now, you can access your application via your domain.
It takes upto 1 minute to apply the changes.
diff --git a/versioned_docs/version-1.x.x/dashboard/log_in.md b/versioned_docs/version-1.x.x/dashboard/log_in.md
index 02d5698..a9ce7ff 100644
--- a/versioned_docs/version-1.x.x/dashboard/log_in.md
+++ b/versioned_docs/version-1.x.x/dashboard/log_in.md
@@ -6,7 +6,7 @@ sidebar_position: 1
When you will visit the dashboard for the first time, you will be asked to log in.
-
+
You can log in using the credentials of the user you created while installing the application.
@@ -19,4 +19,4 @@ You can also **Create New User** from the CLI (if you have access to the server
sudo swiftwave create-user --username
- 🚀 v2.x released openUrl("https://github.com/swiftwave-org/swiftwave/releases/tag/2.0.0-1")}>Check here
+ 🚀 Swiftwave v2.0.x released
{/* tagline */}
@@ -25,7 +25,7 @@ export default function Header() {
for self-hosting
{/* cta */}
- openUrl("/docs/getting_started")}>
+
diff --git a/static/assets/add-ingress-rule.png b/static/assets/1.x.x/add-ingress-rule.png
similarity index 100%
rename from static/assets/add-ingress-rule.png
rename to static/assets/1.x.x/add-ingress-rule.png
diff --git a/static/assets/application-danger-zone.png b/static/assets/1.x.x/application-danger-zone.png
similarity index 100%
rename from static/assets/application-danger-zone.png
rename to static/assets/1.x.x/application-danger-zone.png
diff --git a/static/assets/application-deployment-configuration.png b/static/assets/1.x.x/application-deployment-configuration.png
similarity index 100%
rename from static/assets/application-deployment-configuration.png
rename to static/assets/1.x.x/application-deployment-configuration.png
diff --git a/static/assets/application-details.png b/static/assets/1.x.x/application-details.png
similarity index 100%
rename from static/assets/application-details.png
rename to static/assets/1.x.x/application-details.png
diff --git a/static/assets/application-environment-variables.png b/static/assets/1.x.x/application-environment-variables.png
similarity index 100%
rename from static/assets/application-environment-variables.png
rename to static/assets/1.x.x/application-environment-variables.png
diff --git a/static/assets/application-ingress-rules.png b/static/assets/1.x.x/application-ingress-rules.png
similarity index 100%
rename from static/assets/application-ingress-rules.png
rename to static/assets/1.x.x/application-ingress-rules.png
diff --git a/static/assets/application-list.png b/static/assets/1.x.x/application-list.png
similarity index 100%
rename from static/assets/application-list.png
rename to static/assets/1.x.x/application-list.png
diff --git a/static/assets/application-persistent-volume.png b/static/assets/1.x.x/application-persistent-volume.png
similarity index 100%
rename from static/assets/application-persistent-volume.png
rename to static/assets/1.x.x/application-persistent-volume.png
diff --git a/static/assets/application-update-source.png b/static/assets/1.x.x/application-update-source.png
similarity index 100%
rename from static/assets/application-update-source.png
rename to static/assets/1.x.x/application-update-source.png
diff --git a/static/assets/application-webhook-ci.png b/static/assets/1.x.x/application-webhook-ci.png
similarity index 100%
rename from static/assets/application-webhook-ci.png
rename to static/assets/1.x.x/application-webhook-ci.png
diff --git a/static/assets/backup-history.png b/static/assets/1.x.x/backup-history.png
similarity index 100%
rename from static/assets/backup-history.png
rename to static/assets/1.x.x/backup-history.png
diff --git a/static/assets/cancel-deployment.png b/static/assets/1.x.x/cancel-deployment.png
similarity index 100%
rename from static/assets/cancel-deployment.png
rename to static/assets/1.x.x/cancel-deployment.png
diff --git a/static/assets/change-password.png b/static/assets/1.x.x/change-password.png
similarity index 100%
rename from static/assets/change-password.png
rename to static/assets/1.x.x/change-password.png
diff --git a/static/assets/choose-app-source-app-deploy.png b/static/assets/1.x.x/choose-app-source-app-deploy.png
similarity index 100%
rename from static/assets/choose-app-source-app-deploy.png
rename to static/assets/1.x.x/choose-app-source-app-deploy.png
diff --git a/static/assets/create-local-volume.png b/static/assets/1.x.x/create-local-volume.png
similarity index 100%
rename from static/assets/create-local-volume.png
rename to static/assets/1.x.x/create-local-volume.png
diff --git a/static/assets/create-nfs-volume.png b/static/assets/1.x.x/create-nfs-volume.png
similarity index 100%
rename from static/assets/create-nfs-volume.png
rename to static/assets/1.x.x/create-nfs-volume.png
diff --git a/static/assets/create-redirect-rule.png b/static/assets/1.x.x/create-redirect-rule.png
similarity index 100%
rename from static/assets/create-redirect-rule.png
rename to static/assets/1.x.x/create-redirect-rule.png
diff --git a/static/assets/create-user.png b/static/assets/1.x.x/create-user.png
similarity index 100%
rename from static/assets/create-user.png
rename to static/assets/1.x.x/create-user.png
diff --git a/static/assets/custom-domain-list.png b/static/assets/1.x.x/custom-domain-list.png
similarity index 100%
rename from static/assets/custom-domain-list.png
rename to static/assets/1.x.x/custom-domain-list.png
diff --git a/static/assets/dashboard-loading.png b/static/assets/1.x.x/dashboard-loading.png
similarity index 100%
rename from static/assets/dashboard-loading.png
rename to static/assets/1.x.x/dashboard-loading.png
diff --git a/static/assets/deployment-details.png b/static/assets/1.x.x/deployment-details.png
similarity index 100%
rename from static/assets/deployment-details.png
rename to static/assets/1.x.x/deployment-details.png
diff --git a/static/assets/deployment-list.png b/static/assets/1.x.x/deployment-list.png
similarity index 100%
rename from static/assets/deployment-list.png
rename to static/assets/1.x.x/deployment-list.png
diff --git a/static/assets/git-credential-list.png b/static/assets/1.x.x/git-credential-list.png
similarity index 100%
rename from static/assets/git-credential-list.png
rename to static/assets/1.x.x/git-credential-list.png
diff --git a/static/assets/image-registry-credential-list.png b/static/assets/1.x.x/image-registry-credential-list.png
similarity index 100%
rename from static/assets/image-registry-credential-list.png
rename to static/assets/1.x.x/image-registry-credential-list.png
diff --git a/static/assets/ingress-rule-list.png b/static/assets/1.x.x/ingress-rule-list.png
similarity index 100%
rename from static/assets/ingress-rule-list.png
rename to static/assets/1.x.x/ingress-rule-list.png
diff --git a/static/assets/log-in.png b/static/assets/1.x.x/log-in.png
similarity index 100%
rename from static/assets/log-in.png
rename to static/assets/1.x.x/log-in.png
diff --git a/static/assets/manage-users.png b/static/assets/1.x.x/manage-users.png
similarity index 100%
rename from static/assets/manage-users.png
rename to static/assets/1.x.x/manage-users.png
diff --git a/static/assets/persistent-volumes.png b/static/assets/1.x.x/persistent-volumes.png
similarity index 100%
rename from static/assets/persistent-volumes.png
rename to static/assets/1.x.x/persistent-volumes.png
diff --git a/static/assets/redirect-rule-list.png b/static/assets/1.x.x/redirect-rule-list.png
similarity index 100%
rename from static/assets/redirect-rule-list.png
rename to static/assets/1.x.x/redirect-rule-list.png
diff --git a/static/assets/restore-history.png b/static/assets/1.x.x/restore-history.png
similarity index 100%
rename from static/assets/restore-history.png
rename to static/assets/1.x.x/restore-history.png
diff --git a/static/assets/runtime-logs.png b/static/assets/1.x.x/runtime-logs.png
similarity index 100%
rename from static/assets/runtime-logs.png
rename to static/assets/1.x.x/runtime-logs.png
diff --git a/static/assets/2.0.x/add-http-credential.png b/static/assets/2.0.x/add-http-credential.png
new file mode 100644
index 0000000..7edac04
Binary files /dev/null and b/static/assets/2.0.x/add-http-credential.png differ
diff --git a/static/assets/2.0.x/add-ingress-rule-application.png b/static/assets/2.0.x/add-ingress-rule-application.png
new file mode 100644
index 0000000..98b2321
Binary files /dev/null and b/static/assets/2.0.x/add-ingress-rule-application.png differ
diff --git a/static/assets/2.0.x/add-ingress-rule-external.png b/static/assets/2.0.x/add-ingress-rule-external.png
new file mode 100644
index 0000000..c55fac2
Binary files /dev/null and b/static/assets/2.0.x/add-ingress-rule-external.png differ
diff --git a/static/assets/2.0.x/add-server.png b/static/assets/2.0.x/add-server.png
new file mode 100644
index 0000000..2852b09
Binary files /dev/null and b/static/assets/2.0.x/add-server.png differ
diff --git a/static/assets/2.0.x/add-ssh-credential.png b/static/assets/2.0.x/add-ssh-credential.png
new file mode 100644
index 0000000..7ddcbce
Binary files /dev/null and b/static/assets/2.0.x/add-ssh-credential.png differ
diff --git a/static/assets/2.0.x/app-store.png b/static/assets/2.0.x/app-store.png
new file mode 100644
index 0000000..e1b0286
Binary files /dev/null and b/static/assets/2.0.x/app-store.png differ
diff --git a/static/assets/2.0.x/application-actions.png b/static/assets/2.0.x/application-actions.png
new file mode 100644
index 0000000..a77267c
Binary files /dev/null and b/static/assets/2.0.x/application-actions.png differ
diff --git a/static/assets/2.0.x/application-analytics.png b/static/assets/2.0.x/application-analytics.png
new file mode 100644
index 0000000..ece8012
Binary files /dev/null and b/static/assets/2.0.x/application-analytics.png differ
diff --git a/static/assets/2.0.x/application-configure-webhook.png b/static/assets/2.0.x/application-configure-webhook.png
new file mode 100644
index 0000000..64449b3
Binary files /dev/null and b/static/assets/2.0.x/application-configure-webhook.png differ
diff --git a/static/assets/2.0.x/application-deployment-configuration.png b/static/assets/2.0.x/application-deployment-configuration.png
new file mode 100644
index 0000000..c542918
Binary files /dev/null and b/static/assets/2.0.x/application-deployment-configuration.png differ
diff --git a/static/assets/2.0.x/application-destroy.png b/static/assets/2.0.x/application-destroy.png
new file mode 100644
index 0000000..83e3680
Binary files /dev/null and b/static/assets/2.0.x/application-destroy.png differ
diff --git a/static/assets/2.0.x/application-details.png b/static/assets/2.0.x/application-details.png
new file mode 100644
index 0000000..4a200ed
Binary files /dev/null and b/static/assets/2.0.x/application-details.png differ
diff --git a/static/assets/2.0.x/application-environment-variables.png b/static/assets/2.0.x/application-environment-variables.png
new file mode 100644
index 0000000..4d4c9d5
Binary files /dev/null and b/static/assets/2.0.x/application-environment-variables.png differ
diff --git a/static/assets/2.0.x/application-ingress-rules.png b/static/assets/2.0.x/application-ingress-rules.png
new file mode 100644
index 0000000..c715ead
Binary files /dev/null and b/static/assets/2.0.x/application-ingress-rules.png differ
diff --git a/static/assets/2.0.x/application-persistent-volumes.png b/static/assets/2.0.x/application-persistent-volumes.png
new file mode 100644
index 0000000..40a0d8a
Binary files /dev/null and b/static/assets/2.0.x/application-persistent-volumes.png differ
diff --git a/static/assets/2.0.x/application-ssh-console.png b/static/assets/2.0.x/application-ssh-console.png
new file mode 100644
index 0000000..f89e663
Binary files /dev/null and b/static/assets/2.0.x/application-ssh-console.png differ
diff --git a/static/assets/2.0.x/application-ssh-select-server.png b/static/assets/2.0.x/application-ssh-select-server.png
new file mode 100644
index 0000000..b0eba80
Binary files /dev/null and b/static/assets/2.0.x/application-ssh-select-server.png differ
diff --git a/static/assets/2.0.x/application-update-source.png b/static/assets/2.0.x/application-update-source.png
new file mode 100644
index 0000000..ecfb19d
Binary files /dev/null and b/static/assets/2.0.x/application-update-source.png differ
diff --git a/static/assets/2.0.x/benchmark.png b/static/assets/2.0.x/benchmark.png
new file mode 100644
index 0000000..e8938a1
Binary files /dev/null and b/static/assets/2.0.x/benchmark.png differ
diff --git a/static/assets/2.0.x/create-cifs-volume.png b/static/assets/2.0.x/create-cifs-volume.png
new file mode 100644
index 0000000..26df008
Binary files /dev/null and b/static/assets/2.0.x/create-cifs-volume.png differ
diff --git a/static/assets/2.0.x/create-redirect-rule.png b/static/assets/2.0.x/create-redirect-rule.png
new file mode 100644
index 0000000..5c74756
Binary files /dev/null and b/static/assets/2.0.x/create-redirect-rule.png differ
diff --git a/static/assets/2.0.x/dashboard-loading.png b/static/assets/2.0.x/dashboard-loading.png
new file mode 100644
index 0000000..8ce9c21
Binary files /dev/null and b/static/assets/2.0.x/dashboard-loading.png differ
diff --git a/static/assets/2.0.x/deploy-stack.png b/static/assets/2.0.x/deploy-stack.png
new file mode 100644
index 0000000..bf55e48
Binary files /dev/null and b/static/assets/2.0.x/deploy-stack.png differ
diff --git a/static/assets/2.0.x/deployment-details.png b/static/assets/2.0.x/deployment-details.png
new file mode 100644
index 0000000..b04c92f
Binary files /dev/null and b/static/assets/2.0.x/deployment-details.png differ
diff --git a/static/assets/2.0.x/deployments.png b/static/assets/2.0.x/deployments.png
new file mode 100644
index 0000000..077052b
Binary files /dev/null and b/static/assets/2.0.x/deployments.png differ
diff --git a/static/assets/2.0.x/domain-list.png b/static/assets/2.0.x/domain-list.png
new file mode 100644
index 0000000..4f1b66e
Binary files /dev/null and b/static/assets/2.0.x/domain-list.png differ
diff --git a/static/assets/2.0.x/git-credential-list.png b/static/assets/2.0.x/git-credential-list.png
new file mode 100644
index 0000000..a3a2810
Binary files /dev/null and b/static/assets/2.0.x/git-credential-list.png differ
diff --git a/static/assets/2.0.x/image-registry-credential-list.png b/static/assets/2.0.x/image-registry-credential-list.png
new file mode 100644
index 0000000..81d0e59
Binary files /dev/null and b/static/assets/2.0.x/image-registry-credential-list.png differ
diff --git a/static/assets/2.0.x/ingress-rule-list.png b/static/assets/2.0.x/ingress-rule-list.png
new file mode 100644
index 0000000..fb1dc13
Binary files /dev/null and b/static/assets/2.0.x/ingress-rule-list.png differ
diff --git a/static/assets/2.0.x/log-in.png b/static/assets/2.0.x/log-in.png
new file mode 100644
index 0000000..5715313
Binary files /dev/null and b/static/assets/2.0.x/log-in.png differ
diff --git a/static/assets/2.0.x/runtime-logs.png b/static/assets/2.0.x/runtime-logs.png
new file mode 100644
index 0000000..a147ef4
Binary files /dev/null and b/static/assets/2.0.x/runtime-logs.png differ
diff --git a/static/assets/2.0.x/server-actions.png b/static/assets/2.0.x/server-actions.png
new file mode 100644
index 0000000..460b7b8
Binary files /dev/null and b/static/assets/2.0.x/server-actions.png differ
diff --git a/static/assets/2.0.x/server-analytics.png b/static/assets/2.0.x/server-analytics.png
new file mode 100644
index 0000000..2edfe1b
Binary files /dev/null and b/static/assets/2.0.x/server-analytics.png differ
diff --git a/static/assets/2.0.x/server-logs.png b/static/assets/2.0.x/server-logs.png
new file mode 100644
index 0000000..840a13c
Binary files /dev/null and b/static/assets/2.0.x/server-logs.png differ
diff --git a/static/assets/2.0.x/server-management.png b/static/assets/2.0.x/server-management.png
new file mode 100644
index 0000000..19dae84
Binary files /dev/null and b/static/assets/2.0.x/server-management.png differ
diff --git a/static/assets/2.0.x/server-web-console.png b/static/assets/2.0.x/server-web-console.png
new file mode 100644
index 0000000..3977a6f
Binary files /dev/null and b/static/assets/2.0.x/server-web-console.png differ
diff --git a/static/assets/2.0.x/ssh-git-credential-details.png b/static/assets/2.0.x/ssh-git-credential-details.png
new file mode 100644
index 0000000..b584876
Binary files /dev/null and b/static/assets/2.0.x/ssh-git-credential-details.png differ
diff --git a/static/assets/2.0.x/system-configuration.png b/static/assets/2.0.x/system-configuration.png
new file mode 100644
index 0000000..ed76a58
Binary files /dev/null and b/static/assets/2.0.x/system-configuration.png differ
diff --git a/static/assets/2.0.x/system-logs.png b/static/assets/2.0.x/system-logs.png
new file mode 100644
index 0000000..78403e9
Binary files /dev/null and b/static/assets/2.0.x/system-logs.png differ
diff --git a/versioned_docs/version-1.x.x/cli/auto-updater/enable.md b/versioned_docs/version-1.x.x/cli/auto-updater/enable.md
index c21b5ce..f892d1e 100644
--- a/versioned_docs/version-1.x.x/cli/auto-updater/enable.md
+++ b/versioned_docs/version-1.x.x/cli/auto-updater/enable.md
@@ -14,7 +14,7 @@ Enable Swiftwave Auto Updater Service.
You should keep automated database migration enabled to avoid any issues and use SwiftWave Auto Updater.
If you have disabled automated database migration, you can enable it by
-- Run `swiftwave config -e vim` or `swiftwave config -e nano` to open SwiftWave configuration file in editor. [See more](/docs/cli/config)
+- Run `swiftwave config -e vim` or `swiftwave config -e nano` to open SwiftWave configuration file in editor. [See more](../config)
- Set `service.auto_migrate_database` to `false`
- Save and close the file
diff --git a/versioned_docs/version-1.x.x/cli/auto-updater/index.md b/versioned_docs/version-1.x.x/cli/auto-updater/index.md
index f4ffaee..a558569 100644
--- a/versioned_docs/version-1.x.x/cli/auto-updater/index.md
+++ b/versioned_docs/version-1.x.x/cli/auto-updater/index.md
@@ -10,5 +10,5 @@ sidebar_position: 14
Auto updater is a feature that will automatically update Swiftwave to the latest minor version and apply hotfixes.
### Check available commands
-- [**swiftwave auto-updater enable**](/docs/cli/auto-updater/enable)
-- [**swiftwave auto-updater disable**](/docs/cli/auto-updater/disable)
\ No newline at end of file
+- [**swiftwave auto-updater enable**](./enable)
+- [**swiftwave auto-updater disable**](./disable)
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/cli/haproxy/index.md b/versioned_docs/version-1.x.x/cli/haproxy/index.md
index 3ac8e7f..a4f1927 100755
--- a/versioned_docs/version-1.x.x/cli/haproxy/index.md
+++ b/versioned_docs/version-1.x.x/cli/haproxy/index.md
@@ -10,6 +10,6 @@ sidebar_position: 11
Manage HAProxy service
### Check available commands
-- [**swiftwave haproxy start**](/docs/cli/haproxy/start)
-- [**swiftwave haproxy stop**](/docs/cli/haproxy/stop)
-- [**swiftwave haproxy status**](/docs/cli/haproxy/status)
\ No newline at end of file
+- [**swiftwave haproxy start**](./start)
+- [**swiftwave haproxy stop**](./stop)
+- [**swiftwave haproxy status**](./status)
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/cli/postgres/index.md b/versioned_docs/version-1.x.x/cli/postgres/index.md
index d83b5c7..70865eb 100755
--- a/versioned_docs/version-1.x.x/cli/postgres/index.md
+++ b/versioned_docs/version-1.x.x/cli/postgres/index.md
@@ -10,6 +10,6 @@ sidebar_position: 12
Manage local postgres database (Only for standalone installation) [Not recommended]
### Check available commands
-- [**swiftwave postgres start**](/docs/cli/postgres/start)
-- [**swiftwave postgres stop**](/docs/cli/postgres/stop)
-- [**swiftwave postgres status**](/docs/cli/postgres/status)
\ No newline at end of file
+- [**swiftwave postgres start**](./start)
+- [**swiftwave postgres stop**](./stop)
+- [**swiftwave postgres status**](./status)
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/cli/service/index.md b/versioned_docs/version-1.x.x/cli/service/index.md
index fc23f90..732eeab 100755
--- a/versioned_docs/version-1.x.x/cli/service/index.md
+++ b/versioned_docs/version-1.x.x/cli/service/index.md
@@ -10,6 +10,6 @@ sidebar_position: 10
Manage Swiftwave Daemon Service
### Check available commands
-- [**swiftwave service enable**](/docs/cli/service/enable)
-- [**swiftwave service disable**](/docs/cli/service/disable)
-- [**swiftwave service status**](/docs/cli/service/status)
\ No newline at end of file
+- [**swiftwave service enable**](./enable)
+- [**swiftwave service disable**](./disable)
+- [**swiftwave service status**](./status)
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/cli/start.md b/versioned_docs/version-1.x.x/cli/start.md
index 73517d0..f6d6085 100755
--- a/versioned_docs/version-1.x.x/cli/start.md
+++ b/versioned_docs/version-1.x.x/cli/start.md
@@ -21,4 +21,4 @@ swiftwave start --dev
```
### Note
-If you are looking to run swiftwave as a service, please refer to the [**service**](/docs/cli/service) command.
+If you are looking to run swiftwave as a service, please refer to the [**service**](./service) command.
diff --git a/versioned_docs/version-1.x.x/cli/tls/auto-renew/index.md b/versioned_docs/version-1.x.x/cli/tls/auto-renew/index.md
index efec3e4..cfe94eb 100644
--- a/versioned_docs/version-1.x.x/cli/tls/auto-renew/index.md
+++ b/versioned_docs/version-1.x.x/cli/tls/auto-renew/index.md
@@ -10,5 +10,5 @@ Automated Service to renew TLS certificates for all domain registered for swiftw
> It's not for renewing certificates for domain of hosted applications
### Check available commands
-- [**swiftwave tls auto-renew enable**](/docs/cli/tls/auto-renew/enable)
-- [**swiftwave tls auto-renew disable**](/docs/cli/tls/auto-renew/disable)
+- [**swiftwave tls auto-renew enable**](./enable)
+- [**swiftwave tls auto-renew disable**](./disable)
diff --git a/versioned_docs/version-1.x.x/cli/tls/index.md b/versioned_docs/version-1.x.x/cli/tls/index.md
index 89db0c1..b9b4e89 100644
--- a/versioned_docs/version-1.x.x/cli/tls/index.md
+++ b/versioned_docs/version-1.x.x/cli/tls/index.md
@@ -9,7 +9,7 @@ sidebar_position: 8
Manage TLS for swiftwave service
### Check available commands
-- [**swiftwave tls enable**](/docs/cli/tls/enable)
-- [**swiftwave tls disable**](/docs/cli/tls/disable)
-- [**swiftwave tls generate-certificate**](/docs/cli/tls/generate-certificate)
-- [**swiftwave tls renew-certificates**](/docs/cli/tls/renew-certificates)
\ No newline at end of file
+- [**swiftwave tls enable**](./enable)
+- [**swiftwave tls disable**](./disable)
+- [**swiftwave tls generate-certificate**](./generate-certificate)
+- [**swiftwave tls renew-certificates**](./renew-certificates)
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/contribution_guideline.md b/versioned_docs/version-1.x.x/contribution_guideline.md
index ead8e1e..a7645d2 100644
--- a/versioned_docs/version-1.x.x/contribution_guideline.md
+++ b/versioned_docs/version-1.x.x/contribution_guideline.md
@@ -11,12 +11,12 @@ First off, thanks for having interest in contributing to SwiftWave! 🎉
We have couple of projects under SwiftWave organization. You can contribute to any of them.
-| Project | Description | Tech Stack | GitHub Link | Setup Guide |
-| --- | --- | --- | --- | --- |
-| SwiftWave | Core PaaS | Golang, Docker | [Click Here](https://github.com/swiftwave-org/swiftwave) | [Click Here](/docs/development_setup) |
-| SwiftWave Dashboard | Web interface for SwiftWave. | VueJS, TailwindCSS | [Click Here](https://github.com/swiftwave-org/dashboard) | [Click Here](https://github.com/swiftwave-org/dashboard) |
+| Project | Description | Tech Stack | GitHub Link | Setup Guide |
+| --- | --- | --- | --- |--------------------------------------------------------------|
+| SwiftWave | Core PaaS | Golang, Docker | [Click Here](https://github.com/swiftwave-org/swiftwave) | [Click Here](./development_setup) |
+| SwiftWave Dashboard | Web interface for SwiftWave. | VueJS, TailwindCSS | [Click Here](https://github.com/swiftwave-org/dashboard) | [Click Here](https://github.com/swiftwave-org/dashboard) |
| SwiftWave Docs + Landing Page | Official landing page and documentation website | Docusaurus | [Click Here](https://github.com/swiftwave-org/swiftwave.org) | [Click Here](https://github.com/swiftwave-org/swiftwave.org) |
-| Quick DNS | Service to provide ***.swiftwave.xyz** domain for your swiftwave installation | Golang | [Click Here](https://github.com/swiftwave-org/dns) | [Click Here](https://github.com/swiftwave-org/dns) |
+| Quick DNS | Service to provide ***.swiftwave.xyz** domain for your swiftwave installation | Golang | [Click Here](https://github.com/swiftwave-org/dns) | [Click Here](https://github.com/swiftwave-org/dns) |
### 📝 How to Contribute to any of the project
1. Fork the repository
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/application_update_source.md b/versioned_docs/version-1.x.x/dashboard/application_details/application_update_source.md
index a5de68b..a12ade4 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/application_update_source.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/application_update_source.md
@@ -6,7 +6,7 @@ sidebar_position: 4
In **Update Source Code** section, you can update the source of the application. You can update the source of the application to deploy a new version of the application.
-
+
### How to update source of the application ?
- Change the source info of the application.
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/danger_zone.md b/versioned_docs/version-1.x.x/dashboard/application_details/danger_zone.md
index 5c77c3a..d1cf95a 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/danger_zone.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/danger_zone.md
@@ -6,7 +6,7 @@ sidebar_position: 9
In **Danger Zone** section, you have some options which can lead to downtime of the application. So, be careful while using these options.
-
+
### Restart Application
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/deployment_configuration.md b/versioned_docs/version-1.x.x/dashboard/application_details/deployment_configuration.md
index 6c50ff5..9cf8a57 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/deployment_configuration.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/deployment_configuration.md
@@ -6,7 +6,7 @@ sidebar_position: 7
In **Deployment Configuration** section, you can *scale up* or *scale down* the application.
-
+
**Deployment Modes -**
- **Replicated Mode** - In this mode, you can specify the number of instances you want to run for the application.
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/deployments.md b/versioned_docs/version-1.x.x/dashboard/application_details/deployments.md
index 1cfb898..7ec07c5 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/deployments.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/deployments.md
@@ -6,17 +6,17 @@ sidebar_position: 1
In **Deployments** section, you can see all the deployments of the application. You can check the status of the deployment and time of deployment at a glance.
-
+
But, you want to see more details about the deployment, you can click on the **Deployment Card** to see more details about the deployment.
Once you click on the **Deployment Card**, you will see the **Deployment Details** page like this:
-
+
Here, you can see complete details about the deployment. You can also check deployment logs to figure out what went wrong.
> 📌 While deployment is live,
- The *Deployment Logs* will be updated in realtime.
- **Request Cancellation** button will be available to cancel the deployment, if due to any reason docker build stuck, you can cancel the deployment.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/environment_variables.md b/versioned_docs/version-1.x.x/dashboard/application_details/environment_variables.md
index 6a595bb..8f09830 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/environment_variables.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/environment_variables.md
@@ -6,6 +6,6 @@ sidebar_position: 5
In **Environment Variables** section, you can see all the environment variables of the application. You can add new environment variables, edit existing environment variables, and also can delete environment variables.
-
+
The UI is pretty simple and self-explanatory. After you change something, click on **`Apply Changes`** button to save the changes.
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/index.md b/versioned_docs/version-1.x.x/dashboard/application_details/index.md
index 37943c7..1d6f3d0 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/index.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/index.md
@@ -7,7 +7,7 @@ toc_max_heading_level: 5
In **Application Details**, you can see all the details about the application. You can check the status of the application, last time when it was updated, and the number of instances running for that application.
- openUrl("/docs/installation")}>
+
On the right side, you can see realtime information about the count of active instances of the application.
@@ -21,14 +21,14 @@ If you like to make your application online, you can resume the application. Thi
#### 🏄♂️ Let's go through each section of the **Application Details** page.
-| Section | Page Link |
-|---------|-----------|
-| Deployments | [***Click Here***](/docs/dashboard/application_details/deployments) |
-| Runtime Logs | [***Click Here***](/docs/dashboard/application_details/runtime_logs) |
-| Ingress Rules | [***Click Here***](/docs/dashboard/application_details/ingress_rules) |
-| Update Source Code | [***Click Here***](/docs/dashboard/application_details/update_source_code) |
-| Environment Variables | [***Click Here***](/docs/dashboard/application_details/environment_variables) |
-| Persistent Volumes | [***Click Here***](/docs/dashboard/application_details/persistent_volumes) |
-| Deployment Configuration | [***Click Here***](/docs/dashboard/application_details/deployment_configuration) |
-| Webhook CI | [***Click Here***](/docs/dashboard/application_details/webhook_ci) |
-| Danger Zone | [***Click Here***](/docs/dashboard/application_details/danger_zone) |
\ No newline at end of file
+| Section | Page Link |
+| ------------------------ |------------------------------------------------|
+| Deployments | [***Click Here***](./deployments) |
+| Runtime Logs | [***Click Here***](./runtime_logs) |
+| Ingress Rules | [***Click Here***](./ingress_rules) |
+| Update Source Code | [***Click Here***](./update_source_code) |
+| Environment Variables | [***Click Here***](./environment_variables) |
+| Persistent Volumes | [***Click Here***](./persistent_volumes) |
+| Deployment Configuration | [***Click Here***](./deployment_configuration) |
+| Webhook CI | [***Click Here***](./webhook_ci) |
+| Danger Zone | [***Click Here***](./danger_zone) |
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md b/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md
index 8d0dbc5..7001f5f 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/ingress_rules.md
@@ -6,8 +6,8 @@ sidebar_position: 3
In **Ingress Rules** section, you can find out all the associated ingress rules for the application.
-
+
To manage the ingress rules, click on `Manage Ingress Rules` button.
-This will take you to the **Ingress Rules** page where you can add, edit, and delete the ingress rules for the application. Check this docs for more details: [Ingress Rules](/docs/dashboard/ingress-rules).
\ No newline at end of file
+This will take you to the **Ingress Rules** page where you can add, edit, and delete the ingress rules for the application. Check this docs for more details: [Ingress Rules](../ingress-rules).
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md b/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md
index c8cf94e..89ed737 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/persistent_volumes.md
@@ -6,10 +6,10 @@ sidebar_position: 6
In **Persistent Volumes** section, you can see all the persistent volumes of the application. You can add new persistent volumes, edit existing persistent volumes, and also can delete persistent volumes.
-
+
You can choose pre-registered persistent volume and provide a mount path. After you change something, click on **`Apply Changes`** button to save the changes.
> **Mount Path** - The path where the persistent volume will be mounted inside the container of the application.
-If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can register a persistent volume by following [**this docs**](/docs/dashboard/persistent-volumes).
\ No newline at end of file
+If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can register a persistent volume by following [**this docs**](../persistent-volumes).
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md b/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md
index b0b3a99..2b7f8ab 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/runtime_logs.md
@@ -6,4 +6,4 @@ sidebar_position: 2
In **Runtime Logs** section, you can see all the logs of the application. The logs are updated in realtime, so you don't have to refresh the page to check the latest logs.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md b/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md
index de5b348..0b2a43c 100644
--- a/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md
+++ b/versioned_docs/version-1.x.x/dashboard/application_details/webhook_ci.md
@@ -8,7 +8,7 @@ You can manage the webhook CI of the application from the **Webhook CI** section
This **Webhook** can be used to trigger re-deployment of the application when the source code of the application is updated.
-
+
**Regenerate Webhook Token** - You can regenerate the webhook URL by tapping on **Regenerate Webhook** button. If you have exposed the webhook URL to the public by mistake, then you can regenerate the webhook URL to make the old webhook URL invalid.
diff --git a/versioned_docs/version-1.x.x/dashboard/applications.md b/versioned_docs/version-1.x.x/dashboard/applications.md
index ba15a31..56d8012 100644
--- a/versioned_docs/version-1.x.x/dashboard/applications.md
+++ b/versioned_docs/version-1.x.x/dashboard/applications.md
@@ -6,8 +6,8 @@ sidebar_position: 3
In **Application List**, you can see all the applications that you have created. You can check the status of the application, last time when it was updated, and the number of instances running for that application.
-
+
You can click on **`View Details`** button to see more details about the application.
-Check out [**Application Details**](/docs/dashboard/application_details) to learn more about it.
\ No newline at end of file
+Check out [**Application Details**](./application_details) to learn more about it.
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/change_password.md b/versioned_docs/version-1.x.x/dashboard/change_password.md
index 6525a2c..39ef0d8 100644
--- a/versioned_docs/version-1.x.x/dashboard/change_password.md
+++ b/versioned_docs/version-1.x.x/dashboard/change_password.md
@@ -6,6 +6,6 @@ sidebar_position: 11
To **change your password**, you can click on **Change Password** button in the sidebar. You will see a form like this:
-
+
You need to enter your current password and new password. Then, click on **Change Password** button and your password will be changed.
\ No newline at end of file
diff --git a/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md b/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md
index 068f08e..11a967d 100644
--- a/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md
+++ b/versioned_docs/version-1.x.x/dashboard/deploy_new_application.md
@@ -30,7 +30,7 @@ Deploying with SwiftWave is a breeze – just bring your application's source co
### 📚 Next Steps
-- [**How to check details and manage a deployed application**](/docs/dashboard/application_details/)
-- [**How to expose application to internet ?**](/docs/dashboard/ingress-rules)
-- [**How to configure persistent storage ?**](/docs/dashboard/application_details/persistent_volumes)
-- [**How to configure environment variables ?**](/docs/dashboard/application_details/environment_variables)
+- [**How to check details and manage a deployed application**](./application_details/)
+- [**How to expose application to internet ?**](./ingress-rules)
+- [**How to configure persistent storage ?**](./application_details/persistent_volumes)
+- [**How to configure environment variables ?**](./application_details/environment_variables)
diff --git a/versioned_docs/version-1.x.x/dashboard/domains.md b/versioned_docs/version-1.x.x/dashboard/domains.md
index db0e468..6a7f215 100644
--- a/versioned_docs/version-1.x.x/dashboard/domains.md
+++ b/versioned_docs/version-1.x.x/dashboard/domains.md
@@ -6,7 +6,7 @@ sidebar_position: 7
In **Domains** section, you can manage all the custom domains you have added to swiftwave.
-
+
### Register a new domain
You can click on `Register New` button and fill in the required details to register a new domain.
diff --git a/versioned_docs/version-1.x.x/dashboard/git-credentials.md b/versioned_docs/version-1.x.x/dashboard/git-credentials.md
index f98a487..61422ad 100644
--- a/versioned_docs/version-1.x.x/dashboard/git-credentials.md
+++ b/versioned_docs/version-1.x.x/dashboard/git-credentials.md
@@ -6,7 +6,7 @@ sidebar_position: 5
In **Git Credentials** section, you can check all the saved Git Credentials. You can use these credentials while deploying an application from a Git Repository.
-
+
**You can**
- **Add** a new Git Credential by clicking on `Add New` button.
diff --git a/versioned_docs/version-1.x.x/dashboard/image-credentials.md b/versioned_docs/version-1.x.x/dashboard/image-credentials.md
index baf99d2..24fd654 100644
--- a/versioned_docs/version-1.x.x/dashboard/image-credentials.md
+++ b/versioned_docs/version-1.x.x/dashboard/image-credentials.md
@@ -6,7 +6,7 @@ sidebar_position: 6
In **Image Credentials** section, you can check all the saved Image Registry Credentials. You can use these credentials while deploying an application from a Image Repository.
-
+
**You can**
- **Add** a new Image Registry Credential by clicking on `Add New` button.
diff --git a/versioned_docs/version-1.x.x/dashboard/index.md b/versioned_docs/version-1.x.x/dashboard/index.md
index 5062974..bb7296b 100644
--- a/versioned_docs/version-1.x.x/dashboard/index.md
+++ b/versioned_docs/version-1.x.x/dashboard/index.md
@@ -10,7 +10,7 @@ sidebar_position: 5
justifyContent: 'center',
marginBottom: '2rem'
}}>
-
+
+
+On the right side, you can see realtime information about the count of active instances of the application.
+
+### ⏸️ Pause App
+
+If you like to make your application offline, you can pause the application. This will stop all the instances of the application and will free up the resources.
+
+### ▶️ Resume App
+
+If you like to make your application online, you can resume the application. This will start all the instances of the application and you will be able to access the application within a few seconds.
+
+### 🏄♂️ Let's go through each section of the **Application Details** page.
+
+| Section | Page Link |
+| ------------------------ |------------------------------------------------|
+| Deployments | [***Click Here***](./deployments) |
+| Analytics | [***Click Here***](./analytics) |
+| Runtime Logs | [***Click Here***](./runtime_logs) |
+| Ingress Rules | [***Click Here***](./ingress_rules) |
+| Persistent Volumes | [***Click Here***](./persistent_volumes) |
+| Environment Variables | [***Click Here***](./environment_variables) |
+| Update App Source | [***Click Here***](./update_app_source) |
+| Deployment Configuration | [***Click Here***](./deployment_configuration) |
+| Webhook CI | [***Click Here***](./webhook_ci) |
+| Actions | [***Click Here***](./actions) |
+| Destroy | [***Click Here***](./destroy) |
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/application_details/ingress_rules.md b/versioned_docs/version-2.0.x/dashboard/application_details/ingress_rules.md
new file mode 100644
index 0000000..bd4a82a
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/application_details/ingress_rules.md
@@ -0,0 +1,11 @@
+---
+id: ingress_rules
+title: Ingress Rules
+sidebar_position: 4
+---
+
+In **Ingress Rules** section, you can find out all the associated ingress rules for the application.
+
+
+
+From V2, you can create or delete ingress rules for your application from this same page.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/application_details/persistent_volumes.md b/versioned_docs/version-2.0.x/dashboard/application_details/persistent_volumes.md
new file mode 100644
index 0000000..6eb4118
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/application_details/persistent_volumes.md
@@ -0,0 +1,15 @@
+---
+id: persistent_volumes
+title: Persistent Volumes
+sidebar_position: 5
+---
+
+In **Persistent Volumes** section, you can see all the persistent volumes of the application. You can add new persistent volumes, edit existing persistent volumes, and also can delete persistent volumes.
+
+
+
+You can choose pre-registered persistent volume and provide a mount path. After you change something, click on **`Apply Changes`** button to save the changes.
+
+> **Mount Path** - The path where the persistent volume will be mounted inside the container of the application.
+
+If you see the **Persistent Volume** select dropdown empty, that means you don't have any persistent volume registered. You can create a new persistent volume in that case by tapping on the **Create New Persistent Volume** button.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/application_details/runtime_logs.md b/versioned_docs/version-2.0.x/dashboard/application_details/runtime_logs.md
new file mode 100644
index 0000000..f58003c
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/application_details/runtime_logs.md
@@ -0,0 +1,13 @@
+---
+id: runtime_logs
+title: Runtime Logs
+sidebar_position: 3
+---
+
+In **Runtime Logs** section, you can see all the logs of the application. The logs are updated in realtime, so you don't have to refresh the page to check the latest logs.
+
+
+
+By default, it will show live logs. It includes logs from last 1 minute.
+
+So, from the provided dropdown, you can change the timeframe of the logs.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/application_details/webhook_ci.md b/versioned_docs/version-2.0.x/dashboard/application_details/webhook_ci.md
new file mode 100644
index 0000000..a828670
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/application_details/webhook_ci.md
@@ -0,0 +1,53 @@
+---
+id: webhook_ci
+title: Webhook CI
+sidebar_position: 9
+---
+
+You can manage the webhook CI of the application from the **Webhook CI** section.
+
+This **Webhook** can be used to trigger re-deployment of the application when the source code of the application is updated.
+
+
+
+**Regenerate Webhook Token** - You can regenerate the webhook URL by tapping on **Regenerate Webhook** button. If you have exposed the webhook URL to the public by mistake, then you can regenerate the webhook URL to make the old webhook URL invalid.
+
+---
+
+### 🚀 Setting Up Auto Deployment on GitHub
+
+1. Open your GitHub repository
+2. Click on **Settings** ⚙️
+3. Go to **Webhooks** from the left menu
+4. Press the **Add webhook** button 🤖
+5. Copy and paste the webhook URL in the **Payload URL** field
+6. Choose **Just the push event** from the options
+7. Click **Add webhook** to save 🚀
+8. Hooray! 🎉 Whenever you push changes, the webhook triggers, and your app auto-redeploys! 🔄
+
+---
+
+### 🚀 Setting Up Auto Deployment on GitLab
+
+1. Open your GitLab repository
+2. Click on **Settings** ⚙️
+3. Navigate to **Webhooks** from the left menu
+4. Hit the **Add New webhook** button 🤖
+5. Copy-paste the webhook URL into the **URL** field
+6. Check **Push events** from the **Triggers** section
+7. Click **Add webhook** to save 🚀
+8. Fantastic! 🎉 Push changes, trigger the webhook, and your app auto-redeploys! 🔄
+
+---
+
+### Auto Deployment on Docker Hub
+
+> Note: Make sure you have a Docker Hub account, and you need administrative access to the project.
+
+1. Open your Docker Hub account
+2. Go to the specific repository 📦
+3. Click on **Webhooks** 🌐
+4. Add the webhook URL
+5. Ensure you have administrative access to the project
+6. Click on **Create** 🚀
+7. Done! 🎉 Push changes, trigger the webhook, and your app auto-redeploys! 🔄
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/applications.md b/versioned_docs/version-2.0.x/dashboard/applications.md
new file mode 100644
index 0000000..843d898
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/applications.md
@@ -0,0 +1,13 @@
+---
+id: applications
+title: 📦 Applications
+sidebar_position: 6
+---
+
+In **Application List**, you can see all the applications that you have created. You can check the status of the application, last time when it was updated, and the number of instances running for that application.
+
+
+
+You can click on **`View Details`** button to see more details about the application.
+
+Check out [**Application Details**](./application_details) to learn more about it.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/change_password.md b/versioned_docs/version-2.0.x/dashboard/change_password.md
new file mode 100644
index 0000000..fd894d1
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/change_password.md
@@ -0,0 +1,11 @@
+---
+id: change_password
+title: 🔒 Change Password
+sidebar_position: 15
+---
+
+To **change your password**, you can click on `Administration > Change Password` in the sidebar. You will see a form like this:
+
+
+
+You need to enter your current password and new password. Then, click on **Change Password** button and your password will be changed.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/deploy_new_application.md b/versioned_docs/version-2.0.x/dashboard/deploy_new_application.md
new file mode 100644
index 0000000..669dd72
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/deploy_new_application.md
@@ -0,0 +1,34 @@
+---
+id: deploy_new_application
+title: 🔨 Deploy New Application
+sidebar_position: 3
+---
+
+
+In **SwiftWave** you can deploy your application from various sources.
+- 📦 Git Repository (Supports both HTTP and SSH)
+- 🐳 Docker Image Repository
+- If your code isn't on a Git or Image Repository, worry not! Simply choose your code folder and upload it. 📂
+
+### 🚀 Deploy Application
+1. Click on the `Deploy New Application` button on the *Sidebar* of the **Dashboard**.
+2. Choose your application source (Git Repository, Docker Image, or Upload Code Folder) option.
+3. Fill in the required details.
+4. Click on `Generate Configuration` button.
+5. You can choose to edit generated Dockerfile by clicking on `View/Modify Dockerfile` button. If you feel it detected some wrong services, you can change the detected service and choose another template.
+6. Edit Build Arguments, if required.
+7. Put the command, if you need to override the default command of dockerfile.
+8. Click on `Confirm & Proceed to Next Step` button.
+9. At top, you can configure no of application instances you require. (You can also configure this later.)
+10. Configure your application's environment variables. (You can also configure this later.)
+11. You can also configure persistent storage for your application. (You can also configure this later.)
+12. Click on `Click to Confirm & Deploy` button.
+13. Your application will be deployed in a few minutes. 🚀
+14. You can check the build logs and status in the same page.
+
+
+### 📚 Next Steps
+- [**How to check details and manage a deployed application**](./application_details/)
+- [**How to expose application to internet ?**](./ingress-rules)
+- [**How to configure persistent storage ?**](./application_details/persistent_volumes)
+- [**How to configure environment variables ?**](./application_details/environment_variables)
diff --git a/versioned_docs/version-2.0.x/dashboard/deploy_stack.md b/versioned_docs/version-2.0.x/dashboard/deploy_stack.md
new file mode 100644
index 0000000..517b08d
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/deploy_stack.md
@@ -0,0 +1,35 @@
+---
+id: deploy_stack
+title: 🔨 Deploy Stack
+sidebar_position: 4
+---
+
+
+
+In **SwiftWave**, you have also support to deploy multiple applications using stack file.
+
+This stack file has same format as docker stack file. Still it doesn't support all the features of docker stack file.
+
+#### Available Features
+
+| Name | Supported |
+| --------------------- | --------- |
+| services | Yes |
+| image name | Yes |
+| deploy mode | Yes |
+| command | Yes |
+| replicas | Yes |
+| volumes | Yes |
+| environment variables | Yes |
+| cap_add | Yes |
+| sysctls | Yes |
+| ports | No |
+| networks | No |
+| depends_on | No |
+| healthcheck | No |
+
+:::tip
+
+You can use ingress rules to expose your application to internet.
+
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/domains.md b/versioned_docs/version-2.0.x/dashboard/domains.md
new file mode 100644
index 0000000..6036f13
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/domains.md
@@ -0,0 +1,36 @@
+---
+id: domains
+title: 🌐 Domains
+sidebar_position: 10
+---
+
+In **Domains** section, you can manage all the custom domains you have added to swiftwave.
+
+
+
+### Register a new domain
+You can click on `Register New` button and fill in the required details to register a new domain.
+
+### Delete a domain
+You can click on `Delete` button to delete a domain.
+> Note : You can only delete a domain if
+> - it is not being used by any application
+> - no ingress rules linked to it
+> - no redirect rules linked to it
+
+### Verify DNS
+You can click on `Verify DNS` button to verify if domain is correctly pointing to the proxy server.
+
+:::tip
+
+- If you are using cloudflare as your DNS provider, it is recommended to use DNS only mode while mapping your domain to the proxy server IP.
+- If you want to use Cloudflare Proxy Mode, go to `Domain SSL/TLS Mode` section and mark `Encryption Mode` to `Full`. After this, all your application hosted on swiftwave should use `https` protocol in all ingress rules.
+
+:::
+
+
+### Issue SSL Certificate 🛡️
+Swiftwave has Let's Encrypt integration. You can issue a SSL certificate for your domain by clicking on `Issue SSL` button.
+
+### SSL Auto Renewal
+From V2, Swiftwave supports SSL auto renewal. You don't need to worry about renewing your SSL certificate manually.
diff --git a/versioned_docs/version-2.0.x/dashboard/git-credentials.md b/versioned_docs/version-2.0.x/dashboard/git-credentials.md
new file mode 100644
index 0000000..7dd618b
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/git-credentials.md
@@ -0,0 +1,40 @@
+---
+id: git-credentials
+title: 🐙 Git Credentials
+sidebar_position: 8
+---
+
+In **Git Credentials** section, you can check all the saved Git Credentials. You can use these credentials while deploying an application from a Git Repository.
+
+
+
+Git Credentials vault now supports both HTTP and SSH authentication key.
+
+**You can**
+- **Add** a new Git Credential by clicking on `Add New` button.
+- **View** a Git Credential by clicking on `View Details` button.
+- **Edit** a Git Credential by clicking on `Edit Details` button.
+- **Delete** a Git Credential by clicking on `Delete` button.
+ > Note : You can only delete a Git Credential if it is not being used by any application.
+
+#### Add HTTP Credential
+
+
+
+Choose the type as `HTTP` and fill in the required details.
+
+#### Add SSH Credential
+
+
+
+Choose the type as `SSH` and fill in the required details.
+- If you like to use your own private key, put that in OpenSSH format in the `Private Key` field.
+- Else, leave that field empty and a new key will be generated for you.
+
+**View the public key**
+
+To view the public key, hit the `View Details` button after creating your SSH Git credential.
+
+
+
+You can add this key to your GitHub account and use it to access the private repository.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/image-credentials.md b/versioned_docs/version-2.0.x/dashboard/image-credentials.md
new file mode 100644
index 0000000..3d58820
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/image-credentials.md
@@ -0,0 +1,15 @@
+---
+id: image-credentials
+title: 🐳 Image Credentials
+sidebar_position: 9
+---
+
+In **Image Credentials** section, you can check all the saved Image Registry Credentials. You can use these credentials while deploying an application from a Image Repository.
+
+
+
+**You can**
+- **Add** a new Image Registry Credential by clicking on `Add New` button.
+- **Edit** an existing Image Registry Credential by clicking on `Edit Details` button.
+- **Delete** a Image Registry Credential by clicking on `Delete` button.
+ > Note : You can only delete a Image Registry Credential if it is not being used by any application.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/index.md b/versioned_docs/version-2.0.x/dashboard/index.md
new file mode 100644
index 0000000..31cbd52
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/index.md
@@ -0,0 +1,40 @@
+---
+id: swiftwave_dashboard
+title: 🖥️ SwiftWave Dashboard
+hide_table_of_contents: true
+sidebar_position: 5
+---
+
+
+
+
+
+
+SwiftWave Dashboard is a web-based interface for controlling all resources, including apps, domains, persistent volumes, and more. It is SwiftWave's main management interface.
+
+
+
+## Sections of Dashboard
+| Section | Description | Link |
+| ---------------------------- | --------------------------------------------------------------------- |----------------------------------------------|
+| 🔒 Log In | Log in to SwiftWave Dashboard | [***Click Here***](./log_in) |
+| 🏪 Swiftwave App Store | Install apps in one click from the SwiftWave App Store | [***Click Here***](./swiftwave_app_store) |
+| 🔨 Deploy Application | Deploy new application on your server | [***Click Here***](./deploy_new_application) |
+| 🔨 Deploy Stack | Deploy application using stack file | [***Click Here***](./deploy_stack) |
+| 📦 Persistent Volumes | List of all persistent volumes created on your server & manage them | [***Click Here***](./persistent-volumes) |
+| 📦 Applications | List of all applications deployed on your server & manage them | [***Click Here***](./applications) |
+| 📦 Application Details | View details of an application | [***Click Here***](./application_details) |
+| 🐙 Git Credentials | Manage git credentials for your applications | [***Click Here***](./git-credentials) |
+| 🐳 Image Registry Credentials | Manage docker image credentials for your applications | [***Click Here***](./image-credentials) |
+| 🌐 Domains | Manage custom domains, SSL for your applications | [***Click Here***](./domains) |
+| 🚪 Ingress Rules | Manage exposed domains and routes for your applications | [***Click Here***](./ingress-rules) |
+| 🔄 Redirect Rules | Manage domain redirection and HTTPS redirection for your applications | [***Click Here***](./redirect-rules) |
+| 🖥️ Manage Servers | Manage the onboarded servers for your SwiftWave instance | [***Click Here***](./manage-servers) |
+| 👥 Manage Users | Manage admin users for your hosted SwiftWave instance | [***Click Here***](./manage-users) |
+| 🔒 Change Password | Change password for currently logged In user | [***Click Here***](./change_password) |
+| 🖥️ Manage System | Manage the system settings for your SwiftWave instance | [***Click Here***](./manage-system) |
+
diff --git a/versioned_docs/version-2.0.x/dashboard/ingress-rules.md b/versioned_docs/version-2.0.x/dashboard/ingress-rules.md
new file mode 100644
index 0000000..20a7614
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/ingress-rules.md
@@ -0,0 +1,64 @@
+---
+id: ingress-rules
+title: 🚪 Ingress Rules
+sidebar_position: 11
+---
+
+In **Ingress Rules** section you can manage your ingress rules. You can add or delete ingress rules.
+
+
+
+### 😅 Don't know what ingress rules are ?
+In layman's terms, ingress rules are the rules that will connect your domain to your application.
+
+For example, you have an web application (named **myapp**) running on port 3000 and you want people can access it via `https://myapp.com`. You can do that by creating an ingress rule that will connect your domain to your application.
+
+```
+myapp.com [https] -> myapp:3000
+```
+
+### Add Ingress Rule for Deployed Application
+To add an ingress rule, click on **Add New** button. You will see a form like this:
+
+
+You can choose the protocol your application required.
+- **HTTP**: You can choose any port for your application. It's recommended to use port 80 for HTTP.
+- **HTTPS**: Currently, only port 443 is supported.
+ > Note: To enable, **HTTPS Redirection**, you will have to create a redirect rule. You can follow [**this docs**](./redirect-rules#https-redirect) section to create a redirect rule.
+- **TCP**: If your application relies on TCP protocol, you can choose this option. You can choose any port for your application.
+ > NOTE : In case of TCP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
+- **UDP**: If your application relies on UDP protocol, you can choose this option. You can choose any port for your application.
+ > NOTE : In case of UDP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
+
+Then, you can choose the domain you want to connect to your application. If you don't have any domain, you can click on `Register New Domain` to add a new domain.
+
+**Finally**, you can choose the application you want to connect to your domain.
+
+Hurrah! You have successfully created an ingress rule. Now, you can access your application via your domain.
+It takes upto 1 minute to apply the changes.
+
+> **Note :** If you have created an ingress rule for port except 80 and 443, you will have to wait for 1~2 minutes to see the effect. This is because, we have to reload HAProxy or UDPProxy and other services to expose the port. You should open the port in your server's firewall too.
+
+
+### Add Ingress Rule for External Application
+
+You can use the integrated proxy in Swiftwave to expose certain applications to the outside world if you are unable to deploy them in swiftwave for some reason.
+
+:::info
+
+That external application should use this docker overlay network > `swiftwave_network`
+
+:::
+
+For that, click on **Add New** button. In the form, you will see a label `Need to expose some external services ?`. Click on it and you will see a form like this:
+
+
+
+From here, you can type the container / service name of that external application and create an ingress rule for it.
+
+Hurrah!
+
+
+### Delete Ingress Rule
+To delete an ingress rule, click on **Delete** button. You will see a confirmation dialog. Confirm it and your ingress rule will be deleted.
+
diff --git a/versioned_docs/version-2.0.x/dashboard/log_in.md b/versioned_docs/version-2.0.x/dashboard/log_in.md
new file mode 100644
index 0000000..d8ba9b8
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/log_in.md
@@ -0,0 +1,11 @@
+---
+id: log_in
+title: 🔒 Log In
+sidebar_position: 1
+---
+
+When you will visit the dashboard for the first time, you will be asked to log in.
+
+
+
+You can log in using the credentials, you created while setting up swiftwave.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/manage-servers.md b/versioned_docs/version-2.0.x/dashboard/manage-servers.md
new file mode 100644
index 0000000..95d5062
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/manage-servers.md
@@ -0,0 +1,58 @@
+---
+id: manage-servers
+title: 🖥️ Manage Servers
+sidebar_position: 13
+---
+
+
+
+## Onboard Server
+1. Click the `Add Server` button
+2. Put the IP Address of the server you want to add
+
+ 
+
+ :::tip
+
+ If your server has no public or private IP address, you can use `127.0.0.1` as the IP Address.
+
+ :::
+3. Click the `Register Server` button
+4. Click on `Setup Server` to configure the server
+5. Follow the instructions to configure the server
+
+## Server Analytics
+
+You can click on `Analytics` to view the server analytics.
+
+
+
+The server analytics page shows the following information:
+
+- CPU Usage
+- Memory Usage
+- Disk Usage
+- Network Usage
+
+## Server Logs
+
+You can click on `View Logs` to view the server logs.
+
+
+
+It only has logs from actions that happen on that specific server.
+
+## Actions
+You can perform the following actions on a server:
+
+
+
+All actions are self-explanatory.
+
+## Web Console
+
+Once you have successfully onboarded a server, you can SSH to server using the web console.
+
+Click on `View Actions > Web Console` to open the web console.
+
+
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/manage-system.md b/versioned_docs/version-2.0.x/dashboard/manage-system.md
new file mode 100644
index 0000000..d5f3dbd
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/manage-system.md
@@ -0,0 +1,26 @@
+---
+id: manage-system
+title: 🖥️ Manage System
+sidebar_position: 16
+---
+
+Under `Manage System` option of sidebar, you can have three options:
+- System Logs
+- System Configuration
+- System Restart
+
+## System Logs
+
+You can click on `System Logs` to view the system logs. It have both normal and error logs.
+
+
+
+## System Configuration
+
+You can click on `System Configuration` to view or modify the system configuration.
+
+
+
+## System Restart
+
+To restart Swiftwave, click on "System Restart." There will be no downtime, and all of your applications will work as they do now.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/manage-users.md b/versioned_docs/version-2.0.x/dashboard/manage-users.md
new file mode 100644
index 0000000..beba5b5
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/manage-users.md
@@ -0,0 +1,23 @@
+---
+id: manage-users
+title: 👥 Manage Users
+sidebar_position: 14
+---
+
+In **Manage Users** section, you can manage all the users of your organization.
+
+
+
+**You can -**
+1. **Create** a new user by clicking on `Create User` button.
+ > ⚠️ **Note :** Currently, you can only create a user with `admin` role, so new user will have all the permissions.
+ > We will be adding more roles for granular permission control soon.
+
+ After clicking on `Create User` button, you will see a form like this:
+
+ 
+
+ Enter the required details and click on `Create` button. The user will be created.
+
+2. **Delete** a user by clicking on `Delete` button.
+ > **Note :** You can't delete current logged in user.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/persistent-volumes.md b/versioned_docs/version-2.0.x/dashboard/persistent-volumes.md
new file mode 100644
index 0000000..385e929
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/persistent-volumes.md
@@ -0,0 +1,82 @@
+---
+id: persistent-volumes
+title: 📦 Persistent Volumes
+sidebar_position: 5
+---
+
+In **Persistent Volumes** section, you can see all the persistent volumes created across your cluster for your applications.
+
+
+
+### Create a Persistent Volume
+1. **Local Volume**
+ Local volume is a volume that is created on the local storage of the node. It is not shared across the cluster.
+
+ - Click on `Add New` button.
+ - 
+ - Choose a unique name for the volume and can't contain spaces.
+ - Choose type `Local`.
+ - Click on `Register` button and the volume will be created.
+
+2. **NFS Volume**
+ You can create a NFS volume to share the volume across the cluster and also to keep your data more reliable.
+
+ - Click on `Add New` button.
+ - 
+ - Choose a unique name for the volume and can't contain spaces.
+ - Choose type `NFS`.
+ - Fillup NFS server details.
+ > Note : Duly check the NFS server details before submitting. You can't change the NFS server details once the volume is created.
+ - Click on `Register` button and the volume will be created.
+
+3. **SAMBA Share / CIFS Volume**
+ You can mount a SAMBA share or CIFS volume to share the volume across the cluster and also to keep your data more reliable.
+
+ - Click on `Add New` button.
+ - 
+ - Choose a unique name for the volume and can't contain spaces.
+ - Choose type `CIFS`.
+ - Fillup CIFS server details.
+ > Note : Duly check the CIFS server details before submitting. You can't change the CIFS server details once the volume is created.
+ - Click on `Register` button and the volume will be created.
+
+### Delete a Persistent Volume
+Just click on `Delete` button to delete a persistent volume.
+
+### Analyze Size of Persistent Volume
+You can click on `Fetch Size` button to fetch size of the persistent volume.
+
+### Backup Volume
+1. You can backup and take snapshot of the persistent volume by clicking on `Create Backup` button.
+2. You can choose type of backup.
+ - **Local** : The backup will be stored locally in the server itself.
+ - **S3** : The backup will be stored in S3 bucket. You need to configure S3 beforehand to avail this feature.
+ :::tip
+
+ TODO add system config page
+
+ :::
+3. Submit to create backup.
+4. You can open the backup history by `Show Backups` button to see the status of the backup.
+
+### Backup History
+You can click on `Show Backups` button to see the backup history of the volume.
+
+
+
+- You can check status of old backups.
+- You can also download the backup file by clicking on `Download Backup` button.
+
+
+### Restore Volume
+1. You can upload a backup file to restore the volume by clicking on `Restore Now` button.
+2. Upload the backup file.
+3. Submit to restore the volume.
+4. You can open the restore history by `Show Restores` button to see the status of the restore.
+
+### Restore History
+You can click on `Restore History` button to see the restore history of the volume.
+
+
+
+- You can check status of all restores.
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/redirect-rules.md b/versioned_docs/version-2.0.x/dashboard/redirect-rules.md
new file mode 100644
index 0000000..903b534
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/redirect-rules.md
@@ -0,0 +1,33 @@
+---
+id: redirect-rules
+title: 🔄 Redirect Rules
+sidebar_position: 12
+---
+
+In **Redirect Rules** section you can manage your redirect rules. You can add or delete redirect rules.
+
+
+
+### 😅 Don't know what redirect rules are ?
+In layman's terms, redirect rules are the rules that will redirect your domain to another URL.
+
+- Maybe you have a domain `github.portfolio.com` and you want to redirect it to your github profile `https://github.com/tanmoysrt`, you can do that by creating a redirect rule.
+- Also, if you want to setup a HTTPS redirect, you can do that by creating a redirect rule, which will redirect all the HTTP requests from your domain to HTTPS one.
+
+### Add Redirect Rule
+It's very easy to add a redirect rule. Just click on **Add New** button and you will see a form like this:
+
+
+
+1. Choose the protocol (http/https) and domain you want to redirect.
+2. Choose the url where you want to redirect your domain.
+3. Click on **Register** button and you are done.
+
+### Delete Redirect Rule
+To delete a redirect rule, click on **Delete** button. You will see a confirmation dialog. Confirm it and your redirect rule will be deleted.
+
+### HTTPS Redirect
+If you want to redirect all the HTTP requests from your domain to HTTPS one, you can do that by creating a redirect rule.
+Suppose, you want to enable HTTPS redirect for `myapp.com`. You can do that by creating a redirect rule like this:
+- **Domain**: `myapp.com`
+- **Redirect URL**: `https://myapp.com`
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/dashboard/swiftwave_app_store.md b/versioned_docs/version-2.0.x/dashboard/swiftwave_app_store.md
new file mode 100644
index 0000000..414a2b7
--- /dev/null
+++ b/versioned_docs/version-2.0.x/dashboard/swiftwave_app_store.md
@@ -0,0 +1,29 @@
+---
+id: swiftwave_app_store
+title: 🏪 Swiftwave App Store
+sidebar_position: 2
+---
+
+
+
+
+
+
+
+
+
+From Swiftwave App Store, you can install any app in few clicks.
+
+### Steps to install any app from Swiftwave App Store
+1. Go to Swiftwave App Store
+2. Search for the app you want to install
+3. Click on the app you want to install
+4. Click the variant you want to install
+5. Click the install button
+6. Fill up the required details
+7. Configure the ingress rules. You can also ignore those by tapping on the cross icon
+8. Click on the install button
+9. That's it!
\ No newline at end of file
diff --git a/versioned_docs/version-2.0.x/development_setup.md b/versioned_docs/version-2.0.x/development_setup.md
new file mode 100644
index 0000000..39876dc
--- /dev/null
+++ b/versioned_docs/version-2.0.x/development_setup.md
@@ -0,0 +1,79 @@
+---
+id: development_setup
+title: 👨💻 Development Setup
+sidebar_position: 7
+---
+
+Let's get started with SwiftWave Development Setup!
+
+## 📦 Pre-requisites
+1. You need a linux system for development of SwiftWave.
+2. Install curl, git, unzip and tar utilities.
+ ```bash
+ # For Debian/Ubuntu based distros:
+ sudo apt install curl git unzip tar make
+
+ # For Fedora based distros:
+ sudo dnf install curl git unzip tar make
+ ```
+3. Install docker (Skip this step if you already have docker installed)
+ ```bash
+ curl -fsSL https://get.docker.com | sudo bash -
+ ```
+4. Install Golang by following [this guide](https://golang.org/doc/install)
+5. Install NodeJS by following [this guide](https://deb.nodesource.com/)
+6. You are all set! 🎉
+
+## 📥 Local Installation
+1. Fork and clone SwiftWave repository
+ ```bash
+ git clone git@github.com:
+