[Doc] AppFlowy Personal Cloud Private Beta

[annieappflowy]

Description

Define your goals

• Thoroughly test the personal cloud functionality to guarantee smooth local data backup and seamless cross-device access, addressing any potential data loss issues.
• Extend user outreach to gather comprehensive product feedback from a broader user base.
• Enhance AppFlowy's visibility to increase awareness among a wider audience.

Define the target outcomes

• Validate the stability of the personal cloud for a seamless public beta experience.
• Aim to receive valuable feedback from at least 20% of 5,000 users during this period (1st round).
• Targeting a public beta launch in two months (tentative).

Identify your participants

• Existing AppFlowy users who are eager to use the Cloud functionality.
• New users who are willing to adopt AppFlowy with an understanding of potential product instability during the beta phase.
• Contributors, influencers, and writers who are interested in testing AppFlowy and providing their valuable feedback.

Distribute testing information starting on August 15th

• Send a signup form to target users (Discord --> Twitter --> Email List --> Website --> Other platforms)
• Screen qualified beta testers
• Email a download link / access code with instructions

This may include product access materials like installation packages, download links, user guides, issue logging instructions, and anything else needed to facilitate the test.

Run the beta test

Gather and analyze feedback

Make final product updates

To-Dos

• [x] signup form
• [x] documentation
• [x] forum set up
• [x] beta tester award program
• [x] Windows package ready
• [x] Linux package ready
• [x] invite email
• [ ] blog post
• [x] email subscribers
• [ ] a new video marketing asset
• [ ] risks and mitigations

Impact

Users who want to back up data to cloud and sync across devices

Additional Context

No response

[IMPranshu]

Hey @annieappflowy. I would like to test this and give my feedback. How to get started?

[annieappflowy]

You can sign up via filling out a form which will be shared next week.

[anhhtbk]

Can you provide an update on the progress?

[annieappflowy]

It's on the private beta mode @anhhtbk

[miztizm]

Waiting with impatience, it's the only thing that keeps me from moving to Appflowy.

[adriy-be]

Hello, any news ? How to join the beta ? I'm currently using Joplin with a self-hosted Joplin server, I'm really interesting to try and migrate to AppFlowy.

[annieappflowy]

Hi @miztizm @adriy-be , please sign up for the Cloud beta @adriy-be , have you tried self-hosting AppFlowy with Supabase?

[adriy-be]

Hi @miztizm @adriy-be , please sign up for the Cloud beta @adriy-be , have you tried self-hosting AppFlowy with Supabase?

Interesting ! I check that on my free time. It's seem more complex than just deploy a container like Joplin server but supabase seem very interesting. Thanks

[eitzenbe]

Hi Annie, I have cloud version 0.3.8 docker hosted on one of my servers, but it seems this is not providing features like sharing pages amongst users accessing the server from different machines. I#d be happy to do beta tesing with a few colleagues if such a version is lurking around ;)

[TheRealGramdalf]

Edit: I think I found it: https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/DEPLOYMENT.md

I'm also interested in self-hosting appflowy, but in my perusal of the supabase guide it wasn't quite clear how everything fits together. Is there some guide I'm missing that can get me kickstarted with docker-compose? Or is deploying supabase the only thing to do, and appflowy takes the rest from there (once you've run the database setup etc.)?

[annieappflowy]

@TheRealGramdalf , if you need help with self-hosting, please join our Discord server so we can offer quick support.

[xiaoxiaoimg]

At present, it is a bit troublesome to use docker-compose to deploy, so why not host it on docker? docker run xxx?

[Snuupy]

looks like reminders on cloud beta isn't working (it is working on local)

[speed2exe]

@xiaoxiaoimg Appflowy Cloud comprises of a few services running. You could run each of them individually. docker compose makes the process easier.

[speed2exe]

@Snuupy What do you mean reminders on cloud beta isn't working? As far as I know, reminder are a local feature.

[Snuupy]

@speed2exe

@Snuupy What do you mean reminders on cloud beta isn't working? As far as I know, reminder are a local feature.

Even if I set a reminder in a shared workspace, it won't show up in Upcoming Notifications. I expected it to work as it did locally, that I would receive a notification if something was due.

[therynamo]

EDIT: Fixed.

Sorry for posting this and not digging further.

Hosted wtih Proxmox locally.

OS: linux x86_64 Ubuntu 22.04.4 LTS

Running with docker compose.

It turns out, despite my attempts to follow directions, I still ended up in a bit of an erroneous state.

Here is the error from MinIO:

{"error":"code:Internal msg: Failed to create upload: ServiceError(ServiceError { source: Unhandled(Unhandled { source: ErrorMetadata { code: Some(\"NoSuchBucket\"), message: Some(\"The specified bucket does not exist\"), extras: Some({\"s3_extended_request_id\": \"<redacted>\", \"aws_request_id\": \"<redacted>\"}) }, meta: ErrorMetadata { code: Some(\"NoSuchBucket\"), message: Some(\"The specified bucket does not exist\"), extras: Some({\"s3_extended_request_id\": \"<redacted>\", \"aws_request_id\": \"<redacted>\"}) } }), raw: Response { status: StatusCode(404), headers: Headers { headers: {\"accept-ranges\": HeaderValue { _private: H0(\"bytes\") }, \"content-length\": HeaderValue { _private: H0(\"524\") }, \"content-type\": HeaderValue { _private: H0(\"application/xml\") }, \"server\": HeaderValue { _private: H0(\"MinIO\") }, \"strict-transport-security\": HeaderValue { _private: H0(\"max-age=31536000; includeSubDomains\") }, \"vary\": HeaderValue { _private: H0(\"Origin\") }, \"vary\": HeaderValue { _private: H0(\"Accept-Encoding\") }, \"x-amz-id-2\": HeaderValue { _private: H0(\"<redacted>\") }, \"x-amz-request-id\": HeaderValue { _private: H0(\"<redacted>\") }, \"x-content-type-options\": HeaderValue { _private: H0(\"nosniff\") }, \"x-xss-protection\": HeaderValue { _private: H0(\"1; mode=block\") }, \"date\": HeaderValue { _private: H0(\"<redacted>\") }} }, body: SdkBody { inner: Once(Some(b\"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?>\\n<Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist</Message><Key>[redacted path to image]</Key><BucketName>appflowy</BucketName><Resource>/appflowy/redacted/redacted/redacted.png</Resource><RequestId>redacted</RequestId><HostId>redacted</HostId></Error>\")), retryable: true }, extensions: Extensions { extensions_02x: Extensions, extensions_1x: Extensions } } })"},"target":"appflowy_cloud::api::file_storage","span":{"name":"create_upload"},"spans":[{"client_version":"0.6.6","device_id":"redacted,"method":"POST","path":"/api/file_storage/{workspace_id}/create_upload","payload_size":117,"request_id":"redacted","name":"request"},{"name":"create_upload"}]}

Here was the key to the puzzle:

<BucketName>appflowy</BucketName>

Turns out the bucket appflowy did not exist in MinIO.

Possible Reasons:

• Initially when I booted up the VM I'd had kvm selected as my architecture, and MinIO complained about not supporting x_86. I saw on one of the github issues around here that I needed to use -AES in order to get MinIO to boot up. I changed the architecture, and restarted the machine, everything was good to go. But I imagine maybe there was a startup state missed? Idk. Then when MinIO started up no bucket was created
• The appflowy bucket was missed in the docker compose startup 🤷 . I'm not sure.

Once I manually created the bucket named appflowy, images started syncing from mobile to desktop just fine, like they should!

WOOHOO! 🥳

---

Original Message:

Hey! Just wanted to say thank you so much for building this all in open source and offering a self hosted option. I'm very excited and hoping that AppFlowy can be our home Knowledge Base.

One thing with the self hosted cloud is this known issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4568

This is a really important feature for us in order to fully realize your platform.

I'm positive this is not a trivial issue, so I understand if it's still ongoing development. I'm hoping this is shored up sooner than later, but I know you all have your hands full. Any chance there is an update? (No pressure)

You've got a nice cross platform app here with an intuitive and easy to use UI. I'm very excited for what comes next for this project and team. Thanks again!