Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

needs special handling when installing to ROOT (under Tomcat)

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
devops

Research direction

Start by locating the deployment code that reads webapp_path and creates or extracts the .war file. Reproduce the configuration with webapp_path set to /var/lib/tomcat7/webapps/ROOT, then verify that the WAR contents are extracted into ROOT rather than leaving a renamed WAR file there; also consider the ROOT.war scenario described in the issue.

Written by the indexing model from the issue text.

Description

KPM

... or a control parameter whether to extract the .war

killbill:
  version: 0.12.1
  webapp_path: /var/lib/tomcat7/webapps/ROOT
  plugins_dir: /var/tmp/bundles

simply created a killbill-xxx.war file under the ROOT directory (which is no a valid / deployment) instead of extracting the .war content there ... scenarios where the .war is renamed would likely be also interesting on some servers (have not tried) e.g. /var/lib/tomcat7/webapps/ROOT.war

Dominant language
Ruby
Stars
68
Forks
94
Avg merge
5d 2h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from killbill/killbill-cloud

All issues in killbill/killbill-cloud

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.