| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The long awaited `generate` sub-command is finally here. You may now generate yourself a default
configuration file by running `whirl config generate`!
|
| |
|
|
|
|
|
|
| |
At the moment, the `version` key is never accessed, but once Whirl's "`1.0`" release is out, the
configuration schema will need to be standardized, the `version` key will regulate that and also
ensure no one is left behind when updating.
BREAKING CHANGE: `version` key is created
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Since the configuration file is in the `.whirl` directory, it is redundant to have it's name still
as `Whirl.toml`
BREAKING CHANGE: Configuration file is renamed
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This change is in preperations to the new Docker Compose configuration changes that are planned for
the near future. Currently, the Docker Compose configuration does NOT have persistant storage in the
form of Docker Volumes, that will change once the planned updates are pushed. The reason Docker
Volumes might have not been possible (or at least difficult) is due to the fact that Whirl-generated
files were just thrown about, e.g., `whirl.sqlite3`, `Whirl.toml`, all of these files had no central
location so having a shared folder in the form of Docker Volume between the container and the host
wasn't very possible.j
BREAKING CHANGE: Whirl-generated files are moved to their own directories, if the files are not
moved, Whirl will continue to look for these files and panic due to being unable to find them!
|
| |
|
|
| |
This change makes clippy **a lot** more strict.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|