Snarl 5.0 Beta 8 Released!

fullphat commented 6 years ago

Key Changes

Listeners set to reject forwards and subscription requests now reject them correctly. (47.114)
Change management UI to be more mobile- and tablet-friendly. (47.114)
Added ConfigurationFileUrl and ConfigurationFilePath to sysadmin.json, which can be used to direct Snarl to load its configuration from a different location. Snarl will try ConfigurationFileUrl first, then ConfigurationFilePath, and then fail back to the usual %APPDATA% location. (47.114)
Added several new features to sysadmin.json. (47.114)
Completely revised settings format. registrations.rc, the /etc/apps folder, forwards.rc, listeners.rc, subscriptions.rc and settings.rc have all been combined into a single settings.json file. (47.114)
SNP 3.1 transport now supports AES256 encrypted messages. (47.114)
Now return ERROR_AUTH_FAILURE when auth provided but not needed. (47.114)
SNP 3.1 now supports single \r, single \n or \n\r pairs as line end markers for requests. (47.114)

IMPORTANT NOTE

As the way settings are managed has changed in Beta 8, you’ll need to use the R5ConfigConverter app in the /tools/ folder to migrate the various settings files into the new JSON formatted one.

fruza commented 6 years ago

Hi!.

I cannot get to make it work ConfigurationFilePath. I have the following in my sysadmin.json file:

{ "HideIcon": true, "ConfigurationFilePath": "C:\PUB\", }

And snarl always goes to %APPDATA% for the configuration files:

-=-=- Snarl logging started -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- bootstrap: Thu, 12 Apr 2018 07:07:56 GMT bootstrap: o/s info follows... platform: Win32NT version: Microsoft Windows NT 6.1.7601 Service Pack 1 service pack: Service Pack 1 bootstrap: server info follows... release: 5.0 Beta 8 api: 47 sys: 47.114 bootstrap: getting sysadmin settings... bootstrap: initialising settings... bootstrap: starting UI... bootstrap: checking user data folders... bootstrap: %APPDATA% is "C:\Users\ffrr12\AppData\Roaming\" bootstrap: starting Win32 IPC transport... bootstrap: starting management server on '*:9989'... bootstrap: management server started! bootstrap: starting SnarlOSD... bootstrap: starting notification roster... NotificationRoster.Start(): %appdata% is C:\Users\ffrr12\AppData\Roaming\full phat\snarl 5.0\etc\ NotificationRoster.Start(): loading osd.rc... NotificationRoster.readOsdConfig(): reading osd settings... NotificationRoster.Start(): checking osd presets folder... NotificationRoster.getOsdPresets(): loading osd presets... bootstrap: starting application roster... bootstrap: starting extension roster... bootstrap: starting rules roster... bootstrap: starting presence monitor... bootstrap: enabling... bootstrap: displaying welcome message... bootstrap: starting network roster... NetworkRoster.Start(): loading custom transports... NetworkRoster.Start(): loading listeners... NetworkRoster.Start(): starting listeners... NetworkRoster.Start(): loading subscriptions... NetworkRoster.Start(): loading forwarders... bootstrap: main startup completed, other threads may still be initialising

I'm doing something wrong, don't I?.

Best regards, Fernando.

fullphat commented 6 years ago

ConfigurationFilePath needs to point to the actual settings file, so if it was called settings.json, then it would need to be C:\PUB\settings.json

fruza commented 6 years ago

Sorry but it doesn't work. When I start snarl it makes the directory structure in %APPDATA%\full phat although I have got my settings.json file in: C:\PUB\settings.json

The sysadmin.json file has the following:

{ "ConfigurationFilePath": "C:\PUB\settings.json", "HideIcon": true, }

The log says:

-=-=- Snarl logging started -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- bootstrap: Fri, 13 Apr 2018 11:06:21 GMT bootstrap: o/s info follows... platform: Win32NT version: Microsoft Windows NT 6.1.7601 Service Pack 1 service pack: Service Pack 1 bootstrap: server info follows... release: 5.0 Beta 8 api: 47 sys: 47.114 bootstrap: getting sysadmin settings... bootstrap: initialising settings... bootstrap: starting UI... bootstrap: checking user data folders... bootstrap: %APPDATA% is "C:\Users\ffrr12\AppData\Roaming\" bootstrap: starting Win32 IPC transport... bootstrap: starting management server on '*:9989'... bootstrap: management server started! bootstrap: starting SnarlOSD... bootstrap: starting notification roster... NotificationRoster.Start(): %appdata% is C:\Users\ffrr12\AppData\Roaming\full phat\snarl 5.0\etc\ NotificationRoster.Start(): loading osd.rc... NotificationRoster.Start(): copying default osd.rc... NotificationRoster.readOsdConfig(): reading osd settings... NotificationRoster.Start(): checking osd presets folder... NotificationRoster.Start(): not found: copying default content... NotificationRoster.getOsdPresets(): loading osd presets... bootstrap: starting application roster... bootstrap: starting extension roster... bootstrap: starting rules roster... bootstrap: starting presence monitor... bootstrap: enabling... bootstrap: displaying welcome message... bootstrap: starting network roster... NetworkRoster.Start(): loading custom transports... NetworkRoster.Start(): loading listeners... NetworkRoster.Start(): starting listeners... NetworkRoster.Start(): loading subscriptions... NetworkRoster.Start(): loading forwarders... bootstrap: main startup completed, other threads may still be initialising

Best regards, Fernando.

fullphat commented 6 years ago

Just given it a try, can you modify your sysadmin.json to use double-backslashes like this?

{
  "ConfigurationFilePath": "C:\\PUB\\settings.json",
  "HideIcon": true,
}

That should hopefully work!

fruza commented 6 years ago

It seems that it works however the log file does say nothing about where it gets the settings.json file and it still talks about %APPDATA%. Also when I start snarl if I don't have the configuration directory in %APPDATA%, snarl creates it in %APPDATA%/full phat:

-=-=- Snarl logging started -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- bootstrap: Sat, 14 Apr 2018 11:34:25 GMT bootstrap: o/s info follows... platform: Win32NT version: Microsoft Windows NT 6.1.7601 Service Pack 1 service pack: Service Pack 1 bootstrap: server info follows... release: 5.0 Beta 8 api: 47 sys: 47.114 bootstrap: getting sysadmin settings... bootstrap: initialising settings... bootstrap: starting UI... bootstrap: checking user data folders... bootstrap: %APPDATA% is "C:\Users\ffrr12\AppData\Roaming\" bootstrap: starting Win32 IPC transport... bootstrap: starting management server on '*:9989'... bootstrap: management server started! bootstrap: starting SnarlOSD... bootstrap: starting notification roster... NotificationRoster.Start(): %appdata% is C:\Users\ffrr12\AppData\Roaming\full phat\snarl 5.0\etc\ NotificationRoster.Start(): loading osd.rc... NotificationRoster.Start(): copying default osd.rc... NotificationRoster.readOsdConfig(): reading osd settings... NotificationRoster.Start(): checking osd presets folder... NotificationRoster.Start(): not found: copying default content... NotificationRoster.getOsdPresets(): loading osd presets... bootstrap: starting application roster... bootstrap: starting extension roster... bootstrap: starting rules roster... bootstrap: starting presence monitor... bootstrap: enabling... bootstrap: displaying welcome message... bootstrap: starting network roster... NetworkRoster.Start(): loading custom transports... NetworkRoster.Start(): loading listeners... NetworkRoster.Start(): starting listeners... NetworkRoster.Start(): loading subscriptions... NetworkRoster.Start(): loading forwarders... bootstrap: main startup completed, other threads may still be initialising

My sysadmin.json file:

{ "ConfigurationFilePath": "C:\PUB\settings.json", "HideIcon": true, }

If I have a settings.json file, has snarl got to make also the directory %APPDATA%\full phat ??. I guess that if I have got all the configuration in the settings.json file it's not needed %APPDATA%\full phat directory. Also if I have got sysadmin.json the "ConfigurationFilePath" pointing to "C:\PUB\settings.json" the log file would have to say something about it.

Best regards, Fernando.

fullphat commented 6 years ago

Glad it’s working now! I’ve added more useful debug output to Beta 9 (this helped me find the error you were having) and I’ll stop Snarl from creating the APPDATA folder tree if it’s using a central config.

fruza commented 6 years ago

Hi!. Any news about the snarl Beta 9?. I'm looking forward to testing it soon with the new improvements.

Best regards, Fernando.

fullphat commented 6 years ago

Uploading now! Please let me know how it goes...

https://sourceforge.net/projects/snarlwin/files/Snarl/R5/Beta/

fruza commented 6 years ago

Hi again!. Sorry for the delay. I've been very busy this summer and I have not could test snarl. Now I'm ready to give it a try again! ;-)

I'm running the last version: Beta 9. In management server says Release 5.0 Version 47.116. I have got all settings in a settings.json network centralized file. Everything ok except it still creates %APPDATA%\full phat folder with just the osd.rc settings. Is it not possible to include these settings also in settings.json file and do not create the %APPDATA%\full phat folder ??.

Thanks. Fernando.

fruza commented 6 years ago

Hi fullphat!!. Any news? Is still this project alive?. I don't see too much movement since April.

fullphat commented 6 years ago

Hi Fruza! Yes, absolutely, we're still going strong! :-)

I've been working on a separate project recently, but so far as Snarl goes, I'm pulling together the final requirements for 5.0 general release.

fruza commented 6 years ago

Oh, great to hear from you, fullphat!!. I thought I was alone because I didn't see to much movement in the last months.

Did you see something regarding my last post?. We are planned to deploy snarl where I work (a Hospital in Spain) and it is aproximately a thousand machines and we need to have centralized all configuration and it still creates %APPDATA%\full phat folder with just the ### osd.rc settings.

Thanks and regards, Fernando.

fullphat commented 6 years ago

Yeah, I've standardised most of the settings now into a single json file. The OSD part is still to be done - I'll add that to the to-do list...

fullphat commented 6 years ago

Created issue #53 to cover this and added it to the R5 release milestone

fullphat commented 6 years ago

@fruza just a quick note about your last comment regarding osd.rcin %APPDATA%...

Because of the quirky way the OSD component of Snarl works, you will still see an osd.rc file created in %APPDATA%\full phat\snarl 5.0, however this will just be a transitory file that the OSD component will pick up. Snarl itself will pull the information from whatever global file you create and use this to build the local osd.rc file each time it starts up.

Let me know if that's a possible issue for you?

fruza commented 6 years ago

Hi!

If I don't understand bad you mean it is going to be possible to include all osd information in the centralized settings.json file however meanwhile it still will be created the osd.rc in %APPDATA%\full phat\snarl 5.0. Ok, right!, It could be worth, however I think if someone, like me, want the configuration centralized it is because it doesn't want to have something in local. If it's something temporal regarding the OSD component, all right, but I wouldn't like to have something locally.

Imagine you've got to deploy and administer snarl in more than a thousand machines so that it would be possible to send informations and important notifications to all company users, the best it's to have all snarl's configurations centralized and don't create something locally. We do have roaming profiles for most of the users and the folder %APPDATA%\full phat\snarl 5.0 travels from our file server every time the user login and logoff so if it doesn't exist too much better.

Thanks anyway @fullphat for you time and effort.

Regards, Fernando.

fullphat / snarl

Snarl 5.0 Beta 8 Released! #52