Compare commits
No commits in common. "master" and "v0.1" have entirely different histories.
1
.gitignore
vendored
1
.gitignore
vendored
@ -1 +0,0 @@
|
||||
*.snap
|
@ -3,4 +3,6 @@
|
||||
set -e
|
||||
|
||||
cp $SNAP/default.conf $SNAP_DATA/config
|
||||
chmod 600 $SNAP_DATA/config
|
||||
# The config file should not be world readable, but the snap user can't read it
|
||||
# either if it is chmodded. How to solve this?
|
||||
#chmod 600 $SNAP_DATA/config
|
||||
|
@ -1,6 +1,5 @@
|
||||
name: mythicbeastsddns
|
||||
version: 'git'
|
||||
base: core22
|
||||
summary: Automatically update dynamic dns for your Mythic Beasts hosts
|
||||
description: |
|
||||
Mythic Beasts customers can use this snap to automatically update dynamic dns
|
||||
@ -8,11 +7,12 @@ description: |
|
||||
ipv4hostname and ipv6hostname using the `snap set` command as detailed at
|
||||
https://docs.snapcraft.io/reference/snap-command#set . Activate the updater by
|
||||
setting the updateipv4 and/or updateipv6 keys to "yes".
|
||||
.
|
||||
BEWARE - passwords are stored in world-readable plain text. Until I can find a
|
||||
way around this problem do not use this snap in production.
|
||||
grade: stable
|
||||
confinement: strict
|
||||
architectures:
|
||||
- build-on: [amd64]
|
||||
build-for: [all]
|
||||
architectures: [ all ]
|
||||
|
||||
apps:
|
||||
mythicbeastsddns:
|
||||
|
Loading…
x
Reference in New Issue
Block a user