utopia-php/http

Lite & fast micro PHP HTTP framework that is easy to learn.

http's Issues

📚 Documentation: Where do I get the Documentation

💭 Description

Where do I get the 📚 Documentation ?

I'm trying out this frameWork but can't seem to find it's documentation and features of the frameWork.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

🚀 Feature: Migrate from travis.yml to Github actions

🔖 Feature description

As the title suggests, we are currently migrating all of our workflows from Travis to GitHub Actions. Here's the below checklist that needs to be migrated to GitHub Actions.

Tasklist

• utopia-php/ab (#12)
• utopia-php/analytics (#45)
• utopia-php/cache (#13)
• utopia-php/cli (#29)
• utopia-php/config (#12)
• utopia-php/domains (#31)
• utopia-php/image (#27)
• utopia-php/locale (#16)
• utopia-php/logger (#30)
• utopia-php/mongo
• utopia-php/orchestration (#33)
• utopia-php/queue
• utopia-php/registry (#13)
• utopia-php/storage
• utopia-php/system (#24)
• utopia-php/pay
• utopia-php/platform
• utopia-php/preloader
• utopia-php/websocket

You can look at one of the PRs attached to help us migrating to GitHub actions for rest of the repos

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Upgrade our issue templates to use GitHub issue forms ✍️

Introduction

GitHub has recently rolled out a public beta for their issue forms feature. This would allow you to create interactive issue templates and validate them 🤯.

Appwrite currently uses the older issue template format. Your task is to create GitHub issue forms for this repository. Please use Appwrite's issue templates as a reference for this PR.

Tasks summary:

• Fork & clone this repository
• Prepare bug report issue form in .github/ISSUE_TEMPLATE/bug.yaml
• Prepare documentation issue form in .github/ISSUE_TEMPLATE/documentation.yaml
• Prepare feature request issue form in .github/ISSUE_TEMPLATE/feature.yaml
• Push changes to master and test issue forms on your fork
• Submit pull request

If you need any help, reach out to us on our Discord server.

Are you ready to work on this issue? 🤔 Let us know, and we will assign it to you 😊

Happy Appwriting!

📚 Documentation: App class documentation is not up to date

💭 Description

Both the README.md file and the Getting-Starting-Guide.md file suggests that there are 3 types of hooks, and that the parameters for the init hook for example are a callback function, a resources array, and a group.

However, this has not been the case for the past 2 years.

Documentation should be updated.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

W hat if I want to use external Router & Database class

Hello

1. What do I have to do in order to use an external Router class like https://github.com/bramus/router.

Reason is https://github.com/bramus/router has the features I needed + I couldn't find documentation of the router coupled with utopia PHP FrameWork.

2. Also I don't use Composer, nor do I ever pray to. Could I just copy over the framework and include it ? Checked composer.json and found no external dependency, YET I couldn't find some of the decoupled utopia classes such as the webSocket class inside utopia FrameWork files. Are the decoupled Classes meant to be manually included when needed, or I'm missing something?

3. How do I modify the HTTP class used by utopia PHP frameWork ?
   I presume it should be inside Request.php file. I want to be able to use https://github.com/stefangabos/Zebra_cURL in addition to what utopia PHP frameWork has got to offer.

My interest in utopia frameWork is that it works using just NGINx without PHP-FPM.