Releases: dullage/flatnotes
Releases · dullage/flatnotes
v3.2.1
🗒️ Notable changes:
- There is a new
read_only
authentication type. This is similar tonone
(no authentication) but - as the name implies - doesn't allow creation, modification or deletion. An example use case could be to use flatnotes for documentation or a blog. Resolves #72. - The
/api/token
endpoint is no longer loaded when authentication is disabled (i.e. theFLATNOTES_AUTH_TYPE
is set tonone
orread_only
). - The API no longer requires a dummy bearer token when authentication is disabled. Resolves #90.
🪲 Bug Fixes:
- Fixed an issue displaying lists in tables when using the dark theme. Resolves #94.
v3.1.1
🗒️ Notable changes:
v3.1.0
🗒️ Notable changes:
- Tags are no longer detected when contained within a code block. Thanks to @elmodor
- Extended autolinks have been enabled when rendering markdown. This means that URLs should be clickable even if they are not enclosed in a markdown link syntax e.g.
[link](url)
.
Note: To accommodate the change to tag detection, the index version has been bumped. This will mean a full re-index of all notes on first run and may take some time on larger datasets.
v3.0.3
v3.0.2
v3.0.1
v3.0.0
🚨 Breaking Changes
- The port flatnotes uses inside the Docker container has been changed to
8080
(previously80
). If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly. This change was made to smooth the onboarding process for environments where privileged ports cannot be used by non-privileged users (see #28). - To accompany the above change, support for the
PORT
environment variable has been removed. - The note directory inside the Docker container has moved from
/app/data
to simply/data
. If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly.
🗒️ Notable changes
- flatnotes now has a dark theme! 🌚
- New
PUID
andGUID
environment variables are now supported for Docker deployments. These allow you to specify the user and group that flatnotes will run as inside the Docker container. This is useful to avoid permission issues when mounting a directory from the host. - To support the above change, upon container start, the ownership of all files and directories in the data directory will be recursively changed to the specified user and group.
v3.0.0-rc.6
To use this pre-release please use the docker image tag dullage/flatnotes:v3.0.0-rc.6
.
🚨 Breaking Changes
- The port flatnotes uses inside the Docker container has been changed to
8080
(previously80
). If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly. This change was made to smooth the onboarding process for environments where privileged ports cannot be used by non-privileged users (see #28). - To accompany the above change, support for the
PORT
environment variable has been removed. - The note directory inside the Docker container has moved from
/app/data
to simply/data
. If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly.
🗒️ Notable changes
- flatnotes now has a dark theme! 🌚
- New
PUID
andGUID
environment variables are now supported for Docker deployments. These allow you to specify the user and group that flatnotes will run as inside the Docker container. This is useful to avoid permission issues when mounting a directory from the host. - To support the above change, upon container start, the ownership of all files and directories in the data directory will be recursively changed to the specified user and group.
v3.0.0-rc.5
To use this pre-release please use the docker image tag dullage/flatnotes:v3.0.0-rc.5
.
🚨 Breaking Changes
- The port flatnotes uses inside the Docker container has been changed to
8080
(previously80
). If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly. This change was made to smooth the onboarding process for environments where privileged ports cannot be used by non-privileged users (see #28). - To accompany the above change, support for the
PORT
environment variable has been removed. - The note directory inside the Docker container has moved from
/app/data
to simply/data
. If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly.
🗒️ Notable changes
- flatnotes now has a dark theme! 🌚
- New
PUID
andGUID
environment variables are now supported for Docker deployments. These allow you to specify the user and group that flatnotes will run as inside the Docker container. This is useful to avoid permission issues when mounting a directory from the host. - To support the above change, upon container start, the ownership of all files and directories in the data directory will be recursively changed to the specified user and group.
v3.0.0-rc.4
To use this pre-release please use the docker image tag dullage/flatnotes:v3.0.0-rc.4
.
🚨 Breaking Changes
- The port flatnotes uses inside the Docker container has been changed to
8080
(previously80
). If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly. This change was made to smooth the onboarding process for environments where privileged ports cannot be used by non-privileged users (see #28). - To accompany the above change, support for the
PORT
environment variable has been removed. - The note directory inside the Docker container has moved from
/app/data
to simply/data
. If you using Docker to deploy flatnotes you will need to update your docker/docker-compose commands accordingly.
🗒️ Notable changes
- flatnotes now has a dark theme! 🌚
- Browser font size settings are now honoured. < This was reverted in the next release.
- New
PUID
andGUID
environment variables are now supported for Docker deployments. These allow you to specify the user and group that flatnotes will run as inside the Docker container. This is useful to avoid permission issues when mounting a directory from the host. - To support the above change, upon container start, the ownership of all files and directories in the data directory will be recursively changed to the specified user and group.