| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
Previously, Whirl would grab the default configuration data from the the `Default` trait of
`Config`, this means that the configuration of a Docker container could not be modified. As well,
the database would be reset upon the restart of the Docker container... This solution introduces a
shared Volume directory with the label `.whirl-data` which acts as a means of persistant data
storage for Whirl.
|
| |
|
|
|
|
| |
The file name `whirl.sqlite3` is redundant as the file is already in the `.whirl` directory.
BREAKING CHANGE: Database file renamed
|
| |
|
|
|
|
|
| |
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!
|
| | |
|
| | |
|
| |
|
|
|
| |
Act provides the ability to run GitHub actions locally, read more about Act
[here](https://github.com/nektos/act).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|