Rallly

An open-source tool that simplifies scheduling and collaboration for events and meetings.

Accessing Rallly

  • Open your browser and go to: https://<SERVER-IP>/
  • Accept SSL warning (self-signed certificate).

Email (SMTP) Configuration

Ensure SMTP connections are allowed for this server (ask for enabling SMTP access).

SMTP settings are stored in: /root/rallly/config.env

To update SMTP or email settings:

  1. Edit the file: nano /root/rallly/config.env
  2. Apply changes: cd /root/rallly && docker compose up -d

Creating the Admin Account

  1. Sign up using the admin email you provided during deployment.
  2. Once logged in, open: https://<SERVER-IP>/control-panel
  3. If your email matches INITIAL_ADMIN_EMAIL, you will see a button labeled: Make me an admin
  4. Click it to become the administrator.
  5. You can manage settings and prevent new users from registering an account.

Important Files and Directories

  • Main application directory: /root/rallly
  • Application environment configuration: /root/rallly/config.env
  • Docker Compose configuration: /root/rallly/docker-compose.yml
  • PostgreSQL persistent data: /var/lib/docker/volumes/rallly_db-data
  • Nginx configuration: /etc/nginx/sites-available/rallly.conf
  • SSL certificates: /etc/nginx/ssl/

Managing the Service

Check container status:

docker compose -f /root/rallly/docker-compose.yml ps

Restart Rallly:

docker compose -f /root/rallly/docker-compose.yml restart

View logs:

docker compose -f /root/rallly/docker-compose.yml logs -f

Enabling SSL with a Domain

1. Point your domain to the server IP.

2. Edit the /root/rallly/config.env file to set your domain name: NEXT_PUBLIC_BASE_URL=https://your.domain.com

3. Recreate the services:

cd /root/rallly/
docker compose up -d

4. Edit Nginx config and replace both server_name <IP>; with your domain (<your-domain>) for both HTTP (port 80) and HTTPS (port 443) blocks:

vim /etc/nginx/sites-available/rallly.conf

5. Install Certbot:

apt install -y certbot python3-certbot-nginx

6. Run the following command to generate a valid Let’s Encrypt certificate:

certbot certonly --nginx --non-interactive --agree-tos --email [email protected] -d yourdomain.com

7. Replace SSL paths in Nginx config (TLS section):

vim /etc/nginx/sites-available/rallly.conf
# Before:
    # ssl_certificate /etc/nginx/ssl/fullchain.pem;
    # ssl_certificate_key /etc/nginx/ssl/privkey.pem;
# After:
    # ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    # ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

8. Restart Nginx to apply the changes:

systemctl restart nginx

9. Open your browser and visit: https://yourdomain.com

Application Details