forked from theRAPTLab/meme
-
Notifications
You must be signed in to change notification settings - Fork 1
Why Electron
Flynn Duniho edited this page May 30, 2024
·
1 revision
Deploying MEME as an Electron application addresses multiple challenges:
- Classroom/School Firewalls -- Some schools have firewalls, or we cannot login to their network, or they have whitelists or blacklists, or they use constantly changing dynamic IP addresses, etc.
- Classroom/School Routers are on different networks -- So a student logged in on one network is not able to see the server running on a different network.
- Classroom/School Bandwidth Limits -- Some schools network speed stinks.
- Classroom/School IT Department Resistance
- Security/Privacy Challenges -- The app has not been hardened to run as a public server. Student data needs to be locked down.
- Packaging Resources (PDFs) and Seeding the Database with Data for a particular study
- Easy Demos without needing to create accounts
The general practice is to bring in a complete system including:
- MEME Web Server Computer (Mac Laptop)
- Wifi Router(s)
Deploying as a server on Digital Ocean is not practical for these reasons.
User Manual
Developer Manual
Installation
Setting Up End-User Projects
Deploying
- Deploy Electron
- Electron Code Signing README-signing.md
- Digital Ocean Deployment
- Updating MEME for 2021+
--
Coding Practices
Background
Design Notes
- Dev Insights
- Design Data Management
- Student Login
- Reference Build Differences
- Design Settings Manager
- Why Electron?
Deprecated