Implement BASE_URL

[JamesonRGrieve]

Scripts wich are clearly AI generated and not further revied by the Author of this PR (in terms of Coding Standards and Script Layout) may be closed without review.

✍️ Description

Implements the calling syntax export BASE_URL=https://raw.githubusercontent.com/USER/REPO/COMMIT && bash -c "$(curl -fsSL "$BASE_URL"/ct/erpnext.sh)" to allow for deployment of forked scripts without the risk of find-and-replace artifacts leaking. The variable is defaulted to the initial values where I implemented it.

Note that I only updated the necessary references for testing development scripts - for full implementation I would recommend similarly updating all references to hard-coded URLs similarly (I noticed they don't all point to the same place, some github, some mirror, etc - intentional?).

I've confirmed this method works while developing the ERPNext container - exact syntax / POSIX compliance / etc at the mercy of maintainers to maintain code standards, will update as needed but this is a HUGE quality of life improvement vs find-and-replace.

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards (as much as it can for a core update).
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

---

🔍 Code & Security Review (X in brackets)

• Follows Code_Audit.md & CONTRIBUTING.md guidelines (updated to match)
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials

[michelroegl-brunner]

Can you append that to all location where it is needed? we tried that sometime back but it always broke with the subshells. When this is cahnged and working, i will test it furhter. @JamesonRGrieve

[JamesonRGrieve]

Can you append that to all location where it is needed? we tried that sometime back but it always broke with the subshells. When this is cahnged and working, i will test it furhter. @JamesonRGrieve

It works for development of new containers as-is (I used it for the ERPNext one) - changing other ones would only be necessary for fork development of core functionality. I'm not super familiar with the core scripts so I'm hesitant to touch them but I can give it a go when I have some more time if you wish.

[michelroegl-brunner]

@MickLesk Do we want the core parts also to be done or work for the moment to allow easy development, where the core (tools.func, core.func ,... ) alsways gets pulled from our github?

[MickLesk]

Finalize Build.func, i think this week