Activity Library/Admins/Large Files - Revision history

FGrose: Following the link to the bug shows a 'WONTFIX' status. Please provide better information if this page is to be edited.

2016-12-20T01:01:01Z

Following the link to the bug shows a 'WONTFIX' status. Please provide better information if this page is to be edited.

← Older revision		Revision as of 21:01, 19 December 2016
Line 1:		Line 1:
	~~{{Obsolete \| Bug 371208 is already fixed}}~~
	For files too large to be uploaded through the regular interface, the following process should be followed in Remora until [https://bugzilla.mozilla.org/show_bug.cgi?id=371208 bug 371208] is fixed:		For files too large to be uploaded through the regular interface, the following process should be followed in Remora until [https://bugzilla.mozilla.org/show_bug.cgi?id=371208 bug 371208] is fixed:

KachachanC at 04:52, 19 December 2016

2016-12-19T04:52:27Z

← Older revision		Revision as of 00:52, 19 December 2016
Line 1:		Line 1:
			{{Obsolete \| Bug 371208 is already fixed}}
	For files too large to be uploaded through the regular interface, the following process should be followed in Remora until [https://bugzilla.mozilla.org/show_bug.cgi?id=371208 bug 371208] is fixed:		For files too large to be uploaded through the regular interface, the following process should be followed in Remora until [https://bugzilla.mozilla.org/show_bug.cgi?id=371208 bug 371208] is fixed:

Dfarning: add initial content

2009-04-06T00:37:22Z

add initial content

New page

For files too large to be uploaded through the regular interface, the following process should be followed in Remora until [https://bugzilla.mozilla.org/show_bug.cgi?id=371208 bug 371208] is fixed:

# Add-on author submits stub file(s) with only an install.rdf. Author completes entire additem process with these stubs. Author may wish to include something about not pushing the file public in the Notes to Reviewer.
# Add-on author files mozilla.org :: Server Operations bug and cc's administration@add-ons.bugs. The bug should include links to the real files and a link to this process, as well as the add-on id.
# Server Ops goes to REPO_PATH (as defined in site/app/config/config.php) and goes to the directory of the add-on ID.
# Server Ops copies the remote files to this directory with the same file names as the existing files for that version.
# Add-on author e-mails amo-editors AT mozilla.org (preferred) or requests in #addons on IRC (please be patient) for the next step.
# An AMO admin goes to the Add-on Manager in the Admin Control Panel and goes to the add-on. The admin recalculates the hash and size for the file(s).
# If the admin wishes to push the new version public, he may do so from this panel, which will copy the files to PUBLIC_STAGING_PATH. If the admin wishes the version to undergo normal review, he can leave it like it is and the file will be copied when an editor pushes public. The author will probably want to remove the "do not review" part of the Notes to Reviewer if this option is selected.

Note: if sysadmin handling this will be oremj, a quicker alternative to this entire process may be threatening the cluster with physical violence, causing it to do all of the above steps itself. Just be careful of mrapp08, we don't want another "accident" which causes the colo to smell like server poop for days.