greeneyestyle

Good, glad to hear it helped!

Yes, there’s auth/multi user support. You just need to enable it with the ENABLE_AUTH=true environment variable. It’s documented in the readme configuration section and also in the docker compose example in the readme.

I can help with that. But first a little fyi on containers to get you up to speed.

A docker container is like a mini computer, but where its life depends on one single computer program being alive and running. So if the container is running based on the command from the readme, then you should be able to access the web ui via localhost:3000

You’re very welcome. Please let us know how you like it!

Pacific Northwest (Seattle)

I appreciate the feedback.

No this is a fair question. I think I’ll add this to our sites about page as people seem to want to know.

I’ll also paste a couple paragraphs disclaimers I added to another reddit r/selfhosted post just to save my thumbs while typing this from my iPhone. Please feel free to ask any follow on questions though.

“I built this project on top of a project boilerplate I made almost entirely by hand. I have used copilot to speed up development of this application on top of the boilerplate I made. So everything is built the way I want it, on top of my own architecture, technology, and design decisions. Check out my GitHub here if you’re interested. github.com/gianlazz/“

“The features and quality improvements have been made with considerable time, engineering, and intention. While ShoshannaTM, Leolazz, and I are using copilot to accelerate development, substantial upfront deliberate design was done on our part before any feature development. Additionally, nothing is taken without thorough iteration and human review. We are professional software engineers. This project is not vibe coded. It is engineered and we take much pride in our craft and the quality of our work.”

That’s a really good suggestion, thank you for your support 🙏

ShoshannaTM laughed at this and said:

“Ask partner out on date, and check their wardrobe to suggest an outfit for the outing”

😂

At this point we don’t have a concrete plan, but for the sustainability of the project I would like to monetize it eventually.

As of now we do have a ko-fi donation page set up and linked in the repo though.

What I do know for sure though is that it’s important to me that the selfhosted deployments always be maintained as full featured as possible. I’m a selfhoster myself and have been doing so for many years. I’ve thought a lot about this subject and really don’t want to f it up.

I really like the Bitwarden, Immich, or ghost blog model. “Want to use our convenient cloud hosted instance? Toss us a few bucks a year to support development. Otherwise selfhost it and you’ll still get the same full experience… it just might take a bit of work.”

I’m entertaining some kind of paid plan for professional stylists on the public cloud instance.

The selfhoster will always be our core audience though. It takes actual effort to selfhost and invest in open source, so those who do so will remain first and foremost. And ideally this good will may result in positive recommendations for our cloud offerings down the road to those less inclined to self host.