Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Could you give us a brief overview of the use of AI in the production of Storyden? Like which components are ai-assisted, and to what degree?
I think this is the main sticking point people have with the project, especially since it is apparently in use but it’s not super clear how.
sure, so I use a ton of codegen and hand-write the openapi schema, jsonschemas and database model, I use AI often to write the mapping/binding boilerplate that goes between the outside-to-inside world (database stuff to queriers/writers and http handlers to actual logic) then I write the logic itself as well as the end-to-end tests. I find language models work very well once you have a clear set of constraints/boundaries such as a clear api contract + generated types or a set of tests that define the behaviour. I use a mix of claude and codex. Claude I find works well for exploratory/experimental work (a ton of the new plugin system was R&D so claude helped set up and tear down a bunch of potential implementations and ideas) codex is a lot less interactive and doesn't seem to play well with creative r&d style exploratory workflows, so I use that one more for well planned out features using the codegen mentioned before.
while I somewhat understand the "sticking point" it allows me to work faster and focus on the more enjoyable side of the craft i've honed for almost 20 years. While it's still not a super popular project and a couple of friends sometimes help, it's just me doing it so the AI helps a lot when I only have a couple of hours a night to work on it!
outside of pure code, I used a combination of very early generative imagery models (circa 2022 I think) for the hero art, which started life as a sketch, scanned in, with some iterations on Dall-E (back when it was an app before chatgpt absorbed it) and a few hours painting and expanding in photoshop with my wacom. for future art on blog posts and such, I'm keen to commission a human artist for future marketing assets (in case you know anyone!)
and I think finally, lots of exploratory discussion with chatgpt on api design, http semantics, cross-browser cookie behaviours, boring stuff like that... very useful!
do you think it would be worth including some blurb about how ai tools are used in the readme for this kinda crowd who are understandably skeptical of many open source projects now due to irresponsible usage of ai?