FS-InfMath/Jobboerse
27
0
Fork 1
Code Issues 1 Pull requests Projects Releases 17 Wiki Activity

Separate footer and fixed expiry date #46

Merged
ldr merged 12 commits from separate-footer into main 2026-03-17 19:48:48 +01:00
Conversation 0 Commits 12 Files changed 20 +6 -4
2 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit c743486643 - Show all commits

Update changelog

Prev Next
Lukas Drescher 2026-03-13 21:33:04 +01:00
commit c743486643

2
Changelog.md
View file

@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased] ## [Unreleased]
- Remove the background gradient on the index page
## [0.4.1] (2024-01-02) ## [0.4.1] (2024-01-02)
### Fix ### Fix

8
README.md
View file

@ -16,7 +16,7 @@ It is recommended to use cargo for building as such make sure the `cargo` compon
For a release build you can run `cargo build --release` this should build all dependencies and place the final binary in For a release build you can run `cargo build --release` this should build all dependencies and place the final binary in
the `./target/release/` folder. the `./target/release/` folder.
For a development build you may run `cargo build --features=dev-mode`. For a development build you may run `cargo build --features=dev_mode`.
The dev-mode features allows enabling `development` mode which allows for live template reload. The dev-mode features allows enabling `development` mode which allows for live template reload.
With the feature specified a login provider which accepts all username password combinations is also added. With the feature specified a login provider which accepts all username password combinations is also added.
Enabling this feature will also place a banner at the top of the page informing of the fact that it's running from a dev-build. Enabling this feature will also place a banner at the top of the page informing of the fact that it's running from a dev-build.
@ -30,7 +30,7 @@ By default, it starts in `production` mode, when build with the `dev-mode` featu
The table below list the default config path, it can be overridden using the `--config` flag. The table below list the default config path, it can be overridden using the `--config` flag.
| OS | Path | | OS | Path |
|-----------------------------------------|---------------------------------------------------| | --------------------------------------- | ------------------------------------------------- |
| Linux | `/etc/jobboerse/config.toml` | | Linux | `/etc/jobboerse/config.toml` |
| Windows, if `${PROGRAMDATA}` is defined | `${PROGRAMDATA}/fs-infmath/jobboerse/config.toml` | | Windows, if `${PROGRAMDATA}` is defined | `${PROGRAMDATA}/fs-infmath/jobboerse/config.toml` |
| Fallback | `./config.toml` | | Fallback | `./config.toml` |
@ -54,7 +54,7 @@ The config file uses the toml format.
The expected fields are defined by the `ProgramConfig` struct in `./src/server_config.rs`. The expected fields are defined by the `ProgramConfig` struct in `./src/server_config.rs`.
| config field | required | default | | config field | required | default |
|---------------------|----------|----------------| | ------------------- | -------- | -------------- |
| `url_base_path` | false | empty | | `url_base_path` | false | empty |
| `data_storage_path` | false | `./job_offers` | | `data_storage_path` | false | `./job_offers` |
| `banner` | false | no banner | | `banner` | false | no banner |
@ -114,7 +114,7 @@ Cutting a Release
* Update the version in the root Cargo.toml according to semver, this will be the version to-be-cut * Update the version in the root Cargo.toml according to semver, this will be the version to-be-cut
* Update the changelog to reflect all changes since the last release unter `[Unreleased]` * Update the changelog to reflect all changes since the last release unter `[Unreleased]`
* It's generally recommended to keep the Changelog upto date by adding changes to the unreleased section in the commit that introduces the change * It's generally recommended to keep the Changelog up to date by adding changes to the unreleased section in the commit that introduces the change
* In the now up-to-date changelog add a new section heading for the version to-be-cut between `[Unreleased]` and the first entry of the unreleased section * In the now up-to-date changelog add a new section heading for the version to-be-cut between `[Unreleased]` and the first entry of the unreleased section
* Add a matching link definition at the bottom of a changelog * Add a matching link definition at the bottom of a changelog
* Update the version in dist/arch/PKGBUILD to match the version to-be-cut * Update the version in dist/arch/PKGBUILD to match the version to-be-cut