Please update your docs. Devs like me still have to scour through the internet to find how to correctly format for example the date. Good docs can be very well incorporated into the Gemini 1.5 1 million token context window, but your docs, even though huge, still have very many shortfalls.
IIRC... ":" is for a function, such as ":put" or ":foreach" "/" is for root of command structure. " /system", "/wifi" etc. Is possibly explained better somewhere on the manual.
'/log' is a CLI command that can be called from a script, but ':log' is a separate scripting command that simply has a shorter syntax. help.mikrotik.com/docs/display/ROS/Scripting#Scripting-Commands
And I was wrong... Obviously I have yet to watch the video, will be doing so when the girls are asleep. Thanks to Mikrotik team for clearing up my error
Would be nice to have an easy way to check dates. Like say: /bla [find where ended=[/system clock get - 1d] Would save me so much in my cleanup scripts for UserMan...
dru got really comfortable with being the main YT face for MT! great progress!! always keen on your uploads. keep up the good work guys!
Thank you, great tips .
Please update your docs. Devs like me still have to scour through the internet to find how to correctly format for example the date. Good docs can be very well incorporated into the Gemini 1.5 1 million token context window, but your docs, even though huge, still have very many shortfalls.
what is difference between / and : in start of script lines? for example :log print; and /log print;
IIRC...
":" is for a function, such as ":put" or ":foreach"
"/" is for root of command structure. " /system", "/wifi" etc.
Is possibly explained better somewhere on the manual.
So for your example, ":log" is not valid... I believe.
'/log' is a CLI command that can be called from a script, but ':log' is a separate scripting command that simply has a shorter syntax. help.mikrotik.com/docs/display/ROS/Scripting#Scripting-Commands
Thank you guys
And I was wrong... Obviously I have yet to watch the video, will be doing so when the girls are asleep.
Thanks to Mikrotik team for clearing up my error
For Pt. 3... Maybe cover using script functions to do config, perhaps showing how to take some params to add a L3 VLAN network
Can you elaborate on the situation you would like to script for?
Yay nice
oh shit, a correct "allows"!
Would be nice to have an easy way to check dates.
Like say: /bla [find where ended=[/system clock get - 1d]
Would save me so much in my cleanup scripts for UserMan...
we need python to be integrated with Mikrotik
Mere mortals could not handle such power...
@@mikrotik I'll settle for bash.