147 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
mifi	61236719f4	Or this...	2023-05-06 09:55:09 -04:00
mifi	aa699d5009	Testing this...	2023-05-06 09:48:31 -04:00
mifi	9a4f9cdf4c	Hmmm	2023-05-06 09:48:00 -04:00
mifi	5532fc51a9	Unbroken?	2023-05-06 09:45:05 -04:00
mifi	99db648a36	- Endlessly fighting the ENV - I should be loading from the package... 0.0.34	2023-05-06 09:40:25 -04:00
mifi	adcab6afcb	Double dollar 0.0.33	2023-05-06 09:28:24 -04:00
mifi	8e40c0a06c	Tweaking the ENV 0.0.32	2023-05-06 09:19:31 -04:00
mifi	db5e4858b8	More ENV updates 0.0.31	2023-05-06 09:10:45 -04:00
mifi	d800311ae7	- ENV updates 0.0.30	2023-05-06 09:08:15 -04:00
mifi	32fdde5d90	- The missing env variables... 0.0.29	2023-05-06 08:43:26 -04:00
mifi	2eacdaeece	Tweaks 0.0.28	2023-05-06 01:38:00 -04:00
mifi	827bce6e1b	Updates for staging 0.0.27	2023-05-06 01:15:11 -04:00
mifi	50c74fdb71	I think it is working now... 0.0.26	2023-05-06 00:48:27 -04:00
mifi	42f091489e	Who knows what happens next... 0.0.25	2023-05-05 18:14:20 -04:00
mifi	995dd9a015	A whole new world... 0.0.24	2023-05-05 11:22:26 -04:00
mifi	5b0c9ba72d	Escape the interpolation 0.0.23	2023-05-05 11:14:31 -04:00
mifi	d745869cc0	Last bits to make it whole again... 0.0.22	2023-05-05 11:10:13 -04:00
mifi	e6389d8b9b	More tweaks... 0.0.21	2023-05-05 11:05:18 -04:00
mifi	47f1bdf485	More path fixes... 0.0.20	2023-05-05 10:56:33 -04:00
mifi	bc96664b7c	Path fixes ... and the dumbest environment error yet... 0.0.19	2023-05-05 10:53:42 -04:00
mifi	04ec6e2de3	Hmmmm 0.0.18	2023-05-05 10:42:22 -04:00
mifi	ba31f4b8be	More changes 0.0.17	2023-05-05 10:01:42 -04:00
mifi	d5f9bc4d05	fix bad commands 0.0.16	2023-05-05 09:20:14 -04:00
mifi	ad9ffc89b5	With links and fixed names... 0.0.15	2023-05-05 09:09:06 -04:00
mifi	f482750d08	this may break everything... 0.0.14	2023-05-05 08:47:54 -04:00
mifi	7b77df0c4c	v0.0.13 - fixed triggers perhaps... 0.0.13	2023-05-05 08:32:17 -04:00
mifi	8ee5d627aa	Resolving stupid errors 0.0.12	2023-05-05 08:21:02 -04:00
mifi	775dd60b56	Mostly passing pipelines, still a broken deploy... 0.0.11	2023-05-05 08:19:29 -04:00
mifi	b3365607c5	Muahahahha 0.0.10	2023-05-04 23:28:40 -04:00
mifi	96058995be	New approach...	2023-05-04 23:19:45 -04:00
mifi	1d43b78590	More... 0.0.9	2023-05-04 23:12:09 -04:00
mifi	243682758a	clean-up	2023-05-04 23:07:48 -04:00
mifi	695c4d84e8	Add npmrc, update version, pipeline tweaks - re-enable pipeline in full 0.0.8	2023-05-04 23:05:49 -04:00
mifi	25908dd9d7	Failing on the same old errors...	2023-05-04 22:18:19 -04:00
mifi	34a28b8134	No cache	2023-05-04 22:08:27 -04:00
mifi	7e1f9a1f33	So close I can taste it...	2023-05-04 22:00:41 -04:00
mifi	f0ba205a58	Closer? that was a new error...	2023-05-04 21:51:54 -04:00
mifi	1a717cd83e	Not likely....	2023-05-04 21:49:37 -04:00
mifi	1e932d97c8	Probably not	2023-05-04 21:43:58 -04:00
mifi	d879de2a6b	Maybe a fix for the volume syntax?	2023-05-04 21:41:00 -04:00
mifi	34e3eb04af	Ooops	2023-05-04 21:31:16 -04:00
mifi	ff5f88588e	Auth?	2023-05-04 21:30:25 -04:00
mifi	ac5c09b7da	Or maybe add the registry to the package.json...	2023-05-04 21:17:59 -04:00
mifi	d1b42fe79f	Remove registry from package.json	2023-05-04 21:13:01 -04:00
mifi	3d32c77bd1	That command never played nice...	2023-05-04 21:05:57 -04:00
mifi	8e077810f5	Maybe these path changes will do the trick fixing the volume issues	2023-05-04 21:04:29 -04:00
mifi	5e0621e37d	Copy env into workspace?	2023-05-04 20:59:54 -04:00
mifi	e6f9f9b523	Fix naming collision	2023-05-04 20:53:13 -04:00
mifi	1c5fdabca6	Recombine Steps	2023-05-04 20:48:13 -04:00
mifi	7bbb4bb036	A bit more...	2023-05-04 20:39:38 -04:00