Deploy Hubl MR 267 for testing

Testing: applications/hubl!267 (merged)

Pour la tester comme il faut, j'ai besoin:

• D'un serveur tout à jour (DjangoLDP>2.1 + ses paquets à jour)
• De la branche feature/config-refactoring
• De ce config.json, par exemple pour test 3 : https://snippet.vraiment.top/?f8eecc4e66118e2c#CjpxX3ZmGHDiLuTuVq1odSjsxxEfms4cvGAWT6R2rwXh

changed milestone to %[INV36] Instance deployment

changed the description

@jbpasquier Done.

THe specific platform branch to work on this is test/mr_267

I deployed it on test3 to match your sample but it's a processed template so you can deploy it everywhere as long as yo do it from the test/mr_267 branch.

Happy testing !

Things I have noticed:

• skills now point to the instance itself and not to a "reference" instance

From testing envs, skills of:

• test3 -> test3
• test1, test2 -> test1
• stg1, stg2 -> stg1
• Hubl productions -> community-hubl
• Others -> themselves

Today everything points to client_skills_instance_reference: api.community.hubl.world.

I just need to override this value where it needs to be. Question is: should that be at the federation level ?

@plup I manually ran an npm run build because the actual one looks like its built from the master (or at least an old version?)

I got a build error.

Problems:

• line 3: "name": "clientName": "test3", is written instead of "name": "test3",
• line 4: "logo": "https://cdn.startinblox.com/logos/webp/hubl.webp", remove the comma
• line 10: "authorityName": "test3",, remove the comma
• line 13 "get": "https://api.test3.startinblox.com/open-communities/",, remove the comma

Then, it build properly.

Ok I'm fixing it.

Looks like you already did it.

I also pushed back other configuration that were on master. It should not change that much things on test3 (beside the favicon). If you or someone is able to test it properly for other apps? !51 (merged)

closed