Introduction

Appwrite has been and always will be a tool for developers. To emphasize this, we want to create the best developer experience possible by providing enough guides and examples for new Appwriters.

Your task is to write a blog post Ruby in Appwrite. The main topic of your article should be explaining how to use Appwrites Ruby SDK to write Appwrite Functions. It can be

I like how Simplepush presents a couple of different ways to generate push messages on their website:

https://simplepush.io/#libraries

How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg

It would be nice to use shortcuts for common functions, like:

• s to trigger screen sharing (start/stop)
• someKey to switch between available streams
• f to trigger full screen
• c to copy the room url

When trying to edit the caption of a picture, the submit button doesnt do anything. The captions are not saved and no confirmation is shown. When the generate button is used, a caption is successfully generated and automatically saved. But this caption can not be edited nor removed.
Logs dont show any activity besides caption generation.
This happens on the newest docker-compose examples.

https://material.io/resources/color/#!/?view.left=1&view.right=0 readability needs to be possible almost universally ideally. This means avoiding all caps strings in titles as screen readers read every letter and other nonsense like this however the first and foremost concern is just simply that we ship with a default that is visible for our sighted users who may have issues with color blindness

Describe the bug
After scanning all the users and confirming that photos appear in the timeline and facial recognition is working I went to the People tab. Faces are recognized with minor errors, but I cannot rename any face from the default Unlabeled.

To Reproduce
Steps to reproduce the behavior:

1. Go to the People tab
2. Click on any Unlabeled item in order to change the

Describe the bug

The section on creating a service account in the Google Cloud console is out of date

As mentioned in discord I would recommend adding the following to your k3s deployment. I see multiple pages about the k3s deployment and each are missing the following which will make sure the nodes stay alive even if you over provision pods.

INSTALL_K3S_EXEC= ........ --kubelet-arg system-reserved=cpu=100m,memory=100Mi --kubelet-arg kube-reserved=cpu=200m,memory=400Mi

If we can't open port, then lets do something like:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Addr