- HTML 40.3%
- TypeScript 33.7%
- JavaScript 16.4%
- SCSS 7.3%
- Python 1.7%
- Other 0.6%
- devices: IP range scan back in Add Device (MikroTik), groups for both modes, terminal protocol sent with the single add; old scanner wizard removed - devices: Bulk Edit modal (records / apply on router, chunks of 25), trusted router identity in the MikroTik edit form, displayDevices cached so auto refresh keeps page and sort - user manager / alerts: memoised filters (page kept on refresh); Locked Logins panel and per-user unlock - executions: Warning status filter and badge - settings: Router Identity Verification, RADIUS Login Protection, Message-Authenticator switch, SSL banner text - template manager: Updates tab (status, mode/channel, check now, apply safe, per-field choices, skip, history/revert, import) - vpn: full-mode note - ssl-agent: recreate-ssl.sh keeps ports/volumes/network/restart policy, checks the port first and rolls back on failure - update package: works with every updater in the field. Updater 2.0 (old images) stopped right after unpacking: run by cron (PATH /usr/bin:/bin) it could not find nginx, and pkill is not in the image, so the SSL agent, the nginx config and its own update were never installed. Nothing it acts on is at the top level any more: nginx/default.conf, ssl-agent/ssl-agent.py and version.json are installed by post_update.sh (nginx -t with the full path, reload, rollback; agent started detached, flask check), version.json last so an update that stops early is retried; leftover top-level ssl-agent.py / nginx.conf removed. front-update.py 2.1 (isolated steps, lock, agent watchdog, /conf/logs/front-updater.log); release-front.sh builds and verifies the package; procps in the image |
||
|---|---|---|
| src | ||
| .gitignore | ||
| angular.json | ||
| build.sh | ||
| CHANGELOG.md | ||
| Dockerfile | ||
| entrypoint.sh | ||
| front-update.py | ||
| karma.conf.js | ||
| LICENSE | ||
| mwcrontab | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| post_update.sh | ||
| proxy.conf.json | ||
| proxy.conf.ts | ||
| proxy.conf2.json | ||
| README.md | ||
| release-front.sh | ||
| reqs.txt | ||
| run-docker.sh | ||
| ssl-agent.py | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
| version.json | ||
| version_generate.py | ||
MikroFront | MikroWizard Front
This is the MikroWizard Front app based angular and core-ui admin template
What is MikroWizard?
Mikrotik routers are widely used in the networking industry for their robust features and flexibility. However, managing and monitoring these routers can be a complex and time-consuming task. With MikroWizard, we aim to simplify this process and empower network administrators with a powerful yet user-friendly tool.
Features
- Router Management
- Device grouping
- Access Management
- Monitoring and Reporting
- Automation and Scripting
- Snippets ( Batch configuration )
- User Access Management
- Permission Enforcement
- Activity Monitoring for more info please check mikroman repo
License
MikroFront | MikroWizard Front
This is the MikroWizard Front app based angular and core-ui admin template
What is MikroWizard?
Mikrotik routers are widely used in the networking industry for their robust features and flexibility. However, managing and monitoring these routers can be a complex and time-consuming task. With MikroWizard, we aim to simplify this process and empower network administrators with a powerful yet user-friendly tool.
Tech Stack
Client: Angular , CoreUI admin template , Python(Updater script only)
Server: mikroman
Deployment
To deploy this project run
....