Load template externally #11
You know what absolutely sucks? The fact that whenever I update this template and fix a critical bug, I then have to re-deploy all my other tools. What I should do instead is make the tools load it from static or api, and then request the latest version of the major version. That way, when I do a breaking change, I have to update the applications manually, but I should just prevent that from happening by making a good API, duh.
Anyway, the tools just include the latest version given the major version, and then I'm happy.
Done! They are now hosted on static.fwdekker.com. Deployment automatically puts it in the right directory so that "v1.x.x" always refers to the latest patch of that major version, so other parts of the website can simply import that one and fixes will apply automatically. Same goes for CSS. Files are pretty small so no need to worry about having a lot of folders for outdated versions.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?