./dev.sh

dev.sh ni hati ya bash ya msaidizi ambayo hufanya kufanya kazi na mazingira ya ukuzaji ya Climweb kuwa rahisi.

Kwa chaguomsingi, kuendesha ./dev.sh kutaanzisha dev env na kuhakikisha kuwa vyombo vinafanya kazi kama mtumiaji wako halisi.

Mifano ya matumizi ya ./dev.sh:

$ ./dev.sh # same as the up command above but also ensures the containers run as the running user!
$ ./dev.sh --build # ups and rebuilds
$ ./dev.sh restart # stops and then ups
$ ./dev.sh restart --build # stops, builds, ups
$ ./dev.sh build_only # just builds
$ ./dev.sh dont_migrate # ups but doesn't migrate automatically on startup
$ ./dev.sh dont_migrate dont_sync dont_attach restart --build # even more flags!
$ ./dev.sh run backend manage migrate
# Any commands found after the last `./dev.sh` command will be passed to the `docker compose up` call made by dev.sh
# This lets you say do --build on the end or any other docker-compose commands using dev.sh!
$ ./dev.sh restart {EXTRA_COMMANDS_PASSED_TO_UP}  
$ ./dev.sh down # downs the env
$ ./dev.sh kill # kills (the old stop_dev.sh)
# WARNING: restart_wipe will detail ALL volumes associated with that environment 
# permanently. 
$ ./dev.sh restart_wipe --build

Kwa nini ./dev.sh inahakikisha kwamba vyombo vinaendeshwa kama wewe

Katika hali ya uboreshaji, saraka za udhibiti wa vyanzo vya Climweb huwekwa kutoka kwa repo ya ndani ya git hadi kwenye vyombo. Kwa kupachika vyombo hivi vitaona mabadiliko ya msimbo wa chanzo na kuunda upya kiotomatiki. Walakini, ikiwa vyombo havifanyi kazi kama mtumiaji wako halisi basi vyombo vinaweza kubadilisha umiliki kimakosa au kuunda faili zinazomilikiwa na mtumiaji anayeendesha ndani ya kontena. Kwa hivyo kwa kuendesha vyombo kama mtumiaji wako hakuna nafasi kwamba saraka zako za udhibiti wa chanzo zitakuwa na shida za umiliki wa faili. Kwa kuongeza, ni mazoezi bora kutoendesha vyombo vya Docker kama mtumiaji wa mizizi chaguo-msingi.