After pulling everything together, I thought it would be a good idea to document what ended up working for me with the following setup:
This stack requires the following
Folder structure:
/services
/authelia
docker-compose_authelia.yml # (Includes example service with auth)
/caddy
docker-compose_caddy.yml
Dockerfile # Needed to add the CaddyDockerProxy extension
Caddyfile # Needed to contain common configuration
| #===================================================================== | |
| # Log&Report - Security Events - Web Filter, filter a specific URL. v7.2.3 | |
| #launch CLI from fortigate GUI | |
| config webfilter profile #Configure Web filter profiles | |
| get #list all profiles | |
| edit profile-name | |
| show # see current setting | |
| set log-all-url enable | |
| set extended-log enable |
This document tries to give a description of the .mxtsession files used in the proprietary software MobaXterm. Sadly this format, as efficient as it is, is too obscure to encourage legitimate use cases of this format as there is no public documentation available.
The software licence of MobaXterm, for both Home and Pro editions, allows to "observe, study or test the functioning of the Software in order to determine the ideas and principles which are the basis of the Software, when performing the loading, display, execution, transmission or storage of the Software" and this study has been done in full under those terms.
The studied format is the one of version 23.6: sessions last modified (but not necessarily exported) before this version will have fewer fields.
| #!/usr/bin/env ruby | |
| emails = {} | |
| email_length = 0 | |
| last_email_from = nil | |
| File.open(ARGV[0], "r:ASCII-8BIT").each_line do |line| | |
| if line.start_with?('From ') | |
| unless last_email_from.nil? | |
| emails[last_email_from] ||= 0 |
Out of the box, my SMB performance on macOS 12.3.1 would top out at around 20MB/s in short ~5 second bursts, which was absolutely horrendous, slow to navigate in Finder and slugish to interact with.
Since making these changes, I now get sustained ~80-100MB/s+ and instant Finder navigation which is superb and how things should be out-of-the-box (OOTB)!
May 2023 update: As of Ventura, the SMB issues were just horribly inconsistent and hard to maintain. Something in the combination of Unraid, macOS and SMB just doesn't play nice. I ended up binning NFS/SMB all together and heading to a locally hosted Nextcloud instance for file syncing, then using SFTP/Ansible Git flow for editing files within appdata.
| UEsDBBQAAAAIABNQjFGCf/GfLgAAACwAAAAHAAAAUHJvLmtleTMqdncpCXQOKDAp9woMzEo1MTVOrHAzTjTLME7VNs1LK8owTjQpcU8tcuLlAgBQSwECFAAUAAAACAATUIxRgn/xny4AAAAsAAAABwAAAAAAAAAAAAAAAAAAAAAAUHJvLmtleVBLBQYAAAAAAQABADUAAABTAAAAAAA= |
| def init(id, cfg): | |
| return True | |
| def deinit(id): | |
| return True | |
| def inform_super(id, qstate, superqstate, qdata): | |
| return True | |
| domains = [ |
| ### | |
| # Feel free to use if it helps. | |
| # Forked from all over the place. | |
| ### | |
| ############################################################################### | |
| # INPUT PLUGINS # | |
| ############################################################################### | |
| ## ------------------------------------------- ## |
You'd like a docker container that runs cron jobs, with the output of those cron jobs going to stdout so they are accessible as docker logs. How do you do that?
In your Dockerfile, apt-get -y install cron Use apk or whatever if you are running on alpine or another distribution
Set the command or entrypoint in your Dockerfile to run cron 9n the foreground
ENTRYPOINT ["/usr/sbin/cron", "-f"]