UsersDevelopersPortals
Search…
Skynet Portal Operator Docs
Getting Started
Portal Workshops
Portal Workshop
Portal Concepts
Portal Stack
Ansible
Types of Portals
Prerequisites
Overview
DNS
Hosting Provider
Ansible
Secrets Management
SiaCoin
Portal Setup
Overview
DNS Setup
Server Initialization
Single Portal Setup
Deployment
Discord Notifications
Stripe
PORTAL MANAGEMENT
Upgrading
Retiring Webportal Servers
Handling Abuse Requests
Getting Help
Changelog
Troubleshooting
Important Code Repos
Skynet Webportal
Skynet Accounts
skyd
Ansible Playbooks
Ansible Private Sample
Powered By GitBook
Types of Portals
There are many different types of portals that you can run. Much of the setup is the same and the differences largely come down to DNS settings and various environment variables.

Single Server Portal

The most basic version of a portal is a single server portal. This means that https://myportal.com points to a single server running the skynet portal stack.

Multi-Server Portal

The next most common version of a portal is a multi- server portal. This means that https://myportal.com is load balanced across 2 or more servers running the skynet portal stack. These servers most likely have DNS records like https://sev1.myportal.com and https://sev2.myportal.com for example
NOTE: There is currently a limit of 50 servers per portal. This limit is due to the limitations of the mongo cluster that is part of the portal stack.

Transitioning from Single to Multi-Server Portal

Many people will start off with a single server portal and then decide they would like to scale up and make the portal a multi-server portal.
While this is possible there is currently no documentation on it.

Restricted Access Portal

Portal operators have the ability to restrict access to their portals in a few different ways. Portal operators might want to restrict access to protect against abusive users, or because they only want friends and family to use their portal for example.
By default, portals are set up to require registration, this means portals require users to have a portal account. This can be updated to allow unregistered users if you want your portal to be fully open to the public.
Additionally, you can refine the registered access to differentiate between paying users and just users that have accounts.

Private Portal

If you are interested in running a private portal, there are a few options depending on what your end goal is.
Reach out to us on our discord to discuss different options to best understand what you are looking for.
Portal Concepts - Previous
Ansible
Next - Prerequisites
Overview
Last modified 4mo ago
Copy link
Outline
Single Server Portal
Multi-Server Portal
Transitioning from Single to Multi-Server Portal
Restricted Access Portal
Private Portal