User:Waldyrious/Toolforge

What is toolforge

 * About Toolforge
 * wikitech:Help:Cloud Services Introduction

Getting started

 * wikitech:Portal:Toolforge
 * wikitech:Help:Getting Started

How-to

 * wikitech:Help:Toolforge
 * wikitech:Help:Toolforge (and wikitech:Help:Toolforge/Web)
 * Website will be available at https://tools.wmflabs.org/TOOL/
 * wikitech:Help:Toolforge/Web
 * Website will be available at https://tools-static.wmflabs.org/TOOL/
 * Auto-update the static website whenever there's a push to its github repo
 * Website will be available at https://tools.wmflabs.org/TOOL/
 * wikitech:Help:Toolforge/Web
 * Website will be available at https://tools-static.wmflabs.org/TOOL/
 * Auto-update the static website whenever there's a push to its github repo
 * Website will be available at https://tools-static.wmflabs.org/TOOL/
 * Auto-update the static website whenever there's a push to its github repo
 * Website will be available at https://tools-static.wmflabs.org/TOOL/
 * Auto-update the static website whenever there's a push to its github repo




 * Go to https://github.com/USER/REPO/settings/hooks and click the "Add webhook" button
 * In the "Payload URL" field, type
 * Save the hook (the remaining fields can be kept with the default values)
 * You're done! Now whenever you push commits to the repo on github, the toolserver clone will be automatically updated :)
 * wikitech:Help:Toolforge/How to

Toolserver
Toolforge sort of replaces the old Toolserver.

The archived homepage for my account there can be found at toolserver:~waldir.

Archive of the contents:

index.php
Note: this is a condensed version, to highlight the PHP code. See the full contents here.

notes.txt
I should be able to add a post commit hook to perform a svn export (probably by logging in to ssh and doing the command there?) - See http://svnbook.red-bean.com/en/1.1/ch05s02.html#svn-ch-5-sect-2.1 for info on svn hook scripts. - See https://jira.toolserver.org/browse/TS-301 for a sample request to add a post-commit hook Otherwise, I need to manually login to ssh and run "svn export https://svn.toolserver.org/svnroot/waldir public_html --force"

Note that for it to work, you need to initially set public_html (or whatever directory you're planning to export to) to be writable by everyone, by doing: chmod a+w public_html
 * Update**: I managed to make it work with a simple update script: php calls svn export. See update.php's source code.

wiki-userpage.txt
{| ! Source code !! Rendered Waldir@meta.wikimedia
 * style="vertical-align:top; border-right:2em solid transparent"|
 * style="vertical-align:top; border-right:2em solid transparent"|


 * http://toolserver.org/~waldir/
 * svn: https://fisheye.toolserver.org/browse/waldir (repo: https://svn.toolserver.org/svnroot/waldir)
 * Getting started
 * Toolserver Intuition (for tool translation)
 * To learn: How to run bots from ts?

Random notes
To copy files from local to the toolserver: $ scp /path/to/local/file.ext waldir@login.toolserver.org:/path/to/remote/directory # remote path relative to home I copied .bashrc and .bash_aliases, but they didn't seem to have any effect. This solved the issue: $ source .barshrc (that also reloaded .bash_aliases) Waldir@meta.wikimedia
 * However, something broke: common commands (svn, nano) failed with stuff like "no svn in /sge62/bin/sol-amd64 /usr/bin ." O.o


 * http://toolserver.org/~waldir/
 * svn: https://fisheye.toolserver.org/browse/waldir (repo: https://svn.toolserver.org/svnroot/waldir)
 * Getting started
 * Toolserver Intuition (for tool translation)
 * To learn: How to run bots from ts?

Random notes
To copy files from local to the toolserver: $ scp /path/to/local/file.ext waldir@login.toolserver.org:/path/to/remote/directory # remote path relative to home I copied .bashrc and .bash_aliases, but they didn't seem to have any effect. This solved the issue: $ source .barshrc (that also reloaded .bash_aliases)
 * However, something broke: common commands (svn, nano) failed with stuff like "no svn in /sge62/bin/sol-amd64 /usr/bin ." O.o
 * }