Brain dump of questions and ideas in no particular order. Or simply stated, a verbose README.
What will the command/binary name be? (e.g. git, npm)
lagerlgblblg
@bmallred: Mmm... lager.
How does backlager get initialized? Maybe stick to similiar git commands?
backlager init --hops
@bmallred: Sounds good. What is the flag --hops intended for?
Backlager will be file agnostic as long as there's a reader for it. Examples
- .json
- .md
- .yaml
- .toml
- .xml (yes, gross but many people like to torture themselves)
- .ini
- .txt (This maybe reflects a customized lager specifc format?)
@bmallred: I'm leaning that way. Thinking of tackling
.mdfirst and then just widdling away
Should we have a 'lager' format? deployment_script_32.hops
@bmallred: Ha, why not? If they don't use it then so be it!
Should backlager be able to generate a local static web application containing all artifacts so that users can view them?
backlager servebacklager serve --filename file1, file2
@bmallred: Yes. I think this would go a long way for adoption b/c:
- some people don't like command line
- some people like pretty
- and, people would not need to utilize a SaaS just to get work done.
It also has the added benefit of working when there is no internet connection.
- Same concept as
godoc.org. Web interface should read in those files and render on a site
- Given the distributed and flexible nature of backlager, the onus is on the users to develop a security plan.
- What if users want to control permissions?