# Self-host ActiveMQ Classic

> A message broker with JMS, AMQP and MQTT support and a web console, with a data volume. The console login is admin with the password admin, so change it right after the first sign in.

- Page: https://levelrail.com/templates/activemq/
- JSON: https://levelrail.com/templates/activemq.json
- Category: Infrastructure
- Licence: Apache-2.0 (Permissive license)
- Source: https://github.com/apache/activemq
- Upstream docs: https://activemq.apache.org/components/classic/documentation

## Requirements
- Memory: about 512 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 6.1.4

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| activemq | apache/activemq-classic | 6.1.4 | 8161, 61616 | activemq_data -> /opt/apache-activemq/data |

## Deploy

### CLI

```bash
levelrail-cli templates deploy activemq --name my-activemq
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/activemq/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## First run
1. Sign in to the console as admin with the password admin and change it, because it is public knowledge. Connect clients at activemq:61616.

## Questions

### Can I deploy ActiveMQ Classic on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for ActiveMQ Classic, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image apache/activemq-classic:6.1.4 is what you deploy there.

Self-host ActiveMQ Classic, ActiveMQ Classic docker compose file, deploy ActiveMQ Classic on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
