morethanevil

u/morethanevil@lemmy.fedifriends.social
31 posts · 287 comments

Recent posts

Recent comments

on hosting forgejo publicly · c/selfhosted · 4 pts · 180d

You can use Forgejo with OIDC or normal login behind a reverse proxy. If you want to make a repo public, you need to add this to your App.ini under the [service] section: REQUIRE_SIGNIN_VIEW = false

Example:

[service]
REGISTER_EMAIL_CONFIRM = true
ENABLE_INTERNAL_SIGNIN = false
ENABLE_NOTIFY_MAIL = true
DISABLE_REGISTRATION = false
ALLOW_ONLY_EXTERNAL_REGISTRATION = true
ENABLE_CAPTCHA = false
REQUIRE_SIGNIN_VIEW = true
DEFAULT_KEEP_EMAIL_PRIVATE = false
DEFAULT_ALLOW_CREATE_ORGANIZATION = true
DEFAULT_ENABLE_TIMETRACKING = true
NO_REPLY_ADDRESS = noreply.localhost
REQUIRE_SIGNIN_VIEW = false

Then you can create a public repo which people can view without an account. You can change visibilty at any time

I tried it a few versions ago, but why could I not configure the agents via the web UI? Why a editing manually a json or toml per database? Is this possible now? Connect the agent one time with the dashboard and do the rest via UI? This is a feature I really want

Here is the most used fork for anyone intrested and a few thoughts on other tools:

I tried the mentioned Whats up docker and Diun (docker image notifier), but was not satisfied with both.

Nowadays I use Komodo, it uses basicly docker compose with a very nice web UI and it can do autopolling, notification or auto update itself. It is a very powerful tool and even replaces Portainer.

on PieFed 1.3 is released · c/fediverse · 6 pts · 319d

I see your efforts in the last months. My test failed about 5 months ago, but I will give it another try with the bare metal setup in future.

Piefed is actually the only serious alternative to Lemmy in my opinion. Hope you find help with the container, it is the most used way to selfhost these days, wish you the best :)

on PieFed 1.3 is released · c/fediverse · 10 pts · 319d

Tried to setup it once bare metal, everything prepared, but only got an error on db init.. flask db upgrade worked but flask init-db only threw cryptic errors...

The docs on join.piefed.social are very limited, they should refer to those on Codeberg. Codeberg docs were completely missing how to setup S3 storage. I just took a look, now it is in the docs. This is good 👍🏻

While I set up piefed, you read in the middle of the docs, that you need a second project for notifications at the time I tried to set this up.

Now you don't need it anymore, as far as I read in the docs.

"Okay just use Docker..."

Multiple cronjobs for containers? Come on 😐 Lemmy is far easier to use in a container.

Maybe a take look at piefed again when there is a background manager instead of 4 cronjobs.