EasyRls is an open-source project designed to simplify the management of Row Level Security (RLS) policies in PostgreSQL databases. With EasyRls, you can easily connect to your PostgreSQL instance, manage schemas and tables, and create, edit, or delete RLS policies—all through an intuitive interface that supports both light and dark themes.
easyRls.Demo.mp4
- Connect to PostgreSQL Instances: Easily connect to any PostgreSQL instance using a connection string.
- List Schemas: View all schemas available in your connected PostgreSQL instance.
- List Tables in a Schema: Navigate through schemas to list all tables within a selected schema.
- RLS Policy Status: Check the RLS policy status on any table, enabling you to quickly identify which tables have RLS policies applied.
- Enable/Disable RLS Policies: Toggle RLS policies on and off as needed for any table.
- Manage RLS Policies:
- List All RLS Policies: View a list of all RLS policies applied to a specific table.
- Create New RLS Policy: Easily create new RLS policies to manage data access at a granular level.
- Edit Existing Policy: Modify existing RLS policies to adapt to changing requirements.
- Delete Policy: Remove unnecessary RLS policies with ease.
- Copy Policy: Duplicate existing RLS policies to streamline the creation of similar policies.
- Search Functionality: Search through schemas, tables, and policies to quickly find what you need.
- Light and Dark Theme: Choose between light and dark themes for a comfortable user experience.
This tool is used solely for displaying data from your database. We do not store or retain any data related to your database or its contents on our end.
To get started with EasyRls, follow these steps:
-
Clone the repository:
git clone https://github.com/yourusername/EasyRls.git cd easyRls
-
Install dependencies:
npm install
-
Start the application:
npm start
- Connect to your PostgreSQL instance using the provided connection string interface.
- Explore schemas and tables to manage RLS policies.
- Create, edit, or delete RLS policies as per your requirements.
If it says "SAML ERROR", double check your password for @
,#
and other special characters. They are not properly encoded and if issue still persists, try to use psql
instead of postgres
in prefix of connection string
Contributions from the community are welcomed! If you'd like to contribute, please read our Contributing Guide and Code of Conduct.
This project is licensed under the MIT License - see the LICENSE file for details.