Custom platforms [#2135665]

Looking at directory structure for Octopus user o1we see

backups -> /data/disk/o1/backups
clients -> /data/disk/o1/clients
platforms
static -> /data/disk/o1/static

In How to add custom platform properly? it is stated (and also by Hosting->Platform pathauto) that platforms should reside in ~/static.

Also, the import procedure advises the same directory, ~/static, to start with. That all (copying other site there, some temp files, make files, etc) produces a mess in my opinion.

On the other hand, there is platforms directory that seems vacant -> can that one be used to host my custom platforms?

I assume that clients directory is used for Add client under o1 user? (just to clarify)

UPDATE: me st00pid, sorry. I didn't think enough, obviously, as I saw that platforms reside in unix user space while static is under aegir (/data/disk/o1), but also looking at aegir user, there is also /data/disk/o1/platforms so:

Why is it not symlinked as others are?
Why not use this for custom platforms for user o1?
What is it purpose otherwise?

Comments

Comment #1

MacMladen CreditAttribution: MacMladen commented 14 November 2013 at 11:19

Issue summary:

View changes

Comment #2

omega8cc CreditAttribution: omega8cc commented 14 November 2013 at 11:36

Status:

Active

» Closed (works as designed)

The ~/static is an old default (not a mess) when there was no platforms directory in Aegir used yet, so we stick with this old default to not complicate things further. We plan to use platforms directory in the future for something else: as a location for custom platforms, but with core symlinked automatically as it is done for built-in platforms. When used, it will be also added to SSH/FTPS allowed access paths, obviously.

The clients subdirectory is used to manage automatically updated symlinks too all sites per client (owner) -- it is explained in the (long) welcome e-mail.

Comment #3

MacMladen CreditAttribution: MacMladen commented 14 November 2013 at 14:09

The plan for platforms is really obvious as I was doing it right now, that way by hand as I also saw that as a best way solution.

(I meant that ~/static will become mess with all transient files that are temporary in nature and platforms that should be persistent).

Also, connecting with #1437404: Running Non Drupal Sites Under Octopus, I think there should be some consistent way (and place) for users to add other types under BOA supervision so something like ~/static or ~/non-drupal should be somewhere in plans for next directory layout.

Comment #4

MacMladen CreditAttribution: MacMladen commented 14 November 2013 at 14:10

Somehow, my /data/disk/o1/clients/ have nothing inside and I was making symlinks by hand for some domains under development for easier access.

Comment #5

omega8cc CreditAttribution: omega8cc commented 14 November 2013 at 15:30

It is left for the instance owner/admin to manage sane subdirectory structure in the ~/static tree designed as a central tree for custom platforms. It will be mess only when you will do that mess there ;) There are no plans to change this simple structure with single, central location for all your custom platforms, besides adding ~/platforms at some point for planned new features.