After creating the user and restarting the container it will pick up the env variables.
So u may want to update the docs that will tell users its compulsory to restart the container after creating the user, else there maybe unwanted issues.
OR , if u want to fix u can force the compose ENV variables after the user creation, It will be more work for you though.....
https://github.com/RayLabsHQ/gitea-mirror/issues/69
Just a Quick reminder it still works this way -
After creating the user and restarting the container it will pick up the env variables.
So u may want to update the docs that will tell users its compulsory to restart the container after creating the user, else there maybe unwanted issues.
OR , if u want to fix u can force the compose ENV variables after the user creation, It will be more work for you though.....
<!-- github-sync-id:3368250908 -->
@Tailscale-VPS This has been addressed in v3.5.3. Have a look and feel free to reopen the issue if it still exists.
@Tailscale-VPS This has been addressed in v3.5.3. Have a look and feel free to reopen the issue if it still exists.
<!-- github-comment-id:3263706228 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://github.com/RayLabsHQ/gitea-mirror/issues/69
Just a Quick reminder it still works this way -
After creating the user and restarting the container it will pick up the env variables.
So u may want to update the docs that will tell users its compulsory to restart the container after creating the user, else there maybe unwanted issues.
OR , if u want to fix u can force the compose ENV variables after the user creation, It will be more work for you though.....
@Tailscale-VPS This has been addressed in v3.5.3. Have a look and feel free to reopen the issue if it still exists.