Replies: 1 comment
|
Whatever is happening, blessings from here❤️🍻 Also thanks for your time on this! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Join the discord to stay up to date and have early previews
Changelog
Hey all, been a while 👀
Sorry for the radio silence, I was building, just silently and in the background, my productivity seriously slowed down in the past few months due to some personal stuff (some of you may have read old release notes on here and other apps), but regardless, things are a bit more stable now and I do have a bit more time!
This is a pretty major release and it should solve a lot of issues both logical and visual. It also sorts out some security concerns that were building due to dependencies getting cves and outdated node/next versions.
There are some minor/medium features and some optional hardening you can do with env vars.
Please make sure to back up your crontab files before updating as you always should and triple check everything works, cronmaster is a bit of a wild one to release as every environment tends to do cron slightly differently, so I can't predict it all even if you run this within docker.
features
/by default, add more mounts withDISK_MOUNTS, turn it off withDISABLE_DISK_STATS=true[Feature request] - Disk space and inodes #107nologin,false), falls back to/bin/shautomatically, or force a shell withEXECUTION_SHELL[feature request] Allow execution of crons for exclusive "service" user (a user with no shell) #66HOST_DATA_DIRandHOST_SCRIPTS_DIRto set the host paths yourself instead of relying ondocker inspectEnable logging set the wrong wrapper location #87 Prevent container logging paths from reaching the host crontab #109[cr*nmaster:job].LOG_LEVEL(error, warn, info, debug),LOG_FORMAT=json,NO_COLOR. Warnings show in orange, secrets are never logged. Seehowto/LOGGING.mdOIDC_USER_GROUPS/OIDC_USER_ROLES(basically same as Jotty if you use it)AUTH_MAX_LOGIN_ATTEMPTSandAUTH_LOCKOUT_MINUTESSESSION_MAX_AGE_DAYS(default 30, same as before)STRICT_EXECUTION_USER=trueto refuse running a job as root when its user can't be found on the hostFRAME_ANCESTORSto control who can embed Cr*nMaster in an iframebugfix
DELETE /api/cronjobs/[id]works, andPATCHaccepts partial updatessecurity
yarn auditis as clean as it can possibly beThis discussion was created from the release [Stable] Release 2.4.0.
All reactions