• Pipenv
• Docker
  • Compose

• Make a proper README
  • Project description
  • Setup instructions

Perhaps some additional stuff on the wiki?

• Automated linting (#7)
• Automated push to PyPi when a PR to release is merged (#9)

Hello Traveler!

This was the original idea back in the days when the project was called server-bootstrap. This is kept for archiving purpose!

The original proposal

Abstract

Here is the plan that I have in mind for this project, it should get updated as we go along. The plan for this project is to have a simple web interface allowing you to (re)sync development servers and generate config files for it.

Server generation

When a new server is generated, a bot will create a new server, gather the current state of PyDis, recreate any channel, roles, emotes and webhooks needed for a working test server. Then, the bot would generate a config file using the new IDs. This config file should be as succinct as possible, and do not override any potentially user defined setting, which is currently impossible (see below).
The bot would then add to the guild the user who requested the new server using the OAuth token they provided when requesting the server, send a message with some useful links (contributing page, a link to re-invite the bot to this specific guild, and the song “lint before you push” of course) along with the config file, then leave.

Re-syncing

servers
When the bot is invited to a server, either using the link it dropped when generating the server or using an invite link on the website, it will ask users with the Manage Server to confirm the changes, and will proceed to create any missing objects, and delete any non-referenced objects, generate the config again, and send the end message again.

Getting the state of PyDis

This is the current problem. We want to only have as little things on the server as possible, so we thought about using the config file on the bot repo, but the current format doesn’t allow us to have enough information to generate a good test server (lack of the channel order, role colors, emote source file...). Also, because the current setup uses YAML anchors, it is impossible to have a config file with only the stuff provided by discord.
Another thing I’d to point out, if we decide to use a file from another repo using the GitHub API or something similar, we would have to allow users to select a remote and a branch to choose from (defaulting to python-discord/master). I think mark has some ideas about refactoring the bot config.

Once the container will be properly pushed on GitHub Packages (#2), we can setup the Continuous Delivery on this project.