atd issueshttps://staging.gitlab.com/izwick-schachter/atd/-/issues2017-06-29T11:39:46Zhttps://staging.gitlab.com/izwick-schachter/atd/-/issues/22What is the status of commands?2017-06-29T11:39:46Zusername-removed-662768What is the status of commands?In earlier versions we had a command line tool, but the code is fairly useless and disorganized, we really should clean it up. The docs are also very ambiguous.In earlier versions we had a command line tool, but the code is fairly useless and disorganized, we really should clean it up. The docs are also very ambiguous.Backloghttps://staging.gitlab.com/izwick-schachter/atd/-/issues/12Rackup ignores port2017-06-29T11:39:46Zusername-removed-662768Rackup ignores portBackloghttps://staging.gitlab.com/izwick-schachter/atd/-/issues/5Restart server on changes2017-06-29T11:39:46Zusername-removed-662768Restart server on changesI suggest we use the [Listen](https://github.com/guard/listen) gem, which is a part of guard. Some key functions:
* [ ] For static files, it should be possible to reload one file without reloading the whole server
* [ ] The only thing...I suggest we use the [Listen](https://github.com/guard/listen) gem, which is a part of guard. Some key functions:
* [ ] For static files, it should be possible to reload one file without reloading the whole server
* [ ] The only thing that should trigger a full restart is change of .rb files
* [ ] It should be on by default, but it should be possible to not use listen at all, because there may be compatibility issues.
Basically, when a .rb file is changed, it should reload the server. When a file in the `assets` dir is changed, it should reload that file.
This is important because this is a very useful development feature.Backloghttps://staging.gitlab.com/izwick-schachter/atd/-/issues/4Business logic integration2017-06-29T11:39:46Zusername-removed-662768Business logic integrationWe should decide and document how business logic should be integrated into the app.We should decide and document how business logic should be integrated into the app.Backloghttps://staging.gitlab.com/izwick-schachter/atd/-/issues/3Add Database compatibilty2017-06-29T11:39:46Zusername-removed-662768Add Database compatibiltyAs a first priority, I would suggest we add some way to easily include activerecord, because that is a vital part of most database applications. Even if we don't we should still add instructions in the README.
Here are some suggestions:...As a first priority, I would suggest we add some way to easily include activerecord, because that is a vital part of most database applications. Even if we don't we should still add instructions in the README.
Here are some suggestions:
- We have a DB class, which is responsible for connecting to the DB and is called with `ATD::App#start`
- We don't explicitly support a DB, but we list ways to use popular ORMs
- (Not recommended) We say nothing and leave it to our users to figure it out.Backlog