v1.2.4

Full Changelog: v1.2.3...v1.2.4

1.2.3 Multi-platform Containers

This release only includes changes to the build actions to include builds for arm64 and arm/v/7.

v1.2.2

What's Changed

• Input fixes by @nwesterhausen in #65

Full Changelog: v1.2.1...v1.2.2

1.2.1 Bug fix

Fixes

• change SMTP port when editing in the web UI

1.2.0 Editable SMTP settings and Dashboard Only mode

Fixes an issue where SMTP settings would not save if entered in the web UI.

Adds a configuration option to disable configuration via the web UI (or API). It is configured by default to allow configuration editing in the web UI (which matches current behavior). But by setting the showConfiguration in the app section to false (and restarting the server) will completely disable any editing of configuration in the web UI. This includes:

Editing any configuration values
Adding, updating, or removing domains
Reading SMTP configuration
Reading the admin email for alerts

This should cover all instances of info that you wouldn't want leaking; of course, all the domains on the dashboard are visible with the data included there. This is more to lock the configuration and not allow any visitor to change settings or read sensitive settings.

Full Changelog: v1.1.0...v1.2.0

Domain Expiration Alerts

Adds domain expiration alert scheduler functionality (#41) and fixes a WHOIS cache miss breaking the dashboard (#59)

If you missed it, check out the v1.0.0 release notes

Full Changelog: v1.0.0...v1.1.0

v1.0.0

New release finally. The project has been re-written from nodejs to go, since I thought for the purpose of running the server golang was better suited to handling what this project wants to accomplish. As it is with this 1.0.0 release, all the same functionality is pulled over, with the addition of being able to test the SMTP settings and set a from address and from name.

The same format is used for the domains configuration file, but WHOIS records are stored in a single file now, and since they are generated by a different library than before, I do not plan to support porting them over. It will just re-make the WHOIS lookups to fill it out after running the first time.

There's only a single data/configuration directory now, with the three files (app config, domain config, and WHOIS data).

I've been keeping the beta tag for the container images up to date, although I'm having trouble getting it to update the ghcr.io image reliably. Later today, a 1.0.0 will be released. Also note that the ghcr.io container path is changing with this update (and did with the beta). The docker hub image remains under the same name, domain-monitor and the change on ghcr.io brings the name here in line with that (from domain-monitor/server to domain-monitor).

Also soon to come is a brief improvement to the scheduler so it will take care of all the automated tasks on the same 6 hour time period. That will easily cover any of the recurring checks for domain expiration and refresh WHOIS responsibly according to the schedule laid out in the README.

What's Changed

• rewrite from nodejs to go by @nwesterhausen in #53

Full Changelog: v0.1.0...v1.0.0

Usable Release v0.1.0

The entire system works.. but still has short comings.

What's working:

• add / remove domains to monitor
• set whois monitoring per domain
• whois lookups and long-term caching
• webapp displays domains and cached whois data
• webapp can be used to configure monitoring (domains, who gets alerts)

There's a docker container via github packages that can be used to run the entire thing using docker.