Bot releases are visible (Hide)
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
This is now the new project icon and also used as the default website favicon. I've created it in Affinity Designer and added the project file to the repo, so feel free to improve him if you're good at illustrations!
Sad to hear, but I got you... It's also possible to set your own favicon in the settings.
To make this possible the database settings collection is now split up into settings_private
and settings_public
. The reason is that unauthorized users need to be able to receive the website title and the favicon, which are now stored settings_public
.
settings_private
contains the ping interval and scan ip which are only readable by admins.
If you have set your website title in the past and run UpSnap without the UPSNAP_WEBSITE_TITLE
env var then you have to set your title again. If you use the env var you are already set.
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Since version 3.1 authorisation is enabled by default.
User management is done through the PocketBase webinterface at http://localhost:8090/_/. This is mainly for internal use, such as within a home or corporate network. For external use please see below.
Api permissions listed by user role:
Api | Unauthorized | Users | Admins |
---|---|---|---|
List/Search Rule | ❌ | ✅ | ✅ |
View Rule | ❌ | ✅ | ✅ |
Create Rule | ❌ | ❌ | ✅ |
Delete Rule | ❌ | ❌ | ✅ |
Manage Rule | ❌ | ❌ | ✅ |
Wake devices | ❌ | ✅ | ✅ |
Shutdown devices | ❌ | ✅ | ✅ |
Scan network | ❌ | ❌ | ✅ |
Although UpSnap has user authorisation, it is not recommended to expose it to the open web and make it accessible by everyone!
Reason: The shutdown device command is basically a command piped to #sh (root if you run docker). If anyone gains unauthorized access and can abuse this api route in any way, the attacker has access to a (root) shell on your local network.
Recommended: If you need access from outside your network, please use a vpn. Wireguard or OpenVPN is your way to go.
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
1,10,2
, after: 1,2,10
entrypoint
in docker-compose.yml
Dockerfile
. You can remove it from your docker-compose.yml
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
For UpSnap 3 the backend was completely rewritten with Go. Also the frontend was changed to SvelteKit, updated to Bootstrap 5.3.0-alpha and now uses much less RAM and disk space than v2. Also, the Docker image has moved to ghcr.io.
Version | RAM | Storage |
---|---|---|
v2 | ~550-650 MB | ~600 MB (Docker) |
v3 | ~27 MB | ~43 MB (Binary), ~159MB (Docker) |
You can't download json files anymore. The recommended way is to backup the pb_data
directory.
You found bugs that I didn't find? Please create an issue here.