Load template externally #11

New Issue

FWDekker · 2021-04-14T18:51:20+02:00

FWDekker commented

2021-04-14 18:51:20 +02:00

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.

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.

FWDekker added the

tooling

label 2021-04-14 18:51:20 +02:00

FWDekker self-assigned this 2021-04-14 18:51:20 +02:00

FWDekker commented

2021-04-15 23:17:32 +02:00

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.

FWDekker closed this issue

2021-04-15 23:17:33 +02:00

Sign in to join this conversation.