dhitchenor/hubzilla
A multi-arch container for Hubzilla, based on Alpine Linux, Nginx, and Postgres/MariaDB
2.0K
Hubzilla as a docker image (based on php:8.2-fpm-alpine) in a multi-arch (amd64, armv6/7, arm64) format.
Variable | Description |
---|---|
DB_TYPE | Database type: postgres or mysql |
DB_HOST | Host name of the database |
DB_PORT | Database port number, set to empty to use the default of your DB_TYPE (aka 3306 for mysql) |
DB_NAME | Database name |
DB_USER | Database user |
DB_PASSWORD | Database user password |
REQUIRE_EMAIL | Require email address to register |
REGISTER_POLICY | Allow (or disallow) new user registrations |
SMTP_HOST | Mail server hostname |
SMTP_PORT | Mail server port number |
SMTP_USER | User name for the mail server |
SMTP_DOMAIN | Mail domain |
SMTP_PASS | Password for the user on the mail server, if set empty, then no authentication on the smtp server will be used |
DOMAIN | Web domain name for hubzilla |
ADMIN_EMAIL | Administrators email of the deployed hub |
REDIS_PATH | If set (to something like " tcp://redis") then php sessions will be stored in this redis server (useful for horizontal scalability) |
LDAP_SERVER | LDAP server name (dont forget to add "ldapauth" to the ADDON_LIST) |
LDAP_ROOT_DN | LDAP username to connect to (ex: cn=admin,dc=domain,dc=com) |
LDAP_ADMIN_PASSWORD | Password for that LDAP user |
LDAP_BASE | Path to look for users in the directory (ex: ou=people,,dc=domain,dc=com) |
ADDON_LIST | Addons to install/activate during initial configuration |
1. Clone git repository to your server (or wherever you desire Hubzilla to be deployed from).
git clone https://github.com/dhitchenor/hubzilla
2. Edit nginx.conf:
domain.com
to your desired server name (eg. funnylookingfaces.com, or www.potatogram.net)hub:9000
to match the name (not, container name) of your hubzilla container in your docker-compose.yml file
3. Edit .env file
DOMAIN
value to reflect the domain name that you changed earlier, in the nginx.conf
fileDB agnostic
options to reflect your desired database credentials
DB_NAME
, DB_USER
, and DB_PASSWORD
to reflect that database; if no database is present, a database is created for you using these detailsDB_HOST
should match the name (not, container name) of the database container used for hubzilla or within the docker-compose.yml file (see screenshot)
4. Edit docker-compose.yml file
<
>
symbols, to reflect the appropriate local directories (2 in total, under volumes
)
<
>
symbols; remove them5. Ensure placement of files
6. Run docker compose
docker-compose up -d
(or docker-compose up
if you want to see the output of the deployment), and navigate to your domain (in a web browser), after deployment has finished.
docker compose up -d
or docker compose up
if you want to see the output, as before)version
level in the docker-compose.yml file is not necessary in the new version of docker compose; for backwards compatibility, it has been retaineddocker pull dhitchenor/hubzilla