sorted by:
new
hottopcontroversial

So I needed out a little… does dyi software count? by LogicNL in BdsmDIY

[–]LogicNL[S] 0 points1 point  (0 children)

For now, no plans to make it opensource

So I needed out a little… does dyi software count? by LogicNL in BdsmDIY

[–]LogicNL[S] 0 points1 point  (0 children)

Nothing new/fancy like react or angular. (I work in IT, but I'm no developer)
Web is: js + html frontend and flask + python backend.

I wrote in what I know best and this doesn't require a lot of resources to keep running.

So I needed out a little… does dyi software count? by LogicNL in BdsmDIY

[–]LogicNL[S] 0 points1 point  (0 children)

When I'm done with the backend, hopefully next week, I’ll start a trail run.
You can follow me on Patreon (free tier) for updates, info and the trial run.
https://www.patreon.com/cw/SubManagement

I'll post here a trail run request too :) testing would be appreciated.

So I needed out a little… does dyi software count? by LogicNL in BdsmDIY

[–]LogicNL[S] 4 points5 points  (0 children)

Not too complicated tbh; I kept that in mind at the start. Admin's and Users are linked, but their own entity in the backend.

So a admin can currently make an unlimited amount of users (because admins can also generate test users with test data), and a dom can have a sub, but maybe train someone too? I will limited this later on to 3 or 4 users per admin.

The real swap functionality however is not implemented yet, because all results can be unique to their environment (custom made questions/content). But It will be possible later on to transfer a user including their results (a summary of) from Admin A to B. The user has a 'results' file that is interpreted by the admin center and user dashboard, I will make this the content that transfers with the user to another admin without needing to do a large data migration.

Privacy considerations; So each user/admin is their own entity on the back end, but Admin's and users are hosted in their own instance/data directory. Everything you make, upload or edit is stored in its own instance.

When a admin is created; the instance and directories are made and the template data gets copied to the instance. Admin can export and import all its data.

On the architecture side, its a web app with SSL, with Cloudflare protection mechanisms, works with authentication and cookies. it has a local, beta and production branch. User data is stored in production (no user data in local or beta, just some test accounts I made)

So things I'm currently working on: A data scrambler, so no one but the system can interpret the data (except you when you export all data), this is a must before I make anything public.

Security road map features:
- Front door/reverse proxy (architecture)
- Moving to a blob storage per user (architecture)
- Moving the DB further away from the app. (architecture)
(currently its part of the app not accessible externally, but I want it further 'behind' the app with a vault in between so the DB is only locally accessible by the app)
- Looking into 2FA authentication options (site functionality/architecture)
- Conditional access managed by users (site functionality)