...for easier setup
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | kai.nissen | T157560 Use GitHub Repository for Fundraising Frontend contents | |||
Resolved | • Pablo-WMDE | T162281 Integrate content repo as dev dependency |
Event Timeline
Comment Actions
To work on the content/labels and be able to preview the changes on your localhost, the idea was to...
- check out fundraising-frontend-content locally
- set-up phpstorm to "deploy" (ask @Pablo-WMDE for support, he has a working example) fundraising-frontend-content into FundraisingFrontend's vendor folder (vendor/wmde/fundraising-frontend-content)
- once you are happy you can commit fundraising-frontend-content (e.g. feature branch matching your FundraisingFrontend feature branch). You could strengthen this relationship by specifying it in the FundraisingFrontend's composer.json, e.g. "wmde/fundraising-frontend-content": "dev-myFeatureBranch as 1.0.x-dev"
Content "deployment" with PHPstorm on my PC:
pagr@C217:~/projects$ ll drwxrwxr-x 1 pagr pagr 5664 Apr 6 10:02 FundraisingFrontend/ drwxrwxr-x 1 pagr pagr 1176 Apr 5 14:20 fundraising-frontend-content/ pagr@C217:~/projects$ cat fundraising-frontend-content/.idea/deployment.xml <?xml version="1.0" encoding="UTF-8"?> <project version="4"> <component name="PublishConfigData" autoUpload="Always" serverName="FundraisingFrontend"> <serverData> <paths name="FundraisingFrontend"> <serverdata> <mappings> <mapping deploy="vendor/wmde/fundraising-frontend-content" local="$PROJECT_DIR$" web="/" /> </mappings> </serverdata> </paths> </serverData> <option name="myAutoUpload" value="ALWAYS" /> </component> </project>
Please see https://github.com/wmde//pull/862