Skip to content

Improve dev setup - #1209

Merged
salzig merged 2 commits into
masterfrom
dev-setup-improvements
Sep 28, 2026
Merged

salzig merged 2 commits into
masterfrom
dev-setup-improvements

Conversation

@PragTob

@PragTob PragTob commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator

Wanted to work on a bugfix/investigation but in order to get there needed a couple of things which I think would be helpful for folks:

  • database seeds - I don't have access to heroku so having some basic data helps
  • documenting the login workaround a bit also helps getting started
  • many workarounds to try and make google maps work locally (my bug/gripe is in part with that) so allow to override the google maps key to be used for local dev

@PragTob PragTob mentioned this pull request Sep 6, 2026
@salzig

salzig commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator

Bug with Google Maps? Uh? What kind problem do you have right now? (Btw, was already considering to move away from Google Maps. Maybe we’ll find some to discuss your needs?)

@PragTob

PragTob commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator Author

@salzig sorry for no report, it's at #1210 but generally yeah the pin lands in the middle of the ocean: https://www.rug-b.de/events/september-meetup-2026-2729

salzig pushed a commit that referenced this pull request Sep 9, 2026
We noticed on RUG::B that our latest locations weren't geocoded/
ended up in the middle of the ocean which was a bit odd.

After looking into it, turns out that's due to the geocoding
service used here requiring an HTTP header to identify yourself.

So, that was added along with a couple of fail safes against the
`nil`/`nil` -> 0/0 rendering.

Based on the dev setup branch/#1209 since I needed those changes
here.
salzig pushed a commit that referenced this pull request Sep 9, 2026
We noticed on RUG::B that our latest locations weren't geocoded/
ended up in the middle of the ocean which was a bit odd.

After looking into it, turns out that's due to the geocoding
service used here requiring an HTTP header to identify yourself.

So, that was added along with a couple of fail safes against the
`nil`/`nil` -> 0/0 rendering.

Based on the dev setup branch/#1209 since I needed those changes
here.
@salzig
salzig force-pushed the dev-setup-improvements branch from d5009d4 to 9caa654 Compare September 9, 2026 15:21
Comment thread config/environments/development.rb Outdated
# Settings specified here will take precedence over those in config/application.rb.
config.hosts << /.*onruby\.localhost.*/
# for local development with the recommended domains
config.hosts << /.*onruby\.test.*/

@salzig salzig Sep 11, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.test is not "recommended" anymore, but *.localhost is. For the simple fact that the later doesn't need any change in /etc/hosts`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm really interested in getting this branch done and would like to improve a bit the documentation to setup the platform locally. I hope it's okay that I take on hand and fix the things @PragTob.

I remove the .test from the commit, because we have since some time the .localhost solution that works way more smoothly. Also I will remove the one commit that got already deployed.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be fixed now

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, and sorry as per usual I was too busy with too many things so always happy for people to pick up stuff 😅

salzig pushed a commit that referenced this pull request Sep 14, 2026
We noticed on RUG::B that our latest locations weren't geocoded/
ended up in the middle of the ocean which was a bit odd.

After looking into it, turns out that's due to the geocoding
service used here requiring an HTTP header to identify yourself.

So, that was added along with a couple of fail safes against the
`nil`/`nil` -> 0/0 rendering.

Based on the dev setup branch/#1209 since I needed those changes
here.
@salzig

salzig commented Sep 16, 2026

Copy link
Copy Markdown
Collaborator

btw, I took the geocode commit and brought it live. Maybe you could clean up this mr a bit.

@JoschkaSchulz JoschkaSchulz left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i corrected the commit meshup with the geocode fix. Now this should be fine.

@salzig
salzig force-pushed the dev-setup-improvements branch from 2be4959 to b2bcc7b Compare September 18, 2026 11:39
@PragTob

PragTob commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator Author

Looks good to me, thanks for the fixups folks and sorry for the delay!

IMG_20180603_163744

Wanted to work on a bugfix/investigation but in order to get
there needed a couple of things which I think would be helpful
for folks:

* database seeds - I don't have access to heroku so having some
basic data helps
* documenting the login workaround a bit also helps getting
started
* many workarounds to try and make google maps work locally (my
bug/gripe is in part with that) so allow to override the google
maps key to be used for local dev
@salzig
salzig force-pushed the dev-setup-improvements branch from b2bcc7b to 6a39b56 Compare September 28, 2026 21:01
@salzig
salzig merged commit 2535d03 into master Sep 28, 2026
1 check passed
@salzig
salzig deleted the dev-setup-improvements branch September 28, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants