like dog tags but for dolls and entities of any kind https://dolltags.pet
Find a file
2025-01-25 22:46:54 +01:00
.vscode moved to clean separated sqlx stuff and simpler structs 2025-01-19 17:07:11 +01:00
assets full account deletion done 2025-01-25 18:40:26 +01:00
migrations added base account changes 2025-01-25 19:39:44 +01:00
src page edition done 2025-01-25 22:46:54 +01:00
templates page edition done 2025-01-25 22:46:54 +01:00
.editorconfig woof 2025-01-09 02:21:17 +01:00
.env damn migrating to pgsql was fast here 2025-01-24 16:24:49 +01:00
.gitignore damn migrating to pgsql was fast here 2025-01-24 16:24:49 +01:00
.rustfmt.toml woof 2025-01-09 02:21:17 +01:00
build.rs added migrations 2025-01-23 22:32:47 +01:00
Cargo.lock data export implemented 2025-01-25 18:53:15 +01:00
Cargo.toml data export implemented 2025-01-25 18:53:15 +01:00
LICENSE woof 2025-01-09 02:21:17 +01:00
README.md data export implemented 2025-01-25 18:53:15 +01:00
Rocket.toml damn migrating to pgsql was fast here 2025-01-24 16:24:49 +01:00
shell.nix damn migrating to pgsql was fast here 2025-01-24 16:24:49 +01:00

dolltags

like dog tags but for dolls and entities of all kinds.

a db for registering dolls and their handlers, dog tags style.

profiles are ID'd using a 6-digit ID for manual input (maybe something else if i can manage to make use of RFID tags) and searched with that ID, nothing else.

a profile is

  • name
  • pronouns
  • kind of entity
  • handler name and contact
  • doll type
  • breed
  • behaviour
  • microchipped
  • and whatever else i think of

TODOs

  • privacy policy and GDPR notice
  • p2: saving register form as it gets filled / re-display it with partial values
  • account
    • p2: optional email for forgotten password i guess
    • deleting a tag keeping the account allows to re-use the tag later on. no one else can use it still