Hmm, you have a point. I never worked with these features...

What is there to configure? Group ownership is done in the Web Site app; Read Only is irrelevent - you'd just remove File Upload access which will achieve the same. There is nothing else to configure. FTP access is covered by FTP Upload.

...but only the flexshare exists as directory and it is not accessible via the webconfig. So you can't configure it? Do I miss something?

Websites created through the Web Site app only show up in the Website App although the Flexshares should still exist in the background.

So you can upload to it by FTP or SMB.

Okay, clear. I have seen the bind mounts. What is the reason that the flexshare also exists if a website is create with the website app?

Testing again. Only websites created through the Flexshare system show in the Flexshare app. Websites created through the Web Site app only show up in the Website App although the Flexshares should still exist in the background. Have a look at:

findmnt -t nocgroup,notmpfs,nooverlay -o TARGET,SOURCE,FSTYPE | grep /var

app-storage-core-2.6.15-1.v7.noarch

I am not sure. My brain is currently preoccupied with the App-Attack-Detector upgrade problem. What is the output to:

rpm -qa | grep app-stor

I think we hit a bug?

Enabled "file server upload" on the website settings page in the webserver app. Under websites a map icon is now visible in the webserver app. No flexshare is visible for the website in the flexshare app.

Enable it for "File Server Upload" or possibly "FTP Upload" then have another look.

Marcel van van Leeuwen wrote:
Are you saying If I create a website this directory is created in "/var/www/virtual" and "/var/flexshare/shares"? Yes this works in my situation.

...but the flexshare is not created in the webconfig..

No. That does not seem to be right. If you create a Flexshare, test, and your domain is and enable it for a website, you get the standard flexshare in /var/flexshare/shares/test and you get a folder /var/www/virtual/test. These use your internal domain name and it is not configurable (I've just rememberer that piece of info!) so are only suitable for internal web sites or where you use the same domain internally and externally.

If you create a sandboxed website, test.example.com, you get a flexshare called /var/flexshare/shares/test.example.com and a folder /var/www/virtual/test.example.com. These can use any domain name you like. If you use a different domain internally you can still use the hosts file to access them.

The folders under /var/flexshare/shares and /var/www/virtual are not symlinked together but bind mounted together. Have a look at the output to "findmnt" in a big screen, or, to cut it down a bit "findmnt -t nocgroup,notmpfs,nooverlay -o TARGET,SOURCE,FSTYPE".

Oh, what I also noticed are this symlinks directories? Always thought that the begon with the letter "l"

Okay good information!

To make things clear:

Are you saying that if I create a flexshare website the directory is created in "/var/flexshare/share" and "/var/www/virtual/" This is not the case in my situation.

Are you saying If I create a website this directory is created in "/var/www/virtual" and "/var/flexshare/shares"? Yes this works in my situation.

Flexshare created sites also use /var/www/virtual, but force you to use the sandboxed layout. For some reason you get different configurable parameter in the webconfig (in the flexshare you also have Require SSL and you can override the port) and the mechanism for enabling FTP and File Server upload is different.

With the Flexshare website you can only create a subdomain of your domain or a site in the path of the flexshare. In the Webserver app you can create a site for any domain/subdomain. Be careful of mixing and matching. It looks like if I create a flexshare site called test2 I get a folder of /var/www/virtual/test2, but if I create a Website of test2.howitts.co.uk I get a folder /var/www/virtual/test2.howitts.co.uk and it is similar for the share names.

So the /var/www/virtual/<website> I made with the Webserver app is also visible as /var/flexshare/shares/<website> but when the flexshare is not created in the webconfig what is the purpose of this directory in /var/flex/shares/<website>?

So the other way around if I create a flexshare and enable web it is not create in /var/www/virtual so this is different from what you explained?

In a word, yes. Flexshares are symlinked to /var/www/html for the default site and /var/www/virtual for the rest to allow File Upload via Samba shares and FTP Upload to work. Flexshare websites are much older beasts and have slightly different parameters. I believe they are more suitable for internal websites.

And the directories are kept in sync because the folder in /var/www/ is bound into the flexshare