Welcome to the Skyra Wiki!

This wiki will provide extra documention for developers that guide contributors on how to manage and/or setup Skyra. As per the way the Skyra core team thinks about self-hosting this wiki will not help you self host Skyra. These documents are exclusively meant for developers.

We are not supportive of the idea of people self hosting Skyra as we put a very high priority on providing the best experience we can for our end-users. This image of Skyra will be diminished if people self-host her as they will not use identical architecture to what we do and likely not put in the same amount of effort as we do. If Skyra is lacking a feature you'd like to see, please refer to the developing guidelines above and if you can add that feature it will be in Skyra to stay.

Furthermore, Skyra has not been build with the idea of self hosting in mind and she makes use of many services that you will need to maintain in a production environment for full functionality. For example

• Skyra uses many external API's for which you would have to create API keys
• Skyra uses Lavalink as music module, this means you need to host your own instance of Lavalink (a Java application)
• While Skyra can work with a JSON based database, it is extremely ill-advised to do so in production. Instead in production you should be using PostgreSQL, another thing to host yourself.
• Skyra requires Evlyn in order to run properly, this means you will also need to host this Node.JS application on the same network as Skyra

All this said, if you really are going to self-host Skyra please take heed, she will absolutely not run on services such as Glitch or Heroku. You will need a VPS (Virtual Private Server), for example from a provider such as Netcup (our provider) or DigitalOcean.

Sidenote, if you really think you're clever enough to self host then you're probably also smart enough to write your own bot.