-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Troubleshooting tips #109
Troubleshooting tips #109
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -51,18 +51,19 @@ endef | |
pre-config: pre-init ## Initialise env files, and create some required folders, files and softlinks | ||
@echo "You can now edit your config for flavour '$(FLAVOUR)' in config/$(MIX_ENV)/secrets.env, config/$(MIX_ENV)/public.env and ./config/ more generally." | ||
|
||
CONFIG_PATH=$(FLAVOUR_PATH)/config | ||
pre-init: | ||
@echo "Setting flavour to $(FLAVOUR_PATH)" | ||
@ln -sfn $(FLAVOUR_PATH)/config ./config | ||
@ln -sf $(FLAVOUR_PATH)/config ./config | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. could you explain why the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Docs for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alright fair enough, thank you for explaining. I'll be sure to switch it back before making my next PR |
||
@mkdir -p data/ | ||
@ln -sf ../$(FLAVOUR_PATH) ./data/current_flavour | ||
@mkdir -p config/prod | ||
@mkdir -p config/dev | ||
@touch config/deps.path | ||
@cp -n config/templates/public.env config/dev/ | true | ||
@cp -n config/templates/public.env config/prod/ | true | ||
@cp -n config/templates/not_secret.env config/dev/secrets.env | true | ||
@cp -n config/templates/not_secret.env config/prod/secrets.env | true | ||
@mkdir -p $(CONFIG_PATH)/prod | ||
@mkdir -p $(CONFIG_PATH)/dev | ||
@touch $(CONFIG_PATH)/deps.path | ||
@cp -n $(CONFIG_PATH)/templates/public.env $(CONFIG_PATH)/dev/ | true | ||
@cp -n $(CONFIG_PATH)/templates/public.env $(CONFIG_PATH)/prod/ | true | ||
@cp -n $(CONFIG_PATH)/templates/not_secret.env $(CONFIG_PATH)/dev/secrets.env | true | ||
@cp -n $(CONFIG_PATH)/templates/not_secret.env $(CONFIG_PATH)/prod/secrets.env | true | ||
|
||
pre-run: | ||
@mkdir -p forks/ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,9 +23,9 @@ $ cd bonfire | |
|
||
- The first thing to do is choosing what flavour of Bonfire you want to hack on (the default is `classic`), as each flavour has its own config. | ||
|
||
For example if you want to run the `coordination` flavour: | ||
For example if you want to run the `cooperation` flavour: | ||
|
||
`export FLAVOUR=coordination` | ||
`export FLAVOUR=cooperation` | ||
|
||
- Once you've picked a flavour, run this command to initialise some default config (.env files which won't be checked into git): | ||
|
||
|
@@ -210,7 +210,25 @@ make git.merge~% Draft-merge another branch, eg `make git-mer | |
make git.conflicts Find any git conflicts in ./forks | ||
``` | ||
|
||
## What happens when I get this error? | ||
## Troubleshooting | ||
|
||
### EACCES Permissions Error | ||
|
||
If you get a permissions error when following any of the steps, run the following command and it should be fixed: | ||
|
||
```shell | ||
cd ~/bonfire && sudo chown -R yourusername:yourusername . | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. maybe saying to run the chown in their bonfire directory, since not everyone would have it at ~/bonfire There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suppose it could be changed to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I changed it in the new PR |
||
``` | ||
|
||
### Unable to access Postgres database | ||
|
||
If you are getting any `:nxdomain` errors, check if you have any firewalls that may be blocking the port on your system. | ||
|
||
For example, if you are running UFW (a lot of Linux distros do), run the following command to allow access to port 4000: | ||
|
||
```shell | ||
sudo ufw allow 4000 | ||
``` | ||
|
||
### (Mix) Package fetch failed | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ pkgs, flavour ? "coordination" }: | ||
{ pkgs, flavour ? "cooperation" }: | ||
|
||
with pkgs; | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea