
CM42 Central
An agile project planning tool and Pivotal Tracker drop-in replacement.
web
inloopstudio-team/cm42-central:web
Just deployed
Redis
bitnami/redis:7.2.5
Just deployed
/bitnami
Memcached
memcached:latest
Just deployed
Postgres
railwayapp-templates/postgres-ssl:16
Just deployed
/var/lib/postgresql/data
Adminer
adminer
Just deployed
worker
inloopstudio-team/cm42-central:worker
Just deployed
Deploy and Host CM42 Central on Railway
Built with ❤️ from engineers at Inloop Studio
What is CM42 Central ?
CM42 Central is an open-source, user story–based backlog management system for agile development teams. Originally forked from the now-discontinued Fulcrum project, cm42-central has evolved into a robust alternative to commercial tools like Pivotal Tracker and Trello, offering deeper features for project planning, iteration management, and team collaboration[1][2].
About Hosting CM42 Central
Hosting CM42 Central on Railway provides a scalable, modern environment for agile software project management. With Railway, you eliminate manual infrastructure setup; everything from web servers to databases and cache layers is easily provisioned within a few clicks. Deploying CM42 Central enables your team to collaborate on project backlogs, track agile iterations, analyze metrics (velocity, burn-up), and integrate with team communication channels like Slack and Mattermost without worrying about infrastructure maintenance.
Common Use Cases
- Agile story-based backlog management for software teams
- Iteration tracking and reporting (velocity, bugs, burn-up charts)
- Team-based project planning with role-based access controls
- Integration with Slack/Mattermost for story updates and notifications
- API-based chatbots or slash commands for project status queries
Dependencies for CM42 Central Hosting
- Ruby on Rails (web app backend)
- Node.js (assets/build tasks)
- PostgreSQL (relational database)
- Redis (background job processing & caching)
- Memcached (optional, caching for import/complex tasks)
- (Optional) Slack/Mattermost accounts for integrations
Deployment Dependencies
You must provide connection strings or credentials for:
- Postgres: Main database
- Redis: For job queueing and cache
- Memcached: (optional but recommended for full feature support)
Relevant links:
Implementation Details (OPTIONAL)
After cloning the project and configuring environment variables, install all Ruby and Node dependencies, then run database setup commands. Optionally, run in Docker for local development or as an all-in-one stack on Railway. More setup details can be found in the project README and .env.sample
files.
Why Deploy CM42 Central on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it. By deploying CM42 Central on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
SMTP_HOST
Host address of your SMTP email server (e.g., smtp.gmail.com)
SMTP_PORT
Port used to connect to SMTP server (e.g., 465 or 587)
MAILER_SENDER
Default "from" email address for outgoing emails
SMTP_PASSWORD
Password for SMTP email sender
SMTP_USERNAME
Username for SMTP email sender
CLOUDINARY_URL
URL for connecting to Cloudinary (image/file storage CDN)
Redis
bitnami/redis:7.2.5Memcached
memcached:latestAdminer
adminerSMTP_HOST
Host address of your SMTP email server (e.g., smtp.gmail.com)
SMTP_PORT
Port used to connect to SMTP server (e.g., 465 or 587)
MAILER_SENDER
Default "from" email address for outgoing emails
SMTP_PASSWORD
Password for SMTP email sender
SMTP_USERNAME
Username for SMTP email sender
CLOUDINARY_URL
URL for connecting to Cloudinary (image/file storage CDN)