viktormarinho / enable

Highly portable feature flag service

Enable

Enable is a portable feature flag (aka feature toggles) service, contained in a single executable file.

Taking inspiration from the Pocketbase project, enable can be easily downloaded as a single binary and run anywhere as long as rust can compile to it.

Enable is built using Axum, Svelte and utilizes SQLite3, one of if not the best alternative for having a portable database.

How to run Enable

• Clone the repository (or create a codespace)
  • git clone https://github.com/viktormarinho/enable
• Install the sqlx cli
  • Cargo install sqlx-cli
• Reset database and do migrations
  • sqlx db reset
• Run the project
  • Cargo run

Be happy :)

enable's Issues

Create a Project settings page

Create a Project settings page, that supports:

• renaming the project (with or without renaming all feature prefixes)
• deleting the project
• idk for now this looks ok

Github action for publishing releases

Create a Project history page

Create a Project history page, that shows searchable information in a timeline.
The timeline should show logs about every feature change, creation, etc

Instance monitoring page

Create a page that shows a web requests/resources monitoring panel for the running Enable instance.
Maybe also make it searchable ? but idk how good.
Maybe monitoring for individual projects as well

User can create two projects with the same name

Users can create two projects with the same name, resulting in being unable to create some features even though they do not exist in that project

Change environment list select to custom dropdown

This one is kinda ugly, does not reflect the rest of the UI appearance and do not support adding buttons inside environments (for deleting them) that i will add in the future

Consider if migrating to `tower-sessions` is appropriate

Hi folks,

I'm the author of axum-sessions, which is a crate I see you all are using--I'm glad to see you've found it useful!

Over the course of the last year or so we've hit some roadblocks with our key dependency, async-session. The long and short of that is in order to unblock that and address some problems with axum-sessions's design, we've released a new crate which aims to replace axum-sessions: tower-sessions.

tower-sessions no longer relies on a third-party crate for its session implementation and this has allowed us to change its design to better fit tower and the broader tower ecosystem (i.e. axum). For instance, we no longer need writable and readable sessions, and have simplified the interface as a result.

I'd be curious if there's interest in migrating and am happy to help if so.