Accounts

How to get and manage your F-hub.org account.

How to apply for an account?

We are currently in the process of setting up an account application procedure during this soft-launch period.

The basic procedure is to get into contact with us via our chat network (no account required for that) and explain to one of our admins why you would like to have an account.

The general Terms of Use and Privacy Policy apply for all services and hosted projects.

Generally F-hub.org is open to FOSS projects and the requirements otherwise are minimal (we require a user-name and a working email address). If you are a member of an organisation already hosted by us, please mention that in your application as it will fast-track the decision process and we can directly add you to the respective organisational group.

Once approved you will get an automated email with instructions how to set your password. If for some reason you are not receiving this e-mail or do not have a working email address, we can pre-set a random password and share it with you for one-time access to our account management web-interface.

Please note that F-hub.org aims to be a membership supported organisation and thus combining your membership with recurring donations is strongly encouraged (but not mandatory). We reserve the right to monitor your use of our system resources and might decide to terminate your account if resource-use and contributions (monetary donations or otherwise) are not in balance.

Primary LDAP accounts

The primary account backend is based on LDAP and after applying for an account all linked services will work with the same user-name and password combination.

Typically it is sufficient to use the user-name alone, but in some cases the chosen email address or the fully distingished LDAP name like user@f-hub.org will also work.

The LDAP account self-service portal can be accessed here. It allows resetting your password, changing email addresses and other such typical features. Avatars and display names can also be set, but those are not synced with all services.

We are currently working on a way to make LDAP account management also possible via our IRC channel bot.

Our administrators can also manage group membership via LDAP, which is automatically linked with organisation membership in the git-forge. If you want to set up a new organisation, please let us know so we can configure the group link accordingly.

Oauth2 provider

Our Forgejo git forge supports connecting external services via the Oauth2 provider API. This is a password-less, scoped and token-based authentication method that can be safely used with 3rd party apps.

You can access your personal Oauth2 access tokens via the Settings -> Applications menu where it is also possible to revoke access tokens. As an organisation repository owner you can also generate access tokens there.

Our internal Opengist service is directly connected via Oauth2 to your main account. But 3rd party native apps such as GitNex can also use it. You can also log into our Loomio group collaboration tool via Oauth2. If you already made a Loomio account, please make sure it uses the same email address and then it is possible to link it to your main F-hub.org account via Oauth2. 

For more details, please see the Gitea documentation.

IRC Network accounts

Our IRC networks supports registering accounts directly via NICKSERV for legacy reasons and to allow non-members to use all the features of our IRC network. Click here for a quick guide on how to register legacy IRC accounts.

You can however also use your regular F-hub.org account that is connected to our IRC server via LDAP. Simply use your regular user-name and password as the SASL account details. If you are using our The Lounge IRC web-client, you need to input this twice, once to access The Lounge itself and once in the network connection dialog as the SASL login.

If there is an conflict with an legacy IRC account, please contact us on the #support channel to have an network admin erase that nick. Deleting it via NickServ is sadly insufficient as IRC nick-names stay reserved to prevent impersonation.

Please note that IRC account names are limited to a ASCII subset and registering names with uncommon characters can result in issues with IRC clients and/or chat bridges and is therefore not recommended. If you notice any issues due to this please let us know. 

Access to hosted servers

This is currently still a work in progress and will likely require an independent account with 2FA credentials for SSH access.

Please let us know if you are interested in becoming an alpha-tester of this service.

We plan to provide some low-powered ARM64 root servers and x86 VMs.

Note that this is not professional hosting and bandwidth limits will be strictly enforced.