aah: Choosing Features and Enhancements for v0.11.0

[jeevatkm]

Hello aah users -

As you know v0.10 got released on Mar 28, 2018 with new features and enhancements. Also newly designed website, documentation presentation and per version documentation search.

I hope you're liking it 😄 Thank you for your support.

---

Let's move on to next phase of development iteration focusing on v0.11.0

As you know aah development is community driven; based on community votes, suggestion and recommendation. I would priorities it. Looking forward to your inputs.

For v0.11.0 following is my wish list-

• ORM (Data access layer)
• Configurable option of roles and permissions for each route.
• Make aah anatomy configurable Make aah anatomy configurable #152
• Add aah generate i18n command to generate i18n vars Add aah generate i18n command to generate i18n vars #119
• Websocket Websocket #126

Please have a look on Open Issues, Roadmap or new item from your need; provide your wish list or vote on my wish list.

Then finally balanced wish list would be created. Thank you 😃

[pharrisee]

Have a few work projects that I would love to use Aah for, but the lack of a few features is holding me back, namely:

Websockets / SSE
Something like https://github.com/gobuffalo/packr for bundling resources
Simple database layer, not necessarily ORM. Something like sqlx integration would be awesome.

[jeevatkm]

@pharrisee thank you for your inputs. I'm sorry to hear that its holding you.

I would like to clarify the second point - what is the expected feature? I have looked at the packr library; it converts files into binary data then compiles to binary.

[pharrisee]

Well, at the moment the packaging done by the aah cli is to create a zip file. It would be really good if the packaging built an executable which contained everything required to run the app, no external files. I can see a few issues with things like config etc, but I'm sure that should be do-able.

In fact bundling everything but the config would be good, views, css, js, images, all in the executable.

[jeevatkm]

Actually packing everything into binary is doable, no issues 😄 I will make this feature as on-demand in the build command.

• config - since aah has feature to accept config file as param so no issues. DevOps team can utilize that without engineering team effort
• views, css, js, images - DevOps team looses a capability to modify/update, they have to depend on engineering team. I guess I leave that choice to engineering team

How about startup files? As you know aah does provide startup files (.sh, .cmd).

[pharrisee]

I suppose that the startup files would be more necessary with the zipped version than the packed executable? Also packaging gives a different deployment mechanism which may actually be more in line with some environments.

[jeevatkm]

Okay, I guess its decided.

• Zip archive packing would contain startup files
• Single binary packing is just one binary

Thank you, could you please create an issue for this feature?

[pharrisee]

will do :)

[blagodus]

• ORM (Data access layer)
• Configurable option of roles and permissions for each route.
• Websockets

[jeevatkm]

Thank you @pharrisee @blagodus for your inputs and votes.

Main focus for v0.11.0 release:

• Code and flow optimization Code and flow optimization #157
• Data access layer Data Access Layer #161
• Binary resource packing Binary resource packaging #156
• Websockets Websocket #126
• Configurable option of roles and permissions for each route Configurable option of Authorization (roles and permissions) for each route #162