Search options (Page 1 of 5)

Hi,

Sure, no problem, go ahead :)

The most obvious impediment to running werc is that TuxFamily does not provide rc (yet?).
We could install it; however, finding web hosters that provide both classic CGI and rc may prove difficult; are you sure you want to go this way?
You could look for a similar tool relying on sh/bash (thus keeping only the dependency on CGI), or you could experiment with static sites generators.

Hi and welcome!

- Yes, you should request exult.info. You can test it by adding an entry to your /etc/hosts file, e.g. 212.85.158.4 exult.info to make your browser believe exult.info already points at TuxFamily.

- Technically, you can leverage your TuxFamily SSH access to update your files any way you want... but in practice, giving your TuxFamily SSH access to a third-party sounds quite dangerous. Fiddling with a separate user and Unix permissions is possible but remains error-prone. I see two main approaches: a TuxFamily cron job that regularly checks whether it should rebuild your site, or a custom web page with authentication to reproduce that upload-unzip-done mechanism you described.

- I confirm installing phpBB should work. Just beware of spam.

- once your web area is created, you can use it. The TLS certificate is created and installed automagically, BUT it happens at night, so your web area will be TLS-less for the first day of its life.

By the way, most questions about TuxFamily have their answers on our FAQ, e.g. https://faq.tuxfamily.org/WebArea/En#Ho … 2FHTTPS.3F -- feel free to have a look (and you can even improve it if you want).

Après inspection : tu pourrais gagner de l'espace en déportant tes uploads WordPress dans un espace de téléchargement (cf notre FAQ, on a une page sur le sujet).
Mais bon, en attendant, j'ai augmenté ton quota à 500... enjoy :)

Ah, j'oubliais : c'est mal. Très mal.
Voir le premier point de https://faq.tuxfamily.org/Security/En#Advice / https://faq.tuxfamily.org/Security/Fr#Conseils

Je pense qu'il va falloir mettre à jour la FAQ sur ce sujet.

Avant, composer utilisait $COMPOSER_HOME/cache ; apparemment, ça a changé et il utilise désormais ~/.cache, avec une vague tentative de respecter les variables d'environnement XDG :

composer $ grep '\.cache' src/Composer/Factory.php
$xdgCache = getenv('XDG_CACHE_HOME') ?: $userDir . '/.cache';

Du coup essaye ça :

export COMPOSER_HOME=/home/myprojectgroup/tools/composer
mkdir -p "${COMPOSER_HOME}"
export XDG_CACHE_HOME=/home/myprojectgroup/cache
mkdir -p "${XDG_CACHE_HOME}"
composer ...

Oh, et supprime le contenu de /home/.cache, bien entendu.

Eh bien, oui, il s'agit peut-être d'un souci induit par l'architecture TuxFamily : en effet, si je déporte le dossier de destination des paquets vers /tmp:

mkdir /tmp/dest
chgrp arcenterre1 /tmp/dest
chmod +s /tmp/dest
COMPOSER_VENDOR_DIR=/tmp/dest ~/arcenterre1/tools/composer/composer.phar install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Package operations: 26 installs, 0 updates, 0 removals
  - Installing bcosca/fatfree (3.7.1): Extracting archive
  - Installing doctrine/lexer (1.2.0): Extracting archive
  - Installing ezyang/htmlpurifier (v4.12.0): Extracting archive
  - Installing psr/container (1.0.0): Extracting archive
  - Installing symfony/service-contracts (v2.0.1): Extracting archive
  - Installing symfony/stopwatch (v5.0.2): Extracting archive
  - Installing symfony/process (v5.0.2): Extracting archive
  - Installing symfony/polyfill-php72 (v1.13.1): Extracting archive
  - Installing paragonie/random_compat (v9.99.99): Extracting archive
  - Installing symfony/polyfill-php70 (v1.13.1): Extracting archive
  - Installing symfony/options-resolver (v5.0.2): Extracting archive
  - Installing symfony/finder (v5.0.2): Extracting archive
  - Installing symfony/polyfill-ctype (v1.13.1): Extracting archive
  - Installing symfony/filesystem (v5.0.2): Extracting archive
  - Installing psr/event-dispatcher (1.0.0): Extracting archive
  - Installing symfony/event-dispatcher-contracts (v2.0.1): Extracting archive
  - Installing symfony/event-dispatcher (v5.0.2): Extracting archive
  - Installing symfony/polyfill-php73 (v1.13.1): Extracting archive
  - Installing symfony/polyfill-mbstring (v1.13.1): Extracting archive
  - Installing symfony/console (v5.0.2): Extracting archive
  - Installing php-cs-fixer/diff (v1.3.0): Extracting archive
  - Installing doctrine/annotations (v1.8.0): Extracting archive
  - Installing psr/log (1.1.2): Extracting archive
  - Installing composer/xdebug-handler (1.4.0): Extracting archive
  - Installing composer/semver (1.5.0): Extracting archive
  - Installing friendsofphp/php-cs-fixer (v2.16.1): Extracting archive
Generating autoload files
htdocs/pretty$ ls -al /tmp/dest/
total 356
drwsr-sr-x   12 arcenterre arcenterre1   4096 Jun 29 19:57 .
drwxrwxrwt 9396 root       root        311296 Jun 29 19:57 ..
-rw-r--r--    1 arcenterre arcenterre1    178 Jun 29 19:57 autoload.php
drwxr-sr-x    3 arcenterre arcenterre1   4096 Jun 29 19:57 bcosca
drwxr-sr-x    2 arcenterre arcenterre1   4096 Jun 29 19:57 bin
drwxr-sr-x    4 arcenterre arcenterre1   4096 Jun 29 19:57 composer
drwxr-sr-x    4 arcenterre arcenterre1   4096 Jun 29 19:57 doctrine
drwxr-sr-x    3 arcenterre arcenterre1   4096 Jun 29 19:57 ezyang
drwxr-sr-x    3 arcenterre arcenterre1   4096 Jun 29 19:57 friendsofphp
drwxr-sr-x    3 arcenterre arcenterre1   4096 Jun 29 19:57 paragonie
drwxr-sr-x    3 arcenterre arcenterre1   4096 Jun 29 19:57 php-cs-fixer
drwxr-sr-x    5 arcenterre arcenterre1   4096 Jun 29 19:57 psr
drwxr-sr-x   16 arcenterre arcenterre1   4096 Jun 29 19:57 symfony

À la lecture de https://getcomposer.org/doc/03-cli.md#c … untime-env , je soupçonne Composer de faire des choses un peu spéciales pour aller toujours plus vite, butant ainsi sur une subtilité indéfinie de vhffsfs, notre filesystem virtuel utilisé pour les manipulations en SSH. À creuser.
En attendant, il doit suffire de déplacer le contenu de /tmp/dest dans le dossier pretty/vendor (ce que j'ai fait).
Et de fait, https://arcenterre.tuxfamily.org/pretty/signIn reflète désormais mieux qu'une page vide.

Typically in the same directory as your phpBB/pubBB installation.

How do you list files? Most PHP software come with a .htaccess file, typically filled with various RewriteRules. However, filenames that start with a dot are considered hidden files and may not be displayed unless explicitly requested.

Absolutely. *.htaccess files are not specific to TuxFamily (they are specific to the Apache web server though); there is plenty of documentation on the Internet about them.

As I am writing this message, both https://forum.dslav.tuxfamily.org/ and https://dslav.tuxfamily.org/ are considered secure. The fix was to... wait for the morning. Explanation: TLS/X.509 certificates are not requested immediately, so there is a one-day delay during which your freshly spawned web area is not considered secure over HTTPS.

Je vois que j'arrive un peu tard. TuxFamily propose effectivement PHP 7, moyennant une petite manipulation supplémentaire (décrite dans notre FAQ). Par contre, ça n'explique pas que ton WordPress soit "tombé" du jour au lendemain. Aurait-il par hasard un mécanisme de mise à jour automatique de ses extensions ?

Hello,

C'est installé :)

Hello,

Tu veux dire le site fr.flightgear.org je suppose ?
Très vraisemblablement, tu essayes de supprimer un fichier dans un répertoire qui ne possède pas les bonnes permissions Unix (chmod g+w)... ça tombe bien, il n'y en a qu'un : htdocs/forums_sup/addon, et il contient justement un fichier index.html. J'ai pris la liberté de corriger les permissions, tu peux réessayer.