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.
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
If you're self hosting, the email service only needs to be accessible to those services. Set up a postfix container if you don't want these messages going out.
You can read them locally, or configure postfix to forward them to some other host if you desire.
I'm starting to wonder if a mailpit instance is a bad idea. Just a page you go to where any email goes, make sure it's not externally accessible.
Ooh, that's a useful thing to know about! Thanks!
Was about to add that very idea, maybe I should write a compos file with postfix setup
I don't want email to be accessible to those services. I don't want those services to use email at all.
Then you're free to patch it out.
Why do you assume everyone you interact with is a software developer?
I don't think that assumption was inherent in the comment
If you want an unpopular feature that doesn't exist on an open source platform sometimes your only options are to code it, or ask someone else to. The skillset of the feature requester doesn't change that
I wasn't asking for options, I was asking for an explanation.
In your OP, sure.
But this comment reads as a desired state, and in some situations thats a feature request (in this case it seems like there are architecture / system workarounds):
Did you get an explanation you're happy with?
To be fair, you are on a Self-hosting community but maybe read up the wiki or file the issue to suggest an option to make it not required on their git repo? 🤷
Otherwise, I'm not sure what else are we suppose to say
I wasn't asking for advice, I was asking for an explanation.
You should probably ask the developers then. But the answer is probably to support things like password resets in environments with multiple users. It's less development effort to implement it this way than to maintain multiple code paths with varying levels of account management.
...which ones?
https://github.com/TryGhost/Ghost
This is the repo (unless I have the wrong software).
However, it seems they’re running a business, which means revenue generating features will probably be prioritized. They’re not running a charity.
I’m sure if you donate enough money you can probably get them to implement better self hosting functionality. Chances are the email requirement is just what they have for other features.
Ghost is just one piece of selfhosted software. But I have inquired and they have declined.
They are, actually. They're a registered non-profit.
More unnecessary functionality.
What was their reason for declining?
I see they’re a non profit business. That doesn’t make them a charity. They have paying customers.