Auto-Content/myapp/media/images/background.jpg The json that dictates which asset folders are pulled can be found in the config files. Wave that contains all waves as not to clutter up the Auto-Content folder with instances. The Auto-Content folder contains folders with the same names as the repo names in bitbucket.
#NVM INSTALL NODE 404 UPDATE#
We need to update the githooks property in our global config to point to the hooks folder found in core.
Git checkout development & git branch -u origin/development Git checkout master & git branch -u origin/master Git remote set-url -add -push origin $gitlab Git remote set-url -add -push origin $bitbucket project.name -r )/ $name | tr ' ' ' ' ) $(echo $repo | cut -d '/ ' -f2 ) $repo Repo= $(echo $(curl -s -u $username: $password $url | jq. bitbucket.password ~/targets/misc.json -r ) if || || || then echo -e "\033[0 31m>\033[0m Can't find bitbucket credentials in ~/targets/misc.json " else Name= $(basename `git rev-parse -show-toplevel ` ) The reason origin isn't part of the npm run setup command is because this would throw an error on any freelancers machine trying to connect to gitlab If you don't currently have the origin command you need to add it. Gitlab should be viewed purely a supporting remote used primarily for the CI/CD and should never be used for forking/cloning under any circumstances.Īfter cloning a repo you have to run the origin command on the terminal which will correctly set the origin to point to both remotes. Repo's should only ever be cloned from Bitbucket. The externally facing bitbucket allows freelancers to contribute to our repositories whilst our internally facing gitlab allows our CI/CD to gain a bunch of security advantages just by the fact that it is inherently on the internal network. We currently utilize two remotes for our git versioning. Install brew - then run the following commands.
#NVM INSTALL NODE 404 PDF#
These dependancies are only needed if you're planning to build a pdf locally or manually deploy to the server. The following dependancies are needed to build the source code. Repositories packaged for handover to external agencies won't need these dependencies as all media assets will be bundled into the handover package. The following dependancies are needed to pull media assets from external file storage. They've been split into three groups, content, build and deploy dependancies.
#NVM INSTALL NODE 404 CODE#
DependanciesĪs this code base is shared amongst most of our repos, these dependancies are likely the only ones you'll ever need to install to get project code up and running. Around 2014 all of that code was pulled to a shared npm module which meant a massive reduction in code repetition throughout all of our code bases. For this reason we ended up with lots of duplicate task runner code in each repo that had to be manually updated if any projects came back from the dead further down the line. To keep code bases small we create many smaller repo's rather than branching projects in a larger monorepo. WhyĪs a company we do a lot of smaller short term builds rather than longer term code bases. This repo contains the code that fetches assets, bundles code and deploys it to the server.
0 kommentar(er)
