Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
2 tasks done
jeevatkm opened this issue May 14, 2018 · 1 comment
Closed
2 tasks done

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

jeevatkm opened this issue May 14, 2018 · 1 comment
Assignees
Labels
aah Framework scope cli-tool aah CLI tool enhancement

Comments

@jeevatkm
Copy link
Member

jeevatkm commented May 14, 2018

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

  • Implementation
  • Documentation
@jeevatkm
Copy link
Member Author

Documentation done 😄

jeevatkm added a commit to go-aah/app-templates that referenced this issue Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aah Framework scope cli-tool aah CLI tool enhancement
Projects
None yet
Development

No branches or pull requests

1 participant