Hi Chris, It sounds like our the docs need clarifying here. You need to run `yarn env:yaml` from the *NEW 7.2 codebase directory*. Since you are trying to run it from your old 7.1 code, it is throwing an error as that command didn't exist in the 7.1 codebase.
So, the docs were written assuming you were going to essentially install 7.2 "on top of" 7.1. In that situation, you'd have the 7.2 code...but your old 7.1 "environment.prod.ts" would still be around (as the update to 7.2 doesn't delete that file). For your purposes, it sounds like your 7.2 code *is in a separate directory from 7.1 code*. So, for your purposes, do this: 1. Copy the "src/environment/environment.prod.ts" from your 7.1 (old) directory, over into the 7.2 (new) directory. Where you choose to copy it into doesn't really matter, but you could put it under "[src-7.2]/config", where the configs eventually need to be. 2. Now, go to [src-7.2] (root 7.2 directory) and run: "yarn env:yaml config/environment.prod.ts config/config.prod.yml". That should be it. You can then look at that config/config.prod.yml to double check it looks correct (the same settings exist in both the YAML and TS config files, they just have a different syntax). Once you are satisfied, you can delete the "environment.prod.ts" from your [src-7.2]/config/ folder. It's not used in 7.2 at all. Tim On Tuesday, February 8, 2022 at 12:26:12 PM UTC-6 Chris Clawson wrote: > Thanks, Tim, but still frustrated! > I understand you are saying to go to my old /src/environments directory, > and run this command: > yarn env:yaml environment.prod.ts > Here is the response I get: > root@melo4:/opt/dspace-angular-old/src/environments# yarn env:yaml > environment.prod.ts > yarn run v1.22.17 > error Command "env:yaml" not found. > > -- embarrassing, did I break something? > On Tuesday, February 8, 2022 at 12:55:19 PM UTC-5 Tim Donohue wrote: > >> Hi Chris, >> >> That "yarn env:yaml" command only requires one input, whish is your old >> "environment.*.ts" file. So, that second input is *optional*. If you only >> give it one input, it'll write the output YAML file into that same >> directory. That's perfectly ok...you'd just want to eventually ensure that >> YAML file gets moved over into >> /opt/dspace-angular-dspace/config/config.prod.yml , which is where the UI >> will look for your configs in 7.2 (and above). >> >> So, I would recommend trying the script with a single input, if the >> multiple inputs is getting confusing. >> >> If somehow the script is erroring out or not working at all, send the >> error message to this list and we'll take a closer look at it. >> >> If worst came to worst, you also can just recreate your configs in YAML >> (based on the examples in config.example.yml) ... but, I completely >> understand that it's a ton easier to just migrate the settings over. >> >> Tim >> >> On Tuesday, February 8, 2022 at 9:44:46 AM UTC-6 Chris Clawson wrote: >> >>> Upgrading DSpace 7.x (7.1 to 7.2), upgrading the Front-end, step 'C' >>> says I should use yarn to convert the earlier installation's .ts files to >>> .yml. I am not able to get past this step. Perhaps I only need some >>> assistance in the specific grammar in using the conversion script. >>> >>> The path to my my old DSpace 7.1 angular 'environments' directory >>> >>> /opt/dspace-angular-old/src/environments >>> >>> My unzipped DSpace 7.2 angular is at: >>> >>> /opt/dspace-angular-dspace >>> >>> My command prompt is located at /opt/dspace-angular-dspace/config >>> >>> Given these conditions, *would someone please provide me* with a >>> specific example of how to produce a working command for the this >>> documentation example to convert environment.prod.ts >>> >>> yarn env:yaml src/environments/environment.prod.ts config/config.prod.yml >>> >> -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/960ee536-d800-44bc-affd-a979f2a2c10cn%40googlegroups.com.
