Add PocketBase

[jorgoose]

https://github.com/benallfree/awesome-pocketbase

This list provides documentation, resources, guides etc. for the open-source Go-based backend PocketBase

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.

• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.

• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.

  Left suggestions / feedback on PRs: Add Spring Boot #2810 and Update readme.md - Add LLM WebUIs #2878.

• You have read and understood the instructions for creating a list.

• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift

• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.

  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs

• Your entry should be added at the bottom of the appropriate category.

• The title of your entry should be title-cased and the URL to your list should end in #readme.

  • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

• No blockchain-related lists.

• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• The default branch should be named main, not master.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to a maximum of half the width of the original image.
  • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. The casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Does not use hard-wrapping.
• Does not include a CI (e.g. GitHub Actions) badge.
  You can still use a CI for linting, but the badge has no value in the readme.
• Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Checked all the requirements. Opened a PR on the awesome-pocketbase repo to make changes that adhere to the guidelines and the linter detailed above, which was merged. Should be ready to merge here.

[sindresorhus]

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

[benallfree]

@sindresorhus Could you please direct us to a more detailed analysis of what was missing or not followed? Two of us have reviewed each of the points and can't spot anything, so there might be something we are misinterpreting. Thank you for any help you can provide.

[Mobin965500]

vless://[email protected]:443?type=grpc&serviceName=31520094&security=tls&fp=&alpn=http%2F1.1%2Ch2&sni=1469688760.behmusic.store#vip-ktdb2liy

[philipp2525]

yes hello.. I am neither. I am a professional and have a lot to do with computers. I was sent to this app by okx. I'm trying to open my reserves or so... I've only been doing it for a few days... ...I don't understand a word. Although I translate... and hardly anyone works as hard as you do..., only sndrrs... don't have to be offended. I should do it quickly. but I'm not that good with everything. well and Christmas is here too.. I've been logged in to apps for 3 days.. 🤗🤗

[philipp2525]

Ich meine habe nicht viel mit pc tap und co zu tun . Nur das übliche . Bei okx war es anders . Ich will es gerne lernen .

[philipp2525]

Und hier gibt es viel zu lesen . Das muss ich 2 -3 mal lesen .ich will von niemanden Zeit verschwenden.. hab überhaupt nicht geähnt was diese darstellt .. wollte keine zu nahe treten . Nur diese die Reserven . Weil ich Angst hatte die laufe. Ab. Oder so ..

[philipp2525]

but when I came here to the spp. I found it interesting.. and started reading. But I'm probably an inhuman. Because I'm playing with my daughter on Christmas too... well... I'll read on now

[KFCMULLBANK]

I cant log in on my microsoft.com Den tis 26 dec. 2023 19:27PHILIPP BÖGE ***@***.***> skrev:

…

but when I came here to the spp. I found it interesting.. and started reading. But I'm probably an inhuman. Because I'm playing with my daughter on Christmas too... well... I'll read on now — Reply to this email directly, view it on GitHub <#2895 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A42O56QZ3PZCLXOLAWXSZBDYLMJIPAVCNFSM6AAAAABAI2MEUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZG4YDKOBXGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[hannibalfishkop]

Nice

[benallfree]

@sindresorhus This issue is getting spammed, can we please merge & close? What else needs to be done?

[svilupp]

Hi @benallfree ,

I ran your list through the linter (npx awesome-lint https://github.com/benallfree/awesome-pocketbase) and I'm getting the following errors:

✖ 33:1 Marker style should be - remark-lint:unordered-list-marker-style

Would you mind reviewing the Svelte section? I believe it uses an asterisk instead of a dash as a marker.

[benallfree]

@jorgoose see above

[sindresorhus]

The description starts with an uppercase character and ends with a period.

[sindresorhus]

Descriptions should not be title-cased.

[sindresorhus]

Includes a succinct description of the project/theme at the top of the readme. (Example)

[sindresorhus]

Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[benallfree]

@jorgoose Please see benallfree/awesome-pocketbase#36 and pull from upstream. I believe we have addressed @sindresorhus 's comments, but since this PR is from your branch I was hoping you could do an upstream pull to refresh it.