Tools.nasqueron.org: Difference between revisions
From Nasqueron Agora
Line 1: | Line 1: | ||
== Installation instructions == | == Installation and update instructions == | ||
=== PHP === | === PHP === | ||
* PHP 5.4+ | * PHP 5.4+ | ||
** | ** Short array syntax: <code>$properties = [];</code> | ||
** Class member access on instantiation: <code>(new ThimblController())->run();</code> | |||
* The XSL extension (which depends of the libxslt library ({{port|textproc/libxslt}}) | |||
* Composer | |||
=== Scenario 1 - Redeploy from scratch === | |||
'''Note:''' this is currently a bad idea, as some site content isn't currently in the repository, like gadgets/rain. | |||
su nasqueron.org | |||
mkdir /var/wwwroot/nasqueron.org/tools | |||
git clone git@github.com:nasqueron/tools.nasqueron.org.git | |||
make | |||
=== Scenario 2 - Deploy from tools51.nasqueron.org === | |||
Dereckson uses this to push from his staging copy and then automate scenario 3: | |||
su | |||
cd /home/dereckson/dev/nasqueron/tools/repo | |||
../bin/deploy | |||
See [http://devcentral.nasqueron.org/P13 deploy script]. | |||
=== Scenario 3 - Deploy from GitHub === | |||
'''This is the recommended scenario.''' | |||
su nasqueron.org | |||
cd /var/wwwroot/nasqueron.org/tools | |||
git pull | |||
make clean all | |||
=== Scenario 4 - Only update external packages === | |||
Use this when a tool packaged and fetched by composer like the source templates generator has a new revision. | |||
su nasqueron.org | |||
cd /var/wwwroot/nasqueron.org/tools | |||
make clean all | |||
=== If you need to fix ownership permissions === | |||
chown -R nasqueron:org:web /var/wwwroot/nasqueron.org/tools | |||
# Enquire about the permissions for Gerrit feeds file | |||
[[Category:Nasqueron web sites]] | [[Category:Nasqueron web sites]] |
Revision as of 13:11, 24 November 2014
Installation and update instructions
PHP
- PHP 5.4+
- Short array syntax:
$properties = [];
- Class member access on instantiation:
(new ThimblController())->run();
- Short array syntax:
- The XSL extension (which depends of the libxslt library ( textproc/libxslt)
- Composer
Scenario 1 - Redeploy from scratch
Note: this is currently a bad idea, as some site content isn't currently in the repository, like gadgets/rain.
su nasqueron.org mkdir /var/wwwroot/nasqueron.org/tools git clone git@github.com:nasqueron/tools.nasqueron.org.git make
Scenario 2 - Deploy from tools51.nasqueron.org
Dereckson uses this to push from his staging copy and then automate scenario 3:
su cd /home/dereckson/dev/nasqueron/tools/repo ../bin/deploy
See deploy script.
Scenario 3 - Deploy from GitHub
This is the recommended scenario.
su nasqueron.org cd /var/wwwroot/nasqueron.org/tools git pull make clean all
Scenario 4 - Only update external packages
Use this when a tool packaged and fetched by composer like the source templates generator has a new revision.
su nasqueron.org cd /var/wwwroot/nasqueron.org/tools make clean all
If you need to fix ownership permissions
chown -R nasqueron:org:web /var/wwwroot/nasqueron.org/tools # Enquire about the permissions for Gerrit feeds file