Force the compose script to exit if the checkout path is wrong

[jctanner]

Description 🛠

entrypoint.sh makes assumptions about the checkout path inside the volume mounts. If the underlying host galaxy_ng checkout is not named "galaxy_ng" (galaxy_ng.foobar for example) but you also have a folder named "galaxy_ng", the script will not use the galaxy_ng.foobar folder for pip installs. That makes it seem like your code edits aren't being reflected inside the containers and it's not very obvious why.

Reviewer Checklists 👀

Developer reviewer:

• Code looks sound, good architectural decisions, no code smells
• There is a Jira issue associated (note that "No-Issue" should be rarely used)
• Tests are included in galaxy_ng/tests/integration or galaxy_ng/tests/functional, and they fully cover necessary test scenarios… or tests not needed

QE reviewer (exceptions):

• Tests are included in galaxy_ng/tests/integration or galaxy_ng/tests/functional, and they fully cover necessary test scenarios… or tests not needed
• PR meets applicable Acceptance Criteria for associated Jira issue

Note: when merging, include the Jira issue link in the squashed commit

[netlify]

✅ Deploy Preview for galaxyng ready!

Name	Link
🔨 Latest commit	a3a5b50
🔍 Latest deploy log	https://app.netlify.com/sites/galaxyng/deploys/625597bafe5b700008d6ba92
😎 Deploy Preview	https://deploy-preview-1208--galaxyng.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[himdel]

What are the unintended behaviours? (description)

I'm using galaxy_ng for master, and galaxy_ng-4.2 through galaxy_ng-4.4 for dealing with the stable versions. (I guess I won't anymore :))

EDIT: plugin-template generation seems to write to galaxy_ng-4.3 just fine .. but reads jinja templates from galaxy_ng regardless.

[awcrosby]

https://ci.int.devshift.net/job/ansible-galaxy_ng-pr-check/687/ has passed, so all CI jobs passing