a5a0cda295
Fix tailscale serve: use localhost:PORT, helpful error on Linux
...
Tailscale serve only supports localhost or 127.0.0.1 as proxy targets.
On Linux, prompts user to run `sudo tailscale set --operator=$USER` if access denied.
2025-12-16 14:47:09 -08:00
a755ecdec9
Must be run as sudo
2025-12-16 14:36:51 -08:00
bf6ddcb933
Add --tailscale flag to bin/dev for remote access ( #2168 )
...
Enables sharing dev sites over Tailscale serve. Uses port convention
4xxxx (prepending 4 to the dev port, echoing TLS 443) so multiple apps
can run simultaneously on different ports.
Usage: bin/dev --tailscale
2025-12-16 09:54:53 -08:00
6f002b66d8
In non-SaaS, run jobs in container by default
2025-12-10 12:32:35 +00:00
6345aa4787
Update seeds to use @example.com
...
See also https://www.rfc-editor.org/rfc/rfc2606.html
2025-12-03 15:40:58 -05:00
4ad1718d86
Stub searchable functionality and start to restore login/auth
2025-11-17 09:11:42 -05:00
4d3c265042
Rip out activerecord-tenanting
...
Co-authored-by: Stanko K.R. <stanko@stanko.io >
2025-11-17 09:11:35 -05:00
48783824ee
Fix some small things related to accounts
2025-10-03 16:55:00 -04:00
fcd3c178ce
Account#slug uses the virtual "tenant" attribute
2025-10-02 16:44:24 -04:00
320558919c
Rename LOCAL_AUTHENTICATION to OSS_CONFIG
2025-10-02 16:44:24 -04:00
d5a4239d19
Rename the queenbee_id and signal_user_id columns
...
to be more generic for the open-source release.
Find the signal account via Account#external_account
Find the signal user via User#external_user
2025-09-15 13:57:53 -04:00
2630e4bd74
Extract 37id and QB controllers, models, and tests
2025-09-13 16:03:02 -04:00
9db98366c3
Set up a "cleanslate" seed that has no cards and no collections
...
and only a single user, david@37signals.com
ref: https://fizzy.37signals.com/5986089/collections/7/cards/1318
2025-08-06 17:35:55 -04:00
57269b1b9c
Allow local authentication with LOCAL_AUTHENTICATION=1
...
You can touch `tmp/local-auth.txt` to persist this setting.
2025-08-06 17:05:35 -04:00
3d39bdc9f3
Update bin/dev to point at the new tenant URLs
2025-07-01 15:56:14 -04:00
a8a64a2384
Link the seeds up to the signal_id fixture data
2025-06-20 15:16:57 -04:00
3444427d32
Don't run solid queue in dev by default
...
but allow it to be turned on by touching tmp/solid-queue.txt
2025-05-08 13:44:05 -04:00
f42973618d
bin/dev ensures puma runs solid queue
...
ref: https://37s.fizzy.37signals.com/collections/693169850/cards/999009028
2025-05-07 14:38:59 -04:00
29948d8881
Enumerate all the options for logging in
2025-04-21 15:23:31 +02:00
70275c9f04
Yank Solid Queue from development
...
It clogs up the test log and occasionally causes the puma to hang when
you want to quit.
2025-04-18 16:30:30 +02:00
d9ece38753
Make the application multi-tenant
2025-03-12 07:53:31 -04:00
8b17a33a75
Only run Solid Queue in Puma in dev
...
In production, we have extra containers for it.
2025-02-10 17:55:46 +00:00
bbb394db02
Drop puma-dev in favor of localhost
2024-09-06 16:28:51 -04:00
Jeremy Daer