I neglected to ask if you all would mind if I posted notifications
here when changes are pushed to my GitHub repo for the new web UI.
Sorry. :D
Seems like a bunch of people are using it now, so I figured this would
be a good way to let you know when bugs are fixed and features are
added. If it's too annoying, downvote me to hell and I'll consider turning the notifications off. (Or if DM tells me to stop, I will.)
I neglected to ask if you all would mind if I posted notifications here when changes are pushed to my GitHub repo for the new web UI. Sorry. :D
Seems like a bunch of people are using it now, so I figured this would be a good way to let you know when bugs are fixed and features are added. If it's too annoying, downvote me to hell and I'll consider turning the notifications off. (Or if DM tells me to stop, I will.)
I had figured that was already happening? Or is that the Synchronet CVS that is being modified rather than github? I guess my only concern is that we would begin to see a bunch of double posts (ie: one for CVS and one for github of the same changes).
I seem to already be getting update messages here, which keeps me informed of the current happenings. If this is what I'm already seeing here, then
I've had NO issues with the first version (besides Ftelnet not refreshing after an XTRN is ran) so I stick to the addage why fix it if it is'nt
I've had NO issues with the first version (besides Ftelnet not
refreshing after an XTRN is ran) so I stick to the addage why fix it
if it is'nt
This particular issue was fixed within the last couple of weeks, so that may be a good reason to update.
I neglected to ask if you all would mind if I posted notifications here when changes are pushed to my GitHub repo for the new web UI. Sorry. :D
Seems like a bunch of people are using it now, so I figured this would be a good way to let you know when bugs are fixed and features are added. If it's too annoying, downvote me to hell and I'll consider turning the notifications off. (Or if DM tells me to stop, I will.)
I think it's a pretty great way of notifying folks. Just curious, does that file that hooks into Github work with the old web UI? I'm not quite ready to change interfaces.
There's currently no replication of the synchronet-web-v4 github repo
to the Synchronet CVS. There are a few files that I keep in both
places, but they are rarely changed and will probably disappear from github eventually.
The messages are already being posted here; I just didn't want to spam everyone if not enough people are interested.
I neglected to ask if you all would mind if I posted notifications here when changes are pushed to my GitHub repo for the new web UI. Sorry. :D
Seems like a bunch of people are using it now, so I figured this would be a good way to let you know when bugs are fixed and features are added. If it's too annoying, downvote me to hell and I'll consider turning the notifications off. (Or if DM tells me to stop, I will.)
I think it's a pretty great way of notifying folks. Just curious,
does that file that hooks into Github work with the old web UI? I'm
not quite ready to change interfaces.
I think it should work just sitting on the Synchronet webserver; it doesn't actually use any other scripts from the new web UI.
There is one line that loads a file that's part of synchronet-web-v4, but I suspect I just forgot to delete it. You could comment out line 25:
load(system.exec_dir + '../web/lib/init.js');
And then follow the instructions in the comments at the top of the file to set it up. Might work; would be good to test it on some local testing area of your BBS.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 12:43:36 |
| Calls: | 15,171 |
| Calls today: | 4 |
| Files: | 19,857 |
| D/L today: |
58 files (6,877K bytes) |
| Messages: | 1,691,646 |