Difference between revisions of "Infrastructure"
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
* kosmos.org and chat.kosmos.org MUC (ejabberd) | * kosmos.org and chat.kosmos.org MUC (ejabberd) | ||
* bitcoind (mainnet) | * bitcoind (mainnet) | ||
− | |||
* lnd (testnet) | * lnd (testnet) | ||
* lnd (mainnet, [https://www.robtex.com/lightning/node/024cd3be18617f39cf645851e3ba63f51fc13f0bb09e3bb25e6fd4de556486d946 node info]) | * lnd (mainnet, [https://www.robtex.com/lightning/node/024cd3be18617f39cf645851e3ba63f51fc13f0bb09e3bb25e6fd4de556486d946 node info]) |
Revision as of 14:18, 8 February 2019
The Kosmos project is running some community IT infrastructure, currently sponsored by 5apps. Please ask in #kosmos-dev on Freenode if you need access, changes, info, or whatever else.
Servers
Hetzner
These are root servers run by Hetzner Online GmbH in German datacenters (using renewable energy).
dev.kosmos.org
This server is still running Ubuntu 15.04 and the plan is to decommission it soon, due to the difficulties in getting software updates for it.
Currently hosting:
- https://kosmos.social (Mastodon)
- https://wiki.kosmos.org (you're looking at it :))
- sockethub.kosmos.org (Sockethub)
- Some IRC and XMPP bots (incl. botka and hal8000 on freenode)
- ...
Most things are configured via Chef Solo, based on https://gitea.kosmos.org/kosmos/chef (repo currently not public, for security reasons)
andromeda.kosmos.org
Currently hosting:
- kosmos.org and chat.kosmos.org MUC (ejabberd)
- bitcoind (mainnet)
- lnd (testnet)
- lnd (mainnet, node info)
- c-lightning (mainnet, node info)
- ipfs.kosmos.org (IPFS node)
I have added IPFS using the Chef repo (https://gitea.kosmos.org/kosmos/chef), as well as firewall rules for what was configured manually.