ensl/ensl.org
0
0
Fork 0
mirror of https://github.com/ENSL/ensl.org.git synced 2025-02-10 18:20:53 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update docs

Browse source
This commit is contained in:
Ari Timonen 2020-04-10 19:57:08 +03:00
parent f29eb22aa9
commit bfe19eb5e9
2 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.gitignore vendored
View file

@ -2,7 +2,7 @@
/log/* /log/*
!log/.placeholder !log/.placeholder
/tmp/* /tmp/*
!tmp/.placeholder !tmp/**/.placeholder
/spec/tmp/* /spec/tmp/*
.ruby-version .ruby-version
.ruby-gemset .ruby-gemset

12
DEVELOPMENT.md
View file

@ -22,8 +22,8 @@ Debug:
To get inside docker web+test containers: To get inside docker web+test containers:
docker-compose exec -u root web /bin/bash` docker-compose exec -u root development /bin/bash`
docker-compose exec -u web web /bin/bash` docker-compose exec -u web development /bin/bash`
docker-compose exec -u root test /bin/bash` docker-compose exec -u root test /bin/bash`
docker-compose exec -u web test /bin/bash` docker-compose exec -u web test /bin/bash`
@ -36,9 +36,15 @@ Run some tests:
docker-compose exec -u web test bundle exec rspec` docker-compose exec -u web test bundle exec rspec`
docker-compose exec -u web test bundle exec rspec spec/controllers/shoutmsgs_controller_spec.rb` docker-compose exec -u web test bundle exec rspec spec/controllers/shoutmsgs_controller_spec.rb`
## Unresolved issues
There are some unresolved issues to setup dev env.
1. Make sure tmp, tmp/sockets, tmp/pids and log exist.
1. Make sure docker has access to its dirs. You might have to `sudo chown -R 999:999 for` for `db/data` if you have permission issues with docker.
## Tips ## Tips
1. You might have to `sudo chown -R 999:999 for` for `db/data` if you have permission issues with docker.
1. If you need to run stuff on your host (eg. ruby, rubocop, bundle install etc) run all commands from the: `Dockerfile.dev`. It should setup identical setup for your machine. 1. If you need to run stuff on your host (eg. ruby, rubocop, bundle install etc) run all commands from the: `Dockerfile.dev`. It should setup identical setup for your machine.
1. Add docker container names to /etc/hosts. This makes it possible to run test from local machine without using the container since editor/IDE don't integrate with Docker so well. 1. Add docker container names to /etc/hosts. This makes it possible to run test from local machine without using the container since editor/IDE don't integrate with Docker so well.