Tainbot 2.0

test push master1

Personal discordbot rewrite with glitch.com in mind.

• use github webhooks to allow dev on my own environment, then automatically updated to glitch.com

• write testing (npm jest) as I develop. should be able to locally test before ever needing to push.

• create a simple & functional logging system. (npm debug, winston, marcus, etc..) crashes need to be logged properly, and crash loops should be avoided. writing logs to files should be an option, but not required. along with daily logging etc.. logger should be able to print filename, method name, stack, etc.. as a way to make titles for different log threads. formatting should be easy peasy

• • this should be it's own project. submitted to npm

• adhere to airbnb styling etc.. project should be formatted before ever pushing.

• format -> test -> push -> update

• development is one directional. we should never be editing on glitch.com. consider the website production.

Glitch <> GitHub Sync

Experimental two-way syncing between a Glitch project and a GitHub repo, using git hooks and githubhook.

Glitch takes periodic snapshots of a project with git. When a new snapshot is taken, a git hook pushes the latest changes in the Glitch project to your GitHub repo. The Glitch project also looks out for Webhooks about changes to the GitHub repo, and runs a pull request to get the latest changes.

The result is syncing of changes when they're made on Glitch or GitHub.

Setup

• Remix this Glitch project.

• Create a new repo on GitHub, initializing it with a readme. Then export your Glitch project to that repo.

• Set a secret string for GITHUB_WEBHOOK_SECRET in the .env file in your Glitch project.

• Create a Webhook on GitHub using the same secret string. From the repo on GitHub, go to Settings > Webhooks > Add Webhook and use https://yourproject.glitch.me/github/callback as the callback URL.

• Get Glitch to remember your GitHub login details (we've added .git-credentials to .gitignore so they don't get shared on GitHub). From the console in Glitch, run:

  git config credential.helper store
  git push https://github.com/yourUser/yourRepo.git master --force
  

  Log in with your username and password, and it'll be remembered so you won't need to specify them again (if you use 2-Factor Auth, then you need to generate a personal access token to use as your password).

• Then create a git hook in .git/hooks called post-commit, with the following content:

  #!/bin/sh
  git pull https://github.com/yourUser/yourRepo.git
  

  Make sure it's executable using chmod +x post-commit.

• Update the pull request URL in git.sh to pull from your own repo.

• Make your project private so your .git-credentials can't be remixed.