#Forge Steel - Warehouse

34 messages · Page 1 of 1 (latest)

restive cove
#

Hello everyone,

I've created a data storage backend that integrates with the fantastic Forge Steel by Andy Aiken - the Warehouse!

It's a container that you can run yourself so your Forge Steel data is persisted outside just your browser.

You can find the source code and instructions for running it here: https://github.com/Veritas1000/forgesteel-warehouse

Important notes: for this early version, you've got to run and host it yourself, so you should have an understanding of what that entails before proceeding.

However, at some point in the future I want to provide a much more accessible process for the wider audience to be able to use this, but that's not ready yet.

Also, right now I'm considering this an early beta before a wider release, so you'll need a code to enter in to Forge Steel to enable the settings to be able to connect the warehouse up. If you are interested in trying out the self-hosted warehouse, just drop a message in here and I'll make sure you get the feature code. The code is now in the usage instructions on GitHub

Forge Steel

Heroes, monsters, encounters ... everything you need for Draw Steel.

GitHub
GitHub - Veritas1000/forgesteel-warehouse

Contribute to Veritas1000/forgesteel-warehouse development by creating an account on GitHub.

glass ore
#

This is awesome 🙂

#

I'd reccomend for the future wider audience version that it may be easier to use OAuth instead of trying to manage your own users+passwords. Takes some of the security burden off your shoulders

#

I mean, I guess super longterm having your own user pool may be useful/desired. But meh.

#

Though, I think stuff like AWS simplifies all that user stuff nowdays anyways. I think Cognito can handle it all now basically for you.

restive cove
#

Yup - this first version is just a self-hosted thing, really meant to be just one user (so implementing a whole oauth provider seemed...a bit much). However... Integration with OAuth is on the roadmap for sure

pale plinth
#

Hi! I self host so much stuff, I can definitely help with this! I'll install it this weekend and let you know if I run into any hiccups!

#

Amazing work on this, can't thank you enough!!

restive cove
#

Hopefully there won't be too many of these, but as this moves beyond the 'proof of concept' phase to 'real thing that is more or less robust' I will inevitably find where I have made mistakes.
All that to say - as you're working with this, be aware there will likely be early bugs

pale plinth
#

Totally expected, I'll treat as a pre alpha and just test it like a regular Quality Tester

#

Breaking db migrations are totally fine with me

#

Do whatever you need to do, I'm just happy to contribute to assisting this

restive cove
#

unless you've somehow already setup without the feature flag code, you'll miss this one since I've already pushed the fixed version blobcheeky . And now i've got an int test that checks the upgrade path for obvious issues

pale plinth
#

Hahah it's fine I've not set it up yet!

sharp jay
#

Hi one of my players is a coder and has been doing something similar. He asked me to ask you for the feature flag code. I am not a programmer and don't know what that means

restive cove
#

I'm looking to add a few more beta testers - if you're willing to help test out the Warehouse (no hosting or technical knowhow required on your end!) drop a message here or DM me

vague holly
#

I'd love to help test if you are still looking for testers

restive cove
#

instructions sent

wintry grove
#

I sent a friend request and a dm, but I have it running on my Nas already. What does being a beta tester entail?

restive cove
#

You'd get an API key for my hosted instance. If you've already got it running yourself I don't know that it would get you too much more?

wintry grove
#

I followed your instructions on your github for getting it working on https://andyaiken.github.io/
I had been just serving it locally because of that mix-content error. I thought it worth mentioning that I needed to do one more step to get it working consistently without needing to do a hard refresh every time: chrome dev tools > application > service workers > check bypass for network

image.png
#

still even then though, i need to have dev tools open when i refresh

restive cove
#

yeah, that's still pretty annoying - I'll try and see if there's more I can do to resolve that - but with browser security being increasingly locked down (not a bad thing!) there's only so much you can do

wintry grove
#

right on. i'll also look into it a bit and let you know if i find anything. thanks btw, warehouse is awesome ❤️

#

just spitballing, but could you maybe update connection settings with a bool for disable service worker, add a toggle in get warehouse settings, and then in index don't register the service worker if that setting is flipped? i'm not super familiar with the forge steel code base, i was just poking around.

restive cove
#

I've actually been thinking there probably should be some top-level logic to disable the service worker when there's a remote data store in use

#

so yeah, I'll look into adding that

wintry grove
#

sweet! thanks! i can also look into it and suggest a pr. i've been thinking about contributing lately.

wintry grove
#

i also don't know if that's how you'd want to do it either. or if i missed something entirely 😅

covert cove
#

Just wanted to say that I've spun it up on my cluster, does exactly what it says on the tin. Now I'm wondering if I should get my players to use it

sharp latch
#

I got mine set up on my TrueNAS server as well--working like a charm!

I am going to get my players to use it during sessions, but I'm wondering if there's a way to have stamina updated when a session/encounter is live. The only way I can see right now to get the updates from another client is to remove the hero and add them again.

#

Thanks @restive cove for the work on this!