Page MenuHomePhabricator

Import database from custom installation of phabricator into phacility's hosted service.
Closed, ResolvedPublic

Description

I have my own phabricator instance running in ec2. I want to use the hosted service now and was wondering if there was a way to get my data (diffs) with me.

Event Timeline

bagashe raised the priority of this task from to Needs Triage.
bagashe updated the task description. (Show Details)
bagashe added a project: Phacility Support.
bagashe added a subscriber: bagashe.

Not a problem, go ahead and make an account on Phacility and whenever you're ready:

  • Dump your database with bin/storage dump | gzip > phabricator_data.sql.gz.
  • Upload the file here by dragging and dropping it onto the page: https://admin.phacility.com/file/
  • Let contact@phacility.com know once it's ready, and we'll import it into your instance and you can make sure things look good.

If everything's good, we'll repeat the process again when you're ready to switch over.

Looks like my phabricator_data.sql.gz file is bigger than the post_max_size setting.

As received by the server, this request had a nonzero content length but no POST data.

Normally, this indicates that it exceeds the 'post_max_size' setting in the PHP configuration on the server. Increase the 'post_max_size' setting or reduce the size of the request.

Request size according to 'Content-Length' was '217346228', 'post_max_size' is set to '64M'.

Any way around it?

Are you dragging and dropping or using the upload button? The drag and drop should chunk the file.

Ah! Drag-n-drop worked like a charm.

Edit: Removed non-essential stuff since this is public.

This comment was removed by bagashe.

I'll email contact@phacility.com with this info. Thanks again! :)

Cool, I'll get this importing. Do you want to shoot us an email at support@phacility.com to coordinate the rest of the import? There might be some private questions later on in the process about data specifics in case we run into any issues.

Ah, perfect. Yeah, either contact@ or support@ will work fine. Thanks!

epriestley claimed this task.

Looks like this is in good shape now.