lordfokas / massiveoctomustache Goto Github PK

Specifically stuff in the mechanics section:

• Mechanics
  • Abstract Bus
  • Lazy Intercom Protocol

Pointed out by Loaf in the IRC channel that it doesn't actually say anywhere that it needs it.

I'll add it when I get the chance.

Was just thinking we could potentially have a "dev build" entry in the downloads list that points to the latest build. Have it have all the necessary warnings on it and stuff which can allow for people to test dev code if they want

I think the only place that PHP is used on the production site is for the initial index redirection, if a pure html alternative could be made that would be helpful as I'm moving stuff from one server to another and am going with Nginx for the webserver and don't want to have to fuck about with getting PHP working on there.

My site is gonna be more fun to switch over, yay :/

Little fun project for me :D, tasks include:

• 1. Have a script that listens for commits/PR's pushed to Development branch (Either via GitHub POSTs or GitHub's notification API) by either @LordFokas or Myself containing the phrase bot build this
• 2. git pull the repo's dev branch into a local folder
• 3. HTTP GET the rebuild.php on the local webserver (or the PHP CLI)
• 4. git commit the changes and push up to GitHub

Normally this wouldn't be needed as people submitting changes should do the rebuild on their end before submitting a PR but for a simple change like a typo it can be useful.

We need to come up with a format for this, once we have a template for it I'll go ahead and add the information to the pages

@LordFokas you will need to delete the beanch and re-create it from the master branch ( I can always re-submit the modification of the readme and stuff )