📄️ Creating a Background Worker with Exec and Faktory
In this how to, we'll use Redwood's exec CLI command to create a background worker using Faktory.
📄️ Custom Function
You may not have noticed, but when you're making GraphQL calls, you're actually calling a Function (not to be confused with a Javascript function) on the API side. Capital-F Functions are meant to be deployed to serverless providers like AWS Lambda. (We're using Netlify's nomenclature when we call them Functions.)
📄️ Disable API/Database
Did you know you could deploy your Redwood app without an API layer or database? Maybe you have a simple static site that doesn't need any external data, or you only need to digest a simple JSON data structure that changes infrequently. So infrequently that changing the data can mean just editing a plain text file and deploying your site again.
📄️ File Uploads
As you've probably heard, Redwood thinks the future is serverless. This concept introduces some interesting problems you might not have had to worry about in the past. For example, where do files go when you upload them? There's no server! Like many tasks you may have done yourself in the past, this is another job that we can farm out to a third-party service.
📄️ GoTrue Auth
If you've completed the Authentication section of The Tutorial, you've seen how you can add the Netlify Identity Widget to your Redwood app in a matter of minutes.
📄️ Mocking GraphQL in Storybook
Pre-requisites
📄️ Pagination
This tutorial will show you one way to implement pagination in an app built using RedwoodJS. It builds on top of the tutorial and I'll assume you have a folder with the code from the tutorial that you can continue working on. (If you don't, you can clone this repo//github.com/thedavidprice/redwood-tutorial-test)
📄️ Role-based Access Control (RBAC)
Role-based access control (RBAC) in RedwoodJS aims to be a simple, manageable approach to access management. It adds control over who can access routes, see features, or invoke services or functions to the existing useAuth() hook on the web side and requireAuth() helper on the api side.
📄️ Self-hosting Redwood (Serverful)
This doc has been deprecated in favor of the Baremetal docs.
📄️ Sending Emails
Something a lot of applications will eventually have to do is send emails. To demonstrate how you can do that with RedwoodJS we're going to build a simple list of users and their email addresses, and allow you to trigger an email to them. We'll also include some auditing features, so you get a history of emails you sent to your users. The audit logs will be implemented by using one service from within another service — a powerful RedwoodJS feature.
📄️ Supabase Auth
Let's call this how to a port of the Redwood GoTrue Auth how to to Supabase.
📄️ Testing Redwood in GitHub actions
A good testing strategy is important for any project. Redwood offers a few different types of tests that you can write to make your app more robust—to ship with confidence. In this guide we'll focus on how to run your Redwood tests in GitHub Actions, so you can test your app on every push or pull request.
📄️ Using a Third Party API
The time will come when you'll need data from a source you don't own. This how to will present the scenario of accessing a third party's API from a Redwood app. We'll show an example of accessing an API from both the client side and the server side.
📄️ Windows Development Setup
This guide provides a simple setup to start developing a RedwoodJS project on Windows. Many setup options exist, but this aims to make getting started as easy as possible. This is the recommended setup unless you have experience with some other shell, like PowerShell.