Enabling or disabling components
Last updated: September 13th 2019
Use our scripts for easy management
Some software is enabled or disabled by default on Webdock Server Stacks. We have tried to go for sane defaults which pose as little friction as possible to the casual user, without compromising security.
However, you may want to disable FTP on your server for example, if you don't use it or feel like it's a security risk.
Therefore, we have created a series of scripts which are installed by default in your Webdock account or which can be found in the script library to help you enable or disable certain components easily.
Where can I find these scripts?
- Head on over to your Account Page.
- There you will find a card/section titled Scripts & Files
- Here you can browse the scripts already installed in your account, or click LIBRARY to browse for more
Feel free to click the edit icon on a script to inspect how it works.
How do I deploy these scripts to a server?
- Click on a server in your account, and then in the main server menu go to Cronjobs & Scripts
- On this page, you will find on the right hand side a section titled Deploy a script or file
- Here you can select any of the scripts in your account and send it to your server and optionally run it immediately
- Once deployed you can see the scripts on your server which Webdock knows about in the table in the bottom of the page
- From here you can run the script again at any time
Why is MongoDB installed, but disabled by default?
MongoDB is awesome and is used by a lot of developers. However, in many cases MongoDB will just sit there doing nothing. As the Mongo daemon takes about 400mb of RAM while just idling, we thought it best to disable it by default, and then create a simple script you can run to enable it.
We may do the same for other components in the future which we are considering including in our stacks, such as PostgreSQL. If you have any preference for software you use which we haven't included in our stacks, please let us know and we may include it in future revisions of our stacks.