Create same experience with single and non-single binary - Githubissues

go-aah / aah

A secure, flexible, rapid Go web framework

https://aahframework.org

MIT License

691 stars 33 forks source link

Create same experience with single and non-single binary #178

Closed jeevatkm closed 6 years ago

jeevatkm commented 6 years ago

Currently, I'm occupied with Virtual FileSystem (VFS) implementation for #156 and integrating VFS across the aah module's.

In aah's single binary and non-single binary, I have experienced a difference in invocation. What is it?

single binary - It doesn't come with startup scripts aah.sh and aah.cmd - aah user have to use the single binary with args.
non-single binary - aah user have to use the intermediate startup script, even though they both have same set of input args.

The goal is to bring same experience with both types of application binary. The action items are-

Remove startup aah.sh & aah.cmd
Build binary accordingly

Action Items

[x] Implementation
[x] Documentation

jeevatkm commented 6 years ago

Documentation done 😄