Beiträge von ñull

The licensing of LC likely needs an Internet connection but when I am on the road this is not always affordable (roaming, greedy airport management ) or often not even available (in an economy class plane). I would like to develop my migration script for LiveConfig independent of demo expiry or Internet, or in other words, a developer version. I want to be able to use my VirtualBox environment on my ultrabook with local IP addres and have a working LiveConfig for testing and working on my script. Is that possible? How?

At log-in and password reset, the user is nicely presented with the preferred language in his browser. This is really a great feature, but when I configure in my browser multiple preferred languages, for instance Spanish, Dutch and German in that order of priority, then log-in should appear in Dutch (because Spanish is not available yet), instead it default to English. English should only be chosen as default, when in order, none of the preferred languages match the available translations. This is just a minor issue, because many will understand English fine, but may be you could change the logic for those that don't and make us multilinguals even more happy.

Both in API and FrontEnd I miss the feature to delete Contacts. As a workaround, how would you do that properly from the command line with SQLite or with PHP?

How to start with a clean database?

I now see that apparently the description of HostingSubscriptionAdd has changed. I see that now -1 for both mailquota and webspace can be -1.

Can you please explain? Is overselling possible now? Limiting will only take place when the real used space is more then the contract total?

Can you please confirm that overselling is impossible. If so are you planning to change this or add a feature that would optionally allow it?

What you explain is that you cannot do mail quota "overselling", right? You can not reserve more space than is actually available. Well that is really sh*t then. Makes a migration script virtually impossible or very complex. Wonder how this affects other potential clients migrating from other panels that have loose limits and allow overselling.

I guess the same is valid for webspace quota, right? Same problem will arise there then, that all values need adjustment in some intelligent way.

The old cp had for each user a postmaster mailbox created automatically when a new domain was created. How is this handled in LC with Postfix?

When using API how to set the quota when you want let a mailbox use all available storage space, only limited by the contract quota? Or is that not possible? I attempt to write a migration script and the previous CP would allow the value unlimited. What internal validation is there in HostingMailboxAdd? Would it do strict accounting of the available mail space in the contract? If so, I would need to do the same accounting in my script.

In the API description of this command you can only set the "Webspace, server path" and "Webspace disabled" by either setting the parameter web or leaving it Null. How do you set by API any of the other options available?:

*Redirect with its three options select box and destination field
*Application

Specially the first can be important when you want to write migration script from other control panels.

A friend helps me setting up bind DNS zones. He offers me a secondary DNS, but when looking at the configuration in /etc/bind/named.conf.options he could not agree with what LC did there. Since full DNS support is still in development I will not pass on his comments yet.

For now I would like to deactivate LC controlling the DNS. Is there a way to bring LC back to the initial state that it does not control bind? This would be a good feature to add to LC anyhow, a button to deactivate the control of a service.

Will there be a LUA script to customise DNS configuration?

Für "mc" braucht man etwas mehr:

export HOME="${HOME}/priv" HISTFILE="${HOME}/priv/.bash_history" XDG_CONFIG_HOME="${HOME}/priv/.config" XDG_CACHE_HOME="${HOME}/priv/.cache"  XDG_DATA_HOME="${HOME}/priv

Viel zeit verloren das herauszubekommen. Die Reparaturarbeit wird daher immer größer weil wir abgewichen sind von den Linux Standardverfahren. Konfigurationsdateien sollten in /etc bewahrt werden und der User sollte in seine Home schreiben können.

Mehr Information über XDG Variablen findet man hier.

Diese Lösung ist auch nicht vollkommen. Ich habe gerade bemerkt dass noch immer "mc" seine datei im vorherige home abspeichern will:

Zitat

echo "${HOME} ${HISTFILE}"
/var/www/web1/priv /var/www/web1/priv/.bash_history
mc
Cannot create /var/www/web1/.local/share/mc directory

Zitat von vbinsider

Das müsste in Lua eigentlich möglich sein.

Wie steht es mit der Automatisierung von dieser Lösung? Wird es überhaupt in LUA gemacht und ist es veränderbar?

Was ist den jetzigen Status von DNS Verwaltung? Muss man immer noch manuell Zonen hinzufügen?

Danke! Ich werde damit weiter experimentieren.

Ich habe diese Installation Instruktionen ausprobiert. Funktioniert einigermaßen. Nur überschreibt LC alles wieder natürlich. Ich wird probieren die Postfix lua Datei an zu passen. Hat schon Jemand das probiert?

I just managed to get Awstats going. Unfortunately my clients will not understand the results because everything is in German. Is there an work around for this? Best would be when liveconfig sets this and when it would follow the user's language as set in preferences.

Please add to the documentation that after upgrade of database / mail / web server packages to make sure that LC was restarted afterwards.

I did a apt-get upgrade and LC, apache and mysql were upgraded in that order. LC did restart but it was before apache and mysql were upgraded. I did not realise this and database and web server became unavailable in LC. To be sure I did the manual restart with liveconfig -k and then it worked again.

Beside documentation, it would be interesting when LC could detect itself if there was an upgrade of software and just reload the necessary data.

Keine weitere Reaktionen? Frage bleibt wie man das alles automatisieren soll wenn Liveconfig keinen useradd benutzt?

Heute fand ich diese Instruktionen für Mailman unter Debian. Sollte wahrscheinlich auch unter meinen Ubuntu funktionieren und anscheinend nicht sehr Kompliziert.

Meine frage ist, wenn ich das so ausführen würde für einer meine Kunden, was passiert dann nachher, wenn Mailman oder eine andere Lösung in LC integriert wird? Wann ich meine Kunden zu LiveConfig umziehe, will ich sie nicht nachher belästigen mit noch mal eine Änderung. Ich meine, können wir wenigstens wissen welche Mailinglist Lösung Kepler IT unterstützen wird? Das schönste wäre wenn dazu etwas im Roadmap erscheint.