Releases: beackers/myop
v1.0
v1.0! woohoo!
Heyyyyy guys! @beackers here... First ever release that's actually worth something!
This release adds a lot of new functionality and removes a lot of guessing. Prerelease was the brute force; this one works a little better. And it's my hope that every release makes this a little faster and a little better.
Without further ado, then...
individual changes
- fix security bug by @beackers in #9
- fix that dumb security problem by @beackers in #11
- login by @beackers in #10
- more login by @beackers in #12
- required by @beackers in #15
- can't change permissions of last admin to 0 by @beackers in #16
- editbulletins by @beackers in #18
Full Changelog: prerelease...v1
What's Changed (TL;DR for the changelog)
- LOGINS! The first person in can set up an administrator (or multiple) and other users.
Please do note:- If there's one admin, you can't deactivate, change the permissions of, or delete that one admin (because that's you). To remove user data (and bulletin data!), simply delete the "myop.db" file.
- To get in the first time, use the username "BOOTSTRAP_ADMIN" and password "bootstrapbill". It is highly recommended that you immediately create an admin user for yourself as the first thing you do. After logging in as the bootstrap admin, you will be taken to a page where you can do this. Set "permissions" to "admin", and fill out the other fields, then submit the new user and log in as that user. For security reasons, as soon as at least one admin user exists, the bootstrap admin is disabled.
- Bulletin control! You can now view, edit, and delete all bulletins from a table in the control panel.
- User control! You can view, edit, and delete all (with some restrictions) users from a table in the control panel.
- Bug fixes
- Optimizations
See the README for instructions on downloading and installing.
I haven't tested this on an AREDN node yet, but I'm planning on it soon. Hopefully it holds up!
As always, if you see something out of place, let me know and I'd be glad to fix it. If you have suggestions for improvements, I'd be glad to hear those too! Both belong over in the Issues tab.
Thanks guys! Hope this works well for y'all!
-- @beackers
v0.5 Prerelease / testdrive
Hiiiiii everybody! @beackers here with a prerelease.
Let me be very clear: I barely have any idea of whether this works or not. I did my testing over a LAN with a router, my phone, and a computer, and it worked. Things may be different during deployment. Stuff is going to break.
On the other hand, let me know what breaks, so I can fix it!
This release is the most basic MyOp of all the basic MyOps. It ships with
- a digital bulletin board
- a live chat with a few random options
- a control panel that currently just controls what's active
and that's literally it. No user authentication. Lots of messy code. Probably bugs waiting around every corner.
This release is, in short, in no way guranteed to work.
What I am saying is that if one of your radio operators is young and tech-savvy and likes messing with JavaScript and Python and HTML and CSS, then sure, this might be a handy tool, if he's on call to fix things when they break.
So knowing that, let's get right into this.
installing
- download the package (the links marked "source code" at the bottom)
- unzip the zip (export everything to a folder you like)
- make sure you have
Python 3and these modules:python-flask flask-socketio sqlite3 json - run app.py (on the command line, go to your folder and run
flask run) - set up MyOp as a service on your AREDN node
- get the heck out there with it!
if you find something weird
then please, please let me know. I want to hear about it, because I built the thing and I know how to "properly" operate it, and for sure it needs to be very intuitive. 1970s operators + modern tech does not equal great results (generalization sorry).
a word of warning!
I intentionally released this release BEFORE adding a login system, KNOWING I WAS GOING TO ADD A LOGIN SYSTEM. It really depends on the area you live in: do you really need an authentication system for everybody walking in? I figured AREDN web service may be a little too specialized for a would-be attacker, but someone could do it by spoofing a node. So, just so you know, the control panel is wide open and anybody can access it at any time the web server is running. No locks or anything. If you have an honor system and it works, great. Otherwise? I'd wait for the next release, which will have a login system (and possibly a configurable one).