I definitely am putting sets that haven't yet been gifted into BrickTracker, but assigning them to an alternate storage location. I can't let children browse the DB, because they will likely have a surprise spoiled (or accidentally change data), but it would be useful if they could use BrickTracker to browse sets and open up the downloaded instructions on their own.
If the app (on an alternate port) could be configured as read-only (or an allow list for editable tags like "assembled"), and have an allow list for visible storage locations, that would tremendously useful. A full on auth/account system would be overkill for this usage in my opinion.
I definitely am putting sets that haven't yet been gifted into BrickTracker, but assigning them to an alternate storage location. I can't let children browse the DB, because they will likely have a surprise spoiled (or accidentally change data), but it would be useful if they could use BrickTracker to browse sets and open up the downloaded instructions on their own.
If the app (on an alternate port) could be configured as read-only (or an allow list for editable tags like "assembled"), and have an allow list for visible storage locations, that would tremendously useful. A full on auth/account system would be overkill for this usage in my opinion.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I definitely am putting sets that haven't yet been gifted into BrickTracker, but assigning them to an alternate storage location. I can't let children browse the DB, because they will likely have a surprise spoiled (or accidentally change data), but it would be useful if they could use BrickTracker to browse sets and open up the downloaded instructions on their own.
If the app (on an alternate port) could be configured as read-only (or an allow list for editable tags like "assembled"), and have an allow list for visible storage locations, that would tremendously useful. A full on auth/account system would be overkill for this usage in my opinion.