prosody
30a91d819913
tools/build-env/Containerfile

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody

File

tools/build-env/Containerfile @ 13665:30a91d819913 13.0

mod_account_activity: Record an account's last activity timestamp This is similar to mod_lastlog/mod_lastlog2. Some functionality was dropped, compared to mod_lastlog2. These features (recording the IP address, or tracking the timestamp of multiple events) are handled better by the mod_audit family of modules. For example, those correctly handle multiple logins, IP address truncation, and data retention policies. The "registered" timestamp from mod_lastlog2 was also dropped, as this has been stored in account_details by Prosody itself since at least 0.12 already.
author Matthew Wild <mwild1@gmail.com>
date Wed, 12 Feb 2025 12:33:45 +0000
parent 13323:7bfd6db52528
line wrap: on
line source

ARG os
ARG dist
FROM ${os:-debian}:${dist:-sid}
ENV DEBIAN_FRONTEND noninteractive
RUN set -ex; \
	apt-get update; \
	apt-get install -y --no-install-recommends \
	ccache dh-lua libicu-dev libidn11-dev libssl-dev \
	lua-bitop lua-dbi-mysql lua-dbi-postgresql lua-dbi-sqlite3 \
	lua-event lua-expat lua-filesystem lua-ldap lua-sec lua-socket \
	luarocks shellcheck mercurial; \
	apt-get install -y ca-certificates dns-root-data; \
	apt-get install -y lua-bit32 || true; \
	apt-get install -y lua-busted || true; \
	apt-get install -y lua-check || true; \
	apt-get install -y lua-readline || true; \
	apt-get install -y lua-unbound || true; \
	update-alternatives --set lua-interpreter /usr/bin/lua5.4 || true \
	apt-get clean

# Place this file in an empty directory and build the image with
# podman build . -t prosody.im/build-env
#
# Substituting podman for docker should work, where that is what's available.
#
# Then in a source directory, run:
# podman run -it --rm -v "$PWD:$PWD" -w "$PWD" --entrypoint /bin/bash \
#            --userns=keep-id --network host prosody.im/build-env
#
# In the resulting environment everything required to compile and run prosody
# is available, so e.g. `./configure; make; ./prosody` should Just Work!