Beiträge von ñull

    In fact I tried it out before writing. To reproduce:


    • Created a new customer and in it I created a new subscription with a hosting plan that has ssh enabled called testaccount
    • As root I created the /var/www/testaccoun/.ssh/authorized_keys with my public key. Note the missing "t". The entered subscription ID was truncated without warning. The entry field should not allow more characters to prevent this and avoid confusion.
    • I logged in successfully with ssh testaccoun@mydomain.com
    • By default you end up in the home directory /var/www/testaccoun. I executed:

      Code
      $ chmod u+w .
      $ ls -al
      total 28
      drwxr-x--- 7 testaccoun www-data   4096 2012-09-27 15:03 .
      drwxr-xr-x 7 root       root       4096 2012-09-27 15:01 ..
      drwxr-xr-x 2 testaccoun testaccoun 4096 2012-09-27 15:01 htdocs
      drwxr-x--- 2 www-data   testaccoun 4096 2012-09-27 15:01 logs
      drwxr-x--- 2 testaccoun testaccoun 4096 2012-09-27 15:01 priv
      drwx------ 2 testaccoun testaccoun 4096 2012-09-27 15:04 .ssh
      drwxr-x--- 2 testaccoun testaccoun 4096 2012-09-27 15:01 tmp



    As you can see the single dot (the home) has now rw permission.

    Ich würde sagen das Mailman mehr universell einsetzbar ist. Auf der phplist Webseite lese ich:

    Zitat


    phplist is a one-way email announcement delivery system. It is great for newsletters, publicity lists, notifications, and many other uses. (It is different from group mailing list systems like mailman.)


    Ich glaube das man phplist auch gut unabhängig von LiveConfig benützen kann, vielleicht als installierbare Anwendung. Deshalb würde ich Mailman oder etwas äquivalentes bevorzugen. Vielleicht wäre Sympa eine gute Alternative?

    After your explanation about suPHP, I understand that a symlink is not a solution, but you could allow home folder read-write.


    There is no further need to protect the conf, logs and stats folder, because they are not owned by the user and have only group read access. Furthermore the home folder is owned by the user so the user him/herself can change the permission to read-write. I see therefore no reason why LiveConfig won't set the initial home folder permission to read-write for convenience sake.

    The subscription Id is the same as Unix user ID if I'm not mistaken. Since is it is not possible to change the SSH setting of a subscription, you have to delete it and recreate another that has it set differently. After removing a subscription, it refuses to create a new one with the same ID, saying it is already in use. If it is deleted it should be reusable.

    I removed all subscriptions (after removing all email, web domains). Now I try to delete the customer, but it won't let me saying I should first remove all contacts. Where do you remove contacts from a customer? When I click Edit customer you can only choose another "Owner-C" contact, not delete it.

    When I log in as user with

    Code
    su - username

    and try what I often do, namely start mc (midnight commander) then I get permission errors that the user (the application started by the user) is not allowed to create its configuration folder. I then I discovered that the user has no write permission there.


    When this was consciously chosen for a important reason, then my suggestion is to have the home directory where is usually is at /home/username and there you can allow the user to write, without interfering with that important reason. With a symlink you could then bring /var/www/username in the home folder for convenience.

    As administrator you can override many options in the client's subscription. One thing I miss is the SSH access. I would not give bash access to the normal user. As web designer I would like to run drush (Drupal's command line management tool) logged in as the user. When I want to do this type of maintenance I would like to temporary change SSH access to permit bash, login as the user, do my work, logout and reset to the subscription's value. That way all work is done with the right file ownership. Could this SSH override be added?

    Unfortunately with version 1.5 I get this response:

    Zitat

    /usr/sbin/liveconfig: No new password defined (use LCINITPW/LCINITSOAP environment variables; see manual for more informations)


    Somehow the environment variable is not seen. I checked if it was set with:


    Zitat

    # set |grep LCINITPW
    LCINITPW='MyPaSsWoRd'
    #

    Wir haben uns inzwischen Gedanken dazu gemacht. Für Version 1.5.2* ist geplant, "zentrale Anwendungen" wie eben phpMyAdmin, Roundcube usw. über die LiveConfig-Oberfläche konfigurieren zu können. Somit können auch wieder die (gemanagten) Pakete der Distribution genutzt werden, alternativ wird es einen Mechanismus geben um selber (ggf. aktuellere) Anwendungen bereitzustellen.


    Offenbar nicht typisch ein LiveConfig Problem. Diese Lösung oder ähnliche scheinen mir besser weil diese "zentrale Anwendungen" anscheinend sowieso eher mod_php abhängig sind und in /usr/share installiert sind. Alle andere gefunden Lösungen sind umständlicher.