So spotlight, I made a auto-updater for this actually.

[ghost]

https://github.com/WiiLink24-Extensions/git-pull-cron

Just one bug in the markdown, that's the only thing that isn't fixed. Everything else works great from what I can see from testing.

How to Compile

For compiling WiiLink24's custom version, you will need to install the FS module, follow the enviroment setup guide inside this README by clicking here and then do the following:

• Firstly, run node compile.js to generate the Gruntfile.coffee file.
  
• Secondly, run node generate.js to generate the .npmignore file.
  
• Thirdly, run node rcgen.js to generate the .jshintrc file.
  
• Fourthly, run node packagegen.js to generate the package.json file.
  
• Fifthly, run node clean.js to remove unneeded files to clean your installation up.
  
• Sixthly,run npm install to install this module.
  
• Then to test the functionality, run node test.js to test it.
  
• Then finally, choose the production script you want to run.
  
• The current ones we have made:
  

  Current Scripts

  filemaker.js -- File-Maker updating script, which saves WiiLink24 a lot of work with this particular one!
  vulcan.js -- Vulcan schema updating script, which also saves WiiLink24 a lot of work with this particular one!
  roomserver.js -- Room Server updating script, which saves Spotlight the work of having to manually pull commits.
  wiinoma.js -- Wii No Ma compose repo updating script, which saves Spotlight the work of having to manually pull commits.
  pbrupdater.js -- PBR Engine 2.0 updating script, which saves my buddies over at TPP the work of having to manually pull commits.
  tppcore.js -- TPP Core updating script, which saves my buddies over at TPP the work of having to manually pull commits.
  wiierd.js -- Wiierd error code system updating script, which saves Spotlight and WiiLink24 the work of having to manually pull commits.

  What does this do?

  This module, along with it's customizations and heavy modifications, provides the functionality of Git cloning a repo into a folder and scheduling a cron job to pull updates from the remote origin.

  Great! How do I run it?

  filemaker.js Runtime Docs

  To run filemaker updater, as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/share/engine/
  node filemaker.js
  cd ../../../

  vulcan.js Runtime Docs

  To run vulcan updater, as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/schemas/vulcan/
  node vulcan.js
  cd ../../../

  roomserver.js Runtime Docs

  To run roomserver updater, as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/share/roomserver/
  node roomserver.js
  cd ../../../

  wiierd.js Runtime Docs

  To run wiierd updater, as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/share/wiierd/
  node wiierd.js
  cd ../../../

  wiinoma.js Runtime Docs

  To run Wii No Ma production code updater, as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/share/wiinoma/
  node wiinoma.js
  cd ../../../

  pbrupdater.js Runtime Docs

  To run PBREngine 2.0 Updater, as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/other/tpp/0/data
  node pbrupdater.js
  cd ../../../

  tppcore.js Runtime Docs

  To run TPP Core Updater as a individual module, do:

  cd /var/share/gitbot/
  mkdir /var/other/tpp/1/data
  node tppcore.js
  cd ../../../

  Enviroment Runtime Setup Docs

  To setup the enviroment, do:

  mkdir /var/
  cd var
  mkdir share/
  mkdir schemas/
  mkdir other/
  mkdir other/tpp
  mkdir other/tpp/0
  mkdir other/tpp/1
  cd share
  mkdir gitbot
  git clone --recursive https://github.com/WiiLink24-Extensions/git-pull-cron gitbot/
  cd gitbot

  But... but I don't wanna set the whole thing up. I wanna setup a specific category.

  Ok, click here to view the documentation on that.

  How to install the unmodified version, hiddentao's version that is.

  bash
  clear&&npm install git-pull-cron

  Usage of Unmodified Version

  
  var gitPullCron = require('git-pull-cron');
  /*

• Clone given repo into /dev/my-repo, replacing what's already there
• Schedule cron to run every weekday (Mon-Fri) at 11:30am
• When cron task runs, a git pull origin master will be performed

• Once cron task has run the callback will get invoked with latest commit info / gitPullCron.init('git://my-domain.com/my-repo.git', '/dev/my-repo', '00 30 11 * 1-5', function(err, commit) { if (err) { return console.error(err.stack); }

  console.log('Updated to commit: ' + commit.id); });

  ## Usage of Modified Version
  ```javascript
  const gitPullCron = require('git-pull-cron-mod');
  /* Original example code by hiddentao */
  /* Example was modified by 6100m */
  /* Schedules cron to run every weekday (Mon-Fri) at 11:30am */
  gitPullCron.init('git://my-domain.com/my-repo.git','/dev/my-repo','00 30 11 * * 1-5', function(err,commit) {
  if (err) {
  return console.error(err.stack);
  }
  console.log('Updated to commit: '+commit.id);
  });

  Indvidual Category Setup Guides

  I want to setup the TwitchPlaysPokemon category and that category only.

  I get the feeling! Please click here to view the documentation on how to setup the TwitchPlaysPokemon category you want and that category only.

  I want to setup the WiiLink24 category and that category only.

  I get the feeling! Please click here to view the documentation on how to setup the WiiLink24 category you want and that category only.

  I want to setup the WiiConnect24 category and that category only.

  I get the feeling! Please click here to view the documentation on how to setup the WiiConnect24 category you want and that category only.

  API
  

  .init(gitRepoUrl, localFolderPath, cronSpec, updateCallback)

  Clones remote Git repository to given local folder path and schedule a cron job
  to `git pull` updates.

  Params:

  • gitRepoUrl - URL to remote git repo, should be actionable by git command-line executable.
  • localFolderPath - Where the repository should be cloned to in the filesystem. Will get clobbered prior to cloning.
  • cronSpec - The cron schedule spec, see cron
  • updateCallback - OPTIONAL. A callback (err, commit) which gets invoked for every update performed. The commit parameter is an instance of Commit from gift.

Returns: A Promise which resolves to the CronJob instance.

.jobs

The current list of CronJob instances that have been setup through init()

This is useful in case you wish to modify or stop cron jobs.

LICENSE

MIT - see LICENSE.md

I want to setup TwitchPlaysPokemon stuff only.

Then do...

mkdir /var/
cd var
mkdir other/
mkdir other/tpp
mkdir other/tpp/0
mkdir other/tpp/1
mkdir other/tpp/0/data
mkdir other/tpp/1/data
cd share
mkdir gitbot
git clone --recursive https://github.com/WiiLink24-Extensions/git-pull-cron gitbot/
cd gitbot

Then, to run the PBREngine 2.0 Updater, do:

cd /var/share/gitbot/
node pbrupdater.js
cd ../../../

Then, to run the TPPCore updater, do:

cd /var/share/gitbot/
node tppcore.js
cd ../../../

Please click here to view remaining instructions.

I want to setup WiiLink24 stuff only.

Then do...

mkdir /var/
cd var
mkdir schemas
mkdir share
mkdir schemas/vulcan/
mkdir share/wiinoma/
mkdir share/roomserver/
mkdir share/wiierd/
mkdir share/engine/
cd share
mkdir gitbot
git clone --recursive https://github.com/WiiLink24-Extensions/git-pull-cron gitbot/
cd gitbot

Then, to run the Vulcan Updater, do:

cd /var/share/gitbot/
node vulcan.js
cd ../../../

Then, to run the Wiierd updater, do:

cd /var/share/gitbot/
node wiierd.js
cd ../../../

Then, to run the Wii No Ma production code updater, do:

cd /var/share/gitbot/
node wiinoma.js
cd ../../../

Then, to run the Room Server updater, do:

cd /var/share/gitbot/
node roomserver.js
cd ../../../

Then, to run the File Maker Updater, do:

cd /var/share/gitbot/
node filemaker.js
cd ../../../

Please click here to view remaining instructions.

I wanna setup WiiConnect24 stuff only.

Then do...

mkdir /var/
cd var
mkdir schemas
mkdir share
mkdir schemas/vulcan/
mkdir share/engine/
cd share
mkdir gitbot
git clone --recursive https://github.com/WiiLink24-Extensions/git-pull-cron gitbot/
cd gitbot

Then, to run the File Maker Updater, do:

cd /var/share/gitbot/
node filemaker.js
cd ../../../

Then, to run the Vulcan Updater, do:

cd /var/share/gitbot/
node vulcan.js
cd ../../../

Then, it's up to you what to do next.

[ghost]

I have made some stability improvements Spotlight, I plan to shave off 0.2KB and then besides the markdown line issue, I will be ready 😄

[larsenv]

Shave off 0.2KB? What an improvement /s

[ghost]

Well Larsen, the original was around 16-20KB I think, and it is now 12.2KB, I just don't really have too many areas left to improve in :) I shaved off 1.2KB today I think, and yeah I am now at 12.2KB

[ghost]

The end goal is to be at 11KB.

[ghost]

@larsenv Would the file-maker script be of any use to ya? I mean, it might help you not have to do commits manually.

[larsenv]

no

[Peter0x44]

what is the point of writing like this

[spotlightishere]

Hey, thank you for letting us know.

However, resources-wise, it'd be far lighter to pull via cron directly - the simple command of crontab -e to edit, its quite simple format, and https://crontab.guru can't get you wrong either going from there.

Additionally, I'm not sure it'd be in our best interest to pull the master version of software. Often this involves things such as database migrations that would have to be manually run. While this could be automated, I'd rather not risk production data somehow getting dropped due to changes that weren't fine-tuned upon commit. I think what we may end up doing is publishing tagged releases to ghcr and manually pulling from there, as eventually the structure of this repository will change to reflect changes made via the web panel and et cetera. Realistically the image builds fast enough that it wouldn't be remotely a pain to update whenever the team feels ready.

[ghost]

@spotlightishere I agree with that, maybe we can do internal software as well using Gogs, which then in turn we can do the same for the static repo? EDIT: We also might want to do deploy keys on our Gogs server in the event we ever do.

[spotlightishere]

I'm not sure I follow - why host our own git things?

(Also, Gogs is practically dead nowadays :( Definitely want to use Gitea!)

[ghost]

Oh, just for the private stuff, so we can update the private code, without needing a private Github repo :) As for gitea, yeah, I have been favoring it a bit too.

[spotlightishere]

Ah, I see. The end goal is to have everything public, as the only private assets currently existing are our own designs which haven't been automated via a panel/recorded by our DB to insert and render accordingly.

[ghost]

Alright :) Hey speaking of which Spotlight, had an idea for the glitch session. I am going to be deserializing the hardcoded data, and output it to a pickle .dat file. This hardcoded data mainly consists of the template HTML data and template subject, which my sendgrid script will be using. One of the things I am very curious about though Spotlight, is when we merge my WC24 stuff to Cacti, is it possible to have two mail servers on the same server? It's kinda been a thing I am pondering lately.

[spotlightishere]

I'm not sure why we would need two mail servers - feel free to email or message me individually to discuss as I don't want to pollute the notifications of those following this repo.