Lotus

Lotus takes a unique approach to organizing its codebase, being made up of smaller frameworks, each with its own purpose.

Putting them together remains up to the developer, each section covering a specific area and feature.

By taking this route, the Lotus team has made sure the framework's core will not get bloated with too much functionality and avoids situations where developers have to load code that never gets used.

Lotus can so be used on a per-project basis, activating only the modules  needed for specific tasks and features.

The framework follows a general OOP architecture, but MVC principles can also be found in its smaller parts.

Basic Lotus modules provide support for:
- HTTP routing
- a view layer
- utility belt classes
- data validation
- view helpers
- a controller
- a data persistence model

What is new in this release:

• Added:
• Introduced action generator. Eg. bundle exec lotus generate action web dashboard#index.
• Allow to specify default coookies options in application configuration. Eg. cookies true, { domain: 'lotusrb.org' }.
• Include Lotus::Helpers in views.
• Allow to specify --database CLI option when generate a new application. Eg. lotus new bookshelf --database=postgresql.
• Initialize a Git repository when generating a new application.
• Produce .lotusrc when generating a new application.
• Security HTTP headers. X-Frame-Options and Content-Security-Policy are now enabled by default.
• Database console. Run with bundle exec lotus db console.
• Dynamic finders for relative and absolute routes. It implements method missing: Web::Routes.home_path will resolve to Web::Routes.path(:home).
• Changed:
• Cookies will send HttpOnly by default. This is for security reasons.
• Enable templates configuration for new generated apps.
• Change SQLite file extension from .db to .sqlite3.

Requirements:

• Ruby 2 or higher