woro

Hi, do I miss something or is there no function in Froxlor for email users (not admins or "customers") to change their email passwords? This would be a nice extension to ship an extra simple webinterface to provide this feature to all email users?

Hi, ich verwende derzeit Froxlor und betreibe auch einen Open-Xchange Server. Dieser ben?tigt aber immer eine eigene User-Datenbank. Ich ?berlege gerade, wie man Froxlor am leichtesten an Open-Xchange koppeln k?nnte. Grundlegend m?sste wohl jedes Anlegen eines Kunden in Froxlor einen Mandanten in OX anlegen und jedes hinzuf?gen einer Mailbox dann entsprechend den Benutzer. Am ehesten w?rde man dazu das OX SOAP Interface verwenden. Nachdem ich bisher keinerlei Ahnung ?ber Froxlor Interna habe, sondern nur als Benutzer, frage ich mich, wie man das am besten angehen k?nnte und ob es da irgendwelche Hooks in Froxlor f?r solche Zwecke gibt?

Thanks. Does it just work automatically if the files are not existing?

Hi, I'm running a froxlor system at the moment on an old distribution and want to migrate everything to a newer supported one. Therefore I'm wondering what the best way is to move the existing froxlor setup to the new machine. It will have same hostname, ip address and everything in the end so for the database it would just be a simple mysqldump. Also for the services I need to reconfigure the stuff on the new target system but what I'm not sure about is the config files which are written by froxlor. Do I have to copy everything to the new system or can froxlor recreate everything on demand? If the former is there some checklist available where froxlor is writing stuff?

Hi, I'm running a froxlor system at the moment on an old distribution and want to migrate everything to a newer supported one. Therefore I'm wondering what the best way is to move the existing froxlor setup to the new machine. It will have same hostname, ip address and everything in the end so for the database it would just be a simple mysqldump. Also for the services I need to reconfigure the stuff on the new target system but what I'm not sure about is the config files which are written by froxlor. Do I have to copy everything to the new system or can froxlor recreate everything on demand? If the former is there some checklist available where froxlor is writing stuff?

I actually understand now that froxlor does not support disabling the php handler on a per-directory basis. I'm wondering if that is hard to implement but I'm still quite a beginner of its internals. There is already some stuff creating these "diroptions" config files for apache. Would this be the right place to hook into that one?

Hi, I just started trying to enable APS management to my froxlor installation. Actually I wanted to provide a forum software and know phpbb. But froxlor does not enable phpbb because of the following error: PHP - Sonstiges - Je Verzeichnis deaktivierte PHP Handler werden nicht unterst?tzt. Is there anything I can do/change in my setup to allow phpbb to be installable through the APS system? woro

I'm maintaining my own package in openSUSE's buildservice as I'm an active member and I told the other maintainer about my improved package. Up to now he didn't integrate my patches for unknown reasons. Please note that I'm not a beginner as I have worked for SUSE for several years myself and know the system pretty well. I don't care if the 10.x configuration will be removed or not but I just want to contribute my work back to you. It's your decision to integrate it or not. Wolfgang

I'm running Froxlor on a production openSUSE 11.1 system now and for that reworked/refined most of the configuration templates which should basically work for most of the 11.x series. How can I bring that work back into the Froxlor codebase so that I don't need to maintain my own modifications? Wolfgang

I was trying froxlor some time ago already but now trying to start using it in a production environment and came across the same issues. The first is not really a problem and makes it a bit easier to test it as long as DNS is not setup correctly for a new domain. I also don't see a big issue with it but I'm still interested if there are/were other reasons to provide that. The latter is the thing I actually wondered and why I came here to write a post about it before I found that one. There are alias domains and "normal" domains. I'd have expected that froxlor builds up a structure (probably below the customer path) with those domains but connects the alias domain to its main one. But apparently froxlor treats every domain the same (main issue for me is that apache configs are pointing to the same docroot which just is the customer). I guess it's possible to configure the domains "correctly" but by default everything points to the same data which looks wrong to me given there explicitely exists an option to have alias domains. At the moment every domain of a customer behaves like an alias domain. Or did I miss something? Wolfgang

I have no idea what was the issue yesterday. I tried it again now and the config was reloaded correctly. Issues solved. Thanks.

Yes, it's the correct init script. Is that called immediately after the bind config files have been modified/created? How can I enable debugging since if that's the case it didn't work for me.

My basic question was if bind is reloaded or restarted at all and how? On my system the chroot setup is done from the init script in case of restart or reload. What is not sufficient is to reload the config via -HUP or alike. The way how chroot works in that case is that there is /etc/named.conf - general configuration /etc/named.d/* - included config files like froxlor_bind.conf /var/lib/named - chroot /var/lib/named/master - normal place for zone files I configured froxlor to write /etc/named.d/froxlor_bind.conf and at the same time that means that it creates /etc/named.d/domains/* for its zone files. That's not a problem since the init script transfers the stuff below /etc/named.d into the chroot but as explained only if started or reloaded through the init script. I verified that DNS works correctly when I restart bind using the init script.

Hi, I'm completely new to Froxlor and these might be newbie questions. Feel free to point me to any available documentation I might have missed. I just started testing Froxlor (latest version) in my environment and the first service I was checking is DNS (using bind9 in my case) where I basically have two questions: - I was surprised that the standard subdomains for users is created directly below the FQDN I setup initially. This is not really a problem but was somehow unexpected. Then I wondered that there is no DNS zone maintained for that default domain. From a short hint on IRC I gather that it's not needed since the FQDN should already point to that host. While that might be true I haven't seen an installation document which explains the initial DNS setup (one has to wildcards, right?). - after I created the first domain for the testaccount the DNS zone was created apparently correctly but bind was not restarted. I noticed because my bind9 is running in chroot and the init script is taking care of setting the chroot up but the generated files were not copied. How can I check or debug what is happening? Thanks, Wolfgang

Hi, I'll probably try to use froxlor for a shared hosting server I want to provide (currently doing everything manually). This server will run openSUSE 11.1 in the first phase and later something newer 11.3 or 11.4. I know nothing about froxlor yet but I know quite something about openSUSE and configuring its services. I found that openSUSE support is not that up to date in froxlor and wanted to ask some questions. - the contributed documentation and package is meant as authoritative distribution of froxlor for openSUSE? In that case I have some feedback on packaging and documentation. Where is the best place to report and discuss that? - the 11.x config templates are not part of the official SVN tree for example. What are the plans of incorporating them? (openSUSE 10.0 is _quite_ old and probably should be removed). Wolfgang