eggs
eggs copied to clipboard
Add ntfy egg
Description
Ntfy is a simple HTTP-based pub-sub notification service. It allows you to send notifications to your phone or desktop via scripts from any computer, and/or using a REST API.
Closed issue requesting ntfy: #2471
Checklist for all submissions
- [x] Have you followed the guidelines in our Contributing document?
- [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
- [x] Have you tested and reviewed your changes with confidence that everything works?
- [x] Did you branch your changes and PR from that branch and not from your master branch?
- If not, why?:
- [ ] You verify that the start command applied does not use a shell script
- [ ] If some script is needed then it is part of a current yolk or a PR to add one
- [ ] The egg was exported from the panel
New egg Submissions
- [x] Does your submission pass tests (server is connectable)?
- [ ] Does your egg use a custom docker image?
- [ ] Have you tried to use a generic image?
- [ ] Did you PR the necessary changes to make it work?
- [x] Have you added the egg to the main README.md and any other README files in subdirectories of the egg (e.g /game_eggs) according to the alphabetical order?
- [x] Have you added a unique README.md for the egg you are adding according to the alphabetical order?
- [x] You verify that the start command applied does not use a shell script
- [ ] If some script is needed then it is part of a current yolk or a PR to add one
- [x] The egg was exported from the panel
@QuintenQVD0 Ive added the changes you suggested could you look over it again?
looks fine to me, just have to test it.
@ThnksCJ How to we use this as the issue was closed because you like need to change the startup off the egg. so how does this egg handle this as I do not know this aplication
You can configure the server.yml file that gets created and it's already pre-configured with a working config on the default allocation host and port. You can configure it to add a proxy host and such but you would need to look through the docs for that. If you span up an instance and visited it on http then it would all be working as a basic thing
@QuintenQVD0 I changed the way the config is made to make it hopefully a bit more user friendly, could you look over it? Thanks 👍🏻
how do you manage users if the startup command is hard coded?
(to manage users and permissions it's ntfy user ...
and ntfy access ...
how do you manage users if the startup command is hard coded? (to manage users and permissions it's
ntfy user ...
andntfy access ...
change the startup in the egg or server, when you are admin?
how do you manage users if the startup command is hard coded? (to manage users and permissions it's
ntfy user ...
andntfy access ...
change the startup in the egg or server, when you are admin?
why? it would be enough to make the startup like ntfy {{ARGS}}
and make an env variable where the user can type user add xxx
etc.
I thought users could be added using the web UI and it work the same as using a cmd to do it
it should indeed, as the user will never be allowed to change the startup themselves in offical eggs.
I thought users could be added using the web UI and it work the same as using a cmd to do it
how? in the web UI the add user button is only a way to log into users made with ntfy user add ...
, and in the web UI there's no way to manage permissions (ntfy access ...
)
if that is true, this egg likely will be closed as uses are not allowed to self edit the startup
I thought users could be added using the web UI and it work the same as using a cmd to do it
how? in the web UI the add user button is only a way to log into users made with
ntfy user add ...
, and in the web UI there's no way to manage permissions (ntfy access ...
)
I must have overlooked this fact, mabye ntfy won't work as an egg after all
if that is true, this egg likely will be closed as uses are not allowed to self edit the startup
can't it be done like so?
like ntfy ${OPTIONS}
where OPTIONS
is a user_editable
variable
if that is true, this egg likely will be closed as uses are not allowed to self edit the startup
can't it be done like so? like
ntfy ${OPTIONS}
whereOPTIONS
is auser_editable
variable
That would be better but is almost the same as just giving the user direct startup asses as you put a ; and the command and the panel will run it.
Doesn't the nodejs egg do something like that to start the main file? Wouldn't you be able to put a ; and it escape too
Doesn't the nodejs egg do something like that to start the main file? Wouldn't you be able to put a ; and it escape too
yes technically yes, but that variable is locked to a max of 64 char and should (it is not) be locked with alpha_dash rule what as it sas only allows letters and _ and not symbols.
Then could you not do the same on this egg? Or would that raise password security issues
Then could you not do the same on this egg? Or would that raise password security issues
Problem is it does not allow for -
so many things (that's wy for node it is not set) will not work.
Even uppercase char are not allowed in alpha_dash. so I guess then indeed just lock it to 64 length and do it that way.
@ThnksCJ Can an admin used create other users on the web interface or is it all command line interface, else we just create 1 stock user.
seems like larvel 10 allowed - so alpha_dash
should be the way to go
From what i have read it all has to be done using the cli which is an issue, that is to create specific channels locked behind authentication. Not sure how we could overcome this issue without making a custom image that has a shell to accept commands or somehting
From what i have read it all has to be done using the cli which is an issue, that is to create specific channels locked behind authentication. Not sure how we could overcome this issue without making a custom image that has a shell to accept commands or somehting
That wont be happening.
found out in the server.yml
file you can add these 3 settings
enable-signup: true # anyone can create an account through the web ui
enable-login: true # anyone can login into accounts through the web ui using user and pass
enable-reservations: true # anyone can reserve topics for themselves
only limit is you can't choose who can make accounts and who can't, or who can reserve and who can't
however technically you can if you enable these settings only when you want to create an account or manage reserved topics and disable when you don't need to
found out in the
server.yml
file you can add these 3 settingsenable-signup: true # anyone can create an account through the web ui enable-login: true # anyone can login into accounts through the web ui using user and pass enable-reservations: true # anyone can reserve topics for themselves
only limit is you can't choose who can make accounts and who can't, or who can reserve and who can't
however technically you can if you enable these settings only when you want to create an account or manage reserved topics and disable when you don't need to
its even yaml so you could add variable for those nad let the config parser turn them on and off