Roadmap
Changelog

Have something to say?

Tell Webdock.io how they could make the product more useful to you.

Planned

Ability to shut down server instead of getting overage charges

I think there should be an option to stop traffic or straight up shut down a server automatically if your traffic hits the plan limits instead of getting overage charges. The reason being is that some developers are fine with shutting down their servers instead of generating higher bills.

Atanas About 2 months ago

1

💡 Feature Request

SSL Configuration Presets

Would be neat to be able to be able to set some presets to avoid manually editing the config. Presets would be intermediate/modern from https://ssl-config.mozilla.org/ and applicable to either LAMP or LEMP stacks. Alternatively, maybe a web editor for the config would be a better option, perhaps locked behind a higher tier/extra service? Can use nginx -t to validate configs before they are loaded to prevent incorrect configurations from being used.

Tyler Dunn 3 months ago

1

💡 Feature Request

Open

Arabic language, RTL system

This wonderful, flexible and distinguished platform lacks an important thing in order for it to be suitable for all users from all over the world, which is providing the RTL system, on which nearly 30 languages ​​in the world depend, spoken by more than a billion people, the most prominent of which are Arabic, Persian, and Urdu, and other languages. I hope to provide this feature in two stages if possible, first providing the Arabic language, then providing the RTL system.

Abdellahi Ebbebah 3 months ago

1

💡 Feature Request

Automated Up-/Downscaling of profiles

Sometimes, apps running on servers need a lot of power, other times (most of the time) they are happy with very few resources. One example is Authentik, it needs a lot of CPU processing power when it starts, but during runtime, it idles at a few %. So I am proposing implementing AutoScaling of server profiles, paired with configurable limits, up to what and down to what a respective server can scale.

Epsilon PS _ Paul Schiffer 7 months ago

2

💡 Feature Request

Expand Default Server Domain functionality

Currently, the only way to change the Default Server Domain of "servername.vps.webdock.cloud" is to connect a CloudFlare account so A and AAAA records can be deployed automatically. But sometimes, this is not necessary, for example if we use CloudFlare Tunnel or other Zero Trust products which circumvent port forwardings by running through an edge network and make the A and AAAA record for the servers origin IP unneeded. So I propose to rebuild or expand the current functionality in the following way: - Allow to "connect" a domain to a Webdock account by verifying it (ownership) through industry-standard TXT records. - Allow to change the Default Server Domain with a verified domain. - If the user wants to automatically deploy A and AAAA records, there can be a button that triggers this workflow, CloudFlare has a usable workflow for this already, Microsoft uses this for example for MS365 and connecting a new domain (verifying ownership and also deploying the DNS records). -- It works by calling a specific endpoint of CloudFlare to prompt the creation of various DNS records, in this case the A and AAAA records for the server. -- And this workflow will use the login cookie of the current browser session to land in the correct CloudFlare tenant. - If no A and AAAA records are necessary, the button can just not be pressed, the server now has the new Default Server Domain and everyone is happy :) And this functionality could be on either account level and/or server level, to e.g. just change the domains of some servers, not change the default of the account.

Epsilon PS _ Paul Schiffer About 1 year ago

5

💡 Feature Request