解析关于图像的迁移到heroku / aws [英] Parse migration to heroku/aws regarding the image
问题描述
我已成功将我的解析数据库迁移到aws，但图像文件的网址仍然像
要直接回答您的问题，我们正在积极寻找解决方案和
这里是迁移后最新的迁移和可选的解析文件存储选项。
如何将我的旧Parse文件迁移到Parse Sever ？
将传统的Parse文件从Parse拥有的S3存储桶迁移到开发人员拥有的Parse Sever： https://github.com/ParsePlatform/parse-server/issues/8
我有哪些非数据库选项可用于存储我的Parse迁移到解析服务器后的文件？
添加支持，通过运行解析服务器的S3适配器将解析文件直接上传到Amazon Simple Storage（S3）：https://github.com/Pa rsePlatform / parse-server / pull / 113
解析文件的迁移注意事项：
当用户首次上传时一个文件，Parse服务将其上传到files.parsetfss.com并通过直接链接回复该文件。此时，在Parse Core或其他数据类中没有引用此文件对象的POINTER或METADATA。开发人员需要在他们自己的数据类中保留对此文件的引用，或者进行另一个API调用以创建对象或更新现有对象并将Parse File与该对象相关联。 否则，该文件是孤立的。 Parse允许您在应用程序的应用程序设置中清理文件。此选项将删除任何对象未引用的任何文件。孤立文件只能使用万能钥匙删除，目前无法搜索所有上传的解析文件，除非它与一个类对象相关联。
在迁移到解析服务器期间，现有解析文件会发生什么？
在迁移期间，文件保留在Parse的S3存储桶中，但新迁移的解析服务器知道如何继续提供它们移民后。没有文件被移除！只有当这些文件与对象关联时，才有指向Parse所拥有的S3存储桶的指针。因此，如果开发人员在2017年的Parse关闭之前没有从Parse迁移遗留预迁移Parse文件，他们可能会失去对这些文件的访问权限。
Parse和开源Parse Server社区正在积极致力于提供迁移解决方案。请参见此处。
什么迁移到Parse Server后上传的NEW Parse Files会发生什么？
上传到解析服务器的新Parse文件在 MongoDB GridStore（Mongo）。只有通过api.parse.com API端点上传的文件才由Parse托管。换句话说，如果您将应用程序迁移到Parse Server但尚未更新客户端以使用新的Parse Server API端点，则这些Parse Files仍将上载到Parse拥有的S3存储桶。对于那些使用新的Parse Server API端点上传Parse文件的客户端，这些文件将直接存储到开发人员MongoDB数据库中。
我希望您发现此信息有用。
I have successfully migrated my parse db to aws but the urls of image files still like http://files.parsetfss.com/77447afb-f681-4b55-afad-6bceeb2e155a/tfss-79297c86-bd48-4d7f-87ab-c43e02d1a8f3-photo.png
it means files are still on parse s3 cloud or something their own storage so what will happen to those files after parse shutdown. what is the way to migrate the images to new database/storage on my own AWS. I am worried because I have apprx 14.5 k images on parse.
Please provide you valuable guidance on this.
As you know, Parse Files is a feature allowing developers to upload files (up to 10 megabytes each) and reference those files from objects in Parse Core data classes or directly by URL provided in the API response from Parse.
Behind-the-scenes, Parse is uploading your files to a Parse-owned S3 bucket (files.parsetfss.com) and prefixing the file objects with your application "File key".
To answer your questions directly, there's active solutions in-the-works and here’s the latest addressing the migration and optional Parse File storage options post migration.
How do I migrated my legacy Parse Files over to Parse Sever? Migrating legacy Parse Files from Parse-owned S3 bucket to developer-owned Parse Sever: https://github.com/ParsePlatform/parse-server/issues/8
What NON database options do I have for storing my Parse Files after migrating to Parse Server? Add support to upload Parse Files directly to Amazon Simple Storage (S3) via S3 adapter running Parse Server: https://github.com/ParsePlatform/parse-server/pull/113
Migration Considerations for Parse Files: When a user first uploads a file, Parse service uploads it to files.parsetfss.com and responds with a link directly to the file. At this point, there is NO POINTER or METADATA referencing this file object in Parse Core or other data classes. The developer would need to keep a reference to this file in their own data class OR make another API call to create an object or update an existing object and associate the Parse File with that object. Otherwise, the file is orphaned. Parse does allow you to "Clean Up Files" in the App Settings of your application. This option will delete any files that are not referenced by any objects. Orphaned files can only be deleted by using the Master Key and there is currently no way to search ALL your uploaded Parse Files per account or application unless it’s associated with a class object.
What happens to EXISTING Parse Files during the migration to Parse Server? During the migration, the files stay on Parse's S3 bucket, but the newly migrated Parse Server knows how to continue serving them up post migration. NO FILES HAVE BEEN MIGRATED! Only the pointers to the S3 bucket owned by Parse AND only if those files are associated with an object. So, if the developer DOES NOT MIGRATE the "legacy" pre-migration Parse Files from Parse prior to Parse shutdown in 2017, they could lose access to these files. Parse and the open source Parse Server community is ACTIVELY working on providing migration solutions. See here.
What happens to NEW Parse Files uploaded after the migration to Parse Server? New Parse Files uploaded to a Parse Server after migration are hosted in MongoDB GridStore(Mongo). Only files uploaded through api.parse.com API endpoint are hosted by Parse. In other words, if you migrated your app to Parse Server but have not updated the clients to use the new Parse Server API endpoint, those Parse Files will still get uploaded to the Parse owned S3 bucket. For those clients that upload Parse Files using their new Parse Server API endpoint, the files will be stored directly into the developers MongoDB database.
I hope you found this information useful.
这篇关于解析关于图像的迁移到heroku / aws的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
