Option to disable TLS/HTTPS from the docker-compose setup for dev purposes

[claudioc]

Pitch

(on a MacBook Pro M1) Once the docker-compose is up and running, with all the services, I cannot open the web interface on http://something.local:3000 because apparently, the server is expecting a TLS connection. There should be a way to disable this from the environment file, otherwise an nginx proxy server is needed even for local development?

Motivation

Currently the docker-compose setup is probably the only, simple and feasible way to run Mastodon on a MacBookPro M1 because Vagrant doesn't really work (VirtualBox on M1 is still very early alpha and breaks).

Related: #16747

[nyura123]

@claudioc I'm running mastodon locally on my 2015 Mac. My setup was roughly this:

1. bundle install. For postgres, I installed Postgres app, and had to add a special config in ~/.bundle/config:

---
BUNDLE_BUILD__PG: "--with-pg-config=/Applications/Postgres.app/Contents/Versions/latest/bin/pg_config"

2. bundle exec rake mastodon:setup. It generated .env.production which I copied to .env.development
3. Run redis via Docker: docker run -d --name redis1 -p 6379:6379 redis:7-alpine the first time only, then docker container start redis1 going forward.
4. (separate terminal) Copy .env.development to .env, and run node ./streaming (optional, for live UI updating)
5. (separate terminal) RAILS_ENV=development bundle exec sidekiq
6. (separate terminal) RAILS_ENV=development bundle exec rails s -p 3000
7. for uploading files, I needed to install ImageMagick: brew install imagemagick

[sneko]

@claudioc any solution since then?

Thank you,