- Create a new collection in postman - only include actions you want to run in there.
- Give it a CSV with the amendments/fields, name the columns by the variables that postman expects.
- Remember to put the underscores in the column names in CSV.
- Add number of iterations for how many times you want it to happen.
Nightly rates live in the provider_reservation_successful
event.
Doing a code read today in our monthly 10% time I started to read and document an internal event sourcing framework
we've built in our team. I stumbled across the .dup
method and so naturally I got sidetracked (losing sight of the high level) with StackOverflow posts, Ruby-Doc and my own IRB comparisons between it, and another method that appears quite
similar -clone
.
Importantly dup
differs from clone
in that it duplicates the object as a completely new record (if it's an ActiveRecord
object no id
is assigned however if it's a PORO a new object_id is assigned so it's completely different).
The duped object has no direct assocation with the original at all. Thus, if you modify a duped object, you won't change
the original object and that's because it's a “shallow” copy – it copies the object’s attributes only, not its associations.
You can use mitmproxy which is an interactive HTTPS proxy.
- Install it:
brew install mitmproxy
- In ted:
- go to
common-services.yml
- find the relevant app_name-base ie.
bookings-base
,reservations-base
- add
HOOROO_PROXY: "http://middleman:8080"
- go to
- Middleman is best viewed in Chrome.
- The URL to view it in the browser is
http://middleman.ted:8081
- Run the Ted start script to restart the containers
./start
- Spin up Postman, use the Epic in there to create your availability, make a booking etc.
- Keep commits small/atomic
- Make use of fixup commits (for related changes)
git commit --fixup sha
- If responding to a request/comment in PR reply with a comment like "Done in
<commit-sha>
", then:
git push origin head
git rebase -i origin/master --autosquash
- Once there's a nice history:
git push origin head -f
git checkout master && git merge br-name --ff-only
- Remember to run your specs again!
- git push origin master
- Mounting apps locally use the branch that you have checked out locally.
- When you want to execute a rails type of command inside a container:
docker-compose exec app_name <bundle update --source gem_name>
where the command is the thing in the<>
- try turning Docker daemon off and on again
- To log in to a container to tail the logs
docker-compose exec <container-name> bash
thentail -f log/*logs
Go into the app folder and run:
tail -f log/*