Git over SSH access to Lokinet Gitea (https://lokilocker.com) has been non-functional since at least April 25, 2023.
While Lokinet Gitea did go down for maintenance and update its UI shortly thereafter, fixing issues with broken links, this issue remains as a crucial roadblock to further development.
Recreate pull requests and issues on the main repository, if not migrated.
Push my local edits to fork.
Remove both Lokinet Gitea repositories.
Set up both Lokinet Gitea repositories as mirrors.
Git over SSH access to Lokinet Gitea (https://lokilocker.com) has been non-functional since at least April 25, 2023.
While Lokinet Gitea did go down for maintenance and update its UI shortly thereafter, fixing issues with broken links, this issue remains as a crucial roadblock to further development.
I've already set up a Codeberg account (at <https://codeberg.org/gravel/>), and so has @SomeGuy (at <https://codeberg.org/mdPlusPlus/>).
Further steps to follow:
1. Migrate main repository to <https://codeberg.org/mdPlusPlus/sessioncommunities.online/>.
1. Create my fork at <https://codeberg.org/gravel/sessioncommunities.online/>.
1. Recreate pull requests and issues on the main repository, if not migrated.
1. Push my local edits to fork.
1. Remove both Lokinet Gitea repositories.
1. Set up both Lokinet Gitea repositories as mirrors.
This repo is archived. You cannot comment on issues.
Git over SSH access to Lokinet Gitea (https://lokilocker.com) has been non-functional since at least April 25, 2023.
While Lokinet Gitea did go down for maintenance and update its UI shortly thereafter, fixing issues with broken links, this issue remains as a crucial roadblock to further development.
I've already set up a Codeberg account (at https://codeberg.org/gravel/), and so has @SomeGuy (at https://codeberg.org/mdPlusPlus/).
Further steps to follow: