Ticket #12079 (confirmed Feature Request)
Clean Data.fs copies from plone.org
Reported by: | miohtama | Owned by: | nutjob |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Sysadmin and Development Infrastructure | Version: | 4.1 |
Keywords: | Cc: |
Description
Developers need to have access to existing plone.org for migration, script, new UI, etc. testing
Let's make a script which
- Creates a copy of Data.fs
- manage_delObjects() forbidden directories (foundation)
- Packs the database
- Makes the packed database available as a daily drop for SSH account owners of plone.org
We really need get this fixed or hiring volunteers to work with p.org is little difficult.
E.g. this seems to be pushing back tasks because working is hard http://dev.plone.org/plone/ticket/11771
Change History
comment:2 Changed 4 years ago by kleist
- Status changed from new to confirmed
- Component changed from Website to Sysadmin and Development Infrastructure
comment:5 Changed 4 years ago by martior
- Status changed from confirmed to assigned
- Owner changed from nutjob to martior
comment:7 Changed 3 years ago by nutjob
- Status changed from assigned to closed
- Resolution set to fixed
Implemented as of 6a8ee095075b662956b002d0595d91b33de7329b and deployed to plone01.sixfeetup.com. Runs as an /etc/periodic/weekly task. The scrubbed database ends up in /home/ploneorg/devdrop/var/{file,blob}storage.
I've also updated conf/get_data script and conf/database.cfg to grab from that location.
comment:8 Changed 3 years ago by davisagli
We probably need a different way for the files to be downloaded than get_data and database.cfg, since the main goal of this was to allow people who *don't* have shell access to obtain the db for working on things locally.
comment:9 Changed 3 years ago by miohtama
- Status changed from closed to reopened
- Resolution fixed deleted
Please do not close the ticket until there are public instructions available somewhere how the process should go.
I'd like to see the process of getting your own plone.org copy running from the scratch (buildout.cfg, starting all necessary servers, getting Data.fs copy) documented in Plone admin manual:
http://developer.plone.org/reference_manuals/external/ploneorg.admin/index.html
Here is some old information which also needs to be migrated:
comment:10 Changed 3 years ago by nutjob
@davisagli: I didn't know that was the main goal, although I agree it's an admirable goal.
Indeed, item 4 in the ticket reads: "Makes the packed database available as a daily drop for SSH account owners of plone.org"
I'd still like rsync to be the primary method for developers, whether they've got accounts or not, because many of the blobs won't change and that'll reduce the outgoing traffic from plone01.sixfeetup.com—assuming that we're allowed to open the rsync ports.
@miohtama, you have my most abject, miserable, unworthy, and woeful apologies.
Please also remove the Zope-level Manager user passwords and the LDAP connection details.