Accessing Lucid's Knex Connection Client
Ever need to directly access KnexJS, the query builder Lucid wraps around? Here's how you can do it!
AdonisJS 5 is a NodeJS framework that's comes packed with everything you'll need to quickly build scalable and secure applications or APIs.
Hi,
I was wondering if a chapter about production deployment will be included in the course?
Thanks in advance.
Read moreHello,
I'm trying to install Tailwindcss plugin but I'm getting an error of "require is not defined".
Here is my Tailwindcss config file
/** @type {import('tailwindcss').Config} */
export default {
content: ['./resources/views/**
...
Read more
I'm just getting started with AdonisJS, I used the web app template, and now I need to add a webhook endpoint, so I can receive events from third-party platforms(such as payments) how can I do that.
Excuse my newbie question.
UPDATE
Fixed it, ...
Read moreWhen I switch browser tabs and return to a page after some time (for example, https://adocasts.com/series/lets-learn-adonisjs-6/lessons/filtering-by-users-watched-status), the page initially appears blank. However, if I wait a moment or cli...
Read morehello guys , sorry if this is a stupid question but i have been searching for way to pass data from alpine js to edge js , in my case i need to pass an id to the route() where the id is coming from the selectedReview alpine variable :
<te...
Read moreEver need to directly access KnexJS, the query builder Lucid wraps around? Here's how you can do it!
With AdonisJS 6, layouts have been removed in favor of components. In this snippet, we provide a simple layout component example.
If your server is proxied by Cloudflare, chances are the built-in method to get the user IP Address in AdonisJS is returning Cloudflare's IP instead of your users. With this snippet, we'll fix that!
We can bind handlers to transaction events to easily defer specific actions until after the transaction has been committed and our changes have persisted to the database.
You can use route matchers to specify requirements on the route parameter. In this snippet, we require our username param to start with the @ character for the route to match.
In this lesson, we'll learn how we can combine the new InertiaJS 2 features together, along with Lucid's pagination, to add infinite scrolling to our application. This is made super easily by the last new feature we'll dicuss, called merged props.
In this lesson, we'll take a look at the new WhenVisible InertiaJS 2 component. This component uses an intersection observer to allow us to defer loading a prop's data until it is actually visible on the page.
In this lesson, we'll take a look at the new deferred props feature in InertiaJS 2. Deferred props allows us to delay a prop from loading until the page itself has mounted, which is great for slower queries or below the fold.
In this lesson, we'll take a look at the new prefetching feature in InertiaJS 2. We can use this feature to load the next page's data before the user even clicks on the link.
In this lesson, we'll cover the new polling feature in InertiaJS 2 to see how we can use it to poll our server at an interval for updated information.
During this series, InertiaJS release version 2 consisting of minimal breaking changes and several new features. In this lesson, we'll upgrade our packages to the latest for both InertiaJS & AdonisJS.
In this lesson, we'll finish our authentication rate limiting flow by clearing out any rate limits counting against the user when they reset their password.
In this lesson, we'll add AdonisJS' Rate Limiter to our web login action to restrict the number of times a user can attempt to login to our application with invalid credentials.
In this lesson, we'll create a second TailwindCSS configuration and CSS file specifically for our landing page, which we'll render with EdgeJS.
In this lesson, we'll use our access controls to apply authorization checks to the user interface of our application. This will ensure users don't see actionable items for operations they aren't allowed to perform.
In this lesson, we'll use our access controls to add authorization checks to our controllers where needed. This will help ensure members can't update, delete, or invite users.
In this lesson, we'll create our own simple authorization access control list. We'll then share this list globally throughout our application by appending it to our HttpContext and sharing it with our Vue application via Inertia.
In this lesson, we'll implement a refresh functionality on our org users and invites tables using Inertia's nifty partial data reloading feature.
In this lesson, we'll add the ability to remove users, including ourselves, from an organization. We'll also discuss a few key elements needed to handle this gracefully.
In this lesson, we'll add the ability to cancel a sent invitation to an organization.
In this lesson, we'll wrap up our invite send & accept flows by adding the UI needed to view pending organization invites as well as send new invites. We'll then walk through tests of each flow scenario to ensure all is working.
We'll add our route to handle accepting an organization invite. Within this route, we'll verify our signed url, ensure the invitation is valid, accept the invite, and gracefully handle the use-case where users may need to first login or register.
In this lesson, we'll begin our organization invite system by first adding the ability to send an invitation email to join our organization.
In this lesson, we'll query and list all current members within our active organization.
In this lesson, we'll begin work on our organization's settings page by adding the ability to update and delete the active organization.
Showing 1 to 20 of 346 results