Sharing a cache / egg to build multiple UNIX users

There are several independent Plone installations on the server running under different UNIX accounts.

Is there any reliable tool for sharing the buildout-cache folder on this server for all of these different UNIX users? Since one Plone sample / installation is 250 - 500 MB, this will be a small win.

  • All UNIX users accessing the shared folder will still be able to run buildout, adding to new eggs

  • New eggs will be available on disk to other users, without having to drag them, copy them

  • Users are trusted; there is no fear that they will go to the balls / and corrupt other users.

Currently, the problem is that eggs / pulled out by creating one of the UNIX users become write-disabled by the other.

My guess is that after each run of the build there may be some custom sudo script fixing rights to the eggs.

Any other suggested egg sharing method?

+4
source share
3 answers

You can share all the eggs by putting them in the same directory, as you said, and then you can solve the resolution problem by adding this to your assemblies:

[buildout] parts += chmod [chmod] recipe = plone.recipe.command command = chmod -R ugo+rw ${buildout:eggs-directory} 
+5
source

We use collective.hostout for all esp production deployments, where each installation belongs to a different user. Hostout creates a common group for the global egg cache. This ensures that any egg is read by the group after starting the assembly.

+2
source

It occurs to me that another solution (not as good as the recipe for chmod, imo, but maybe someone will see some value) consists only in sharing the download cache - now other users don’t need to " drag "" but save your folder with eggs. Files in the download cache are not writable by other users, but who will write them? [but then I'm not sure why we make sure that the eggs are writable - who writes in egg catalogs?]

+1
source

Source: https://habr.com/ru/post/1402594/


All Articles