Sojan Jose
8bbf6c75e3
chore: Improvements to codespaces ( #11635 )
...
- Remove the deprecated extensions
- Install claude code in base image
- Fix rails deprecation warning
2025-05-29 21:18:02 -06:00
Sojan Jose
fdd35ff549
chore: Update Codespaces ( #11621 )
...
- Fix issues with the current Chatwoot development codespaces
- Switch from webpacket to vite
- Add additional configs to make the development easier with codespaces
- toggles v4 feature true as default
2025-05-29 01:45:00 -06:00
Sojan Jose
bc42aec68e
chore: upgrade ruby version to 3.4.4 ( #11524 )
...
- Chore upgrade ruby version to 3.4.4 before we migrate to rails 7.2
over #11037
2025-05-21 19:40:07 +05:30
Shivam Mishra
f2a7e1da6b
fix: Corepack pnpm issue ( #10840 )
...
So, a while back Circle CI builds and Heroku builds started to fail.
From all the threads I read, it seems like the [npm registry rotated
it's signing
keys](https://github.com/pnpm/pnpm/issues/9014#issuecomment-2616589753 )
New pnpm versions were signed with the new key. Corepack, however,
bundles a static set of trusted keys (from Node’s release), so it
continued verifying signatures only against the old key. When it
encountered packages signed with the new key, Corepack’s integrity check
failed with “Cannot find matching keyid” errors.This mismatch caused
Corepack’s integrity check to fail with “Cannot find matching keyid”
errors.
Workarounds include the following
1. Updating Corepack (to 0.31.0), they [upgraded their
package](https://github.com/nodejs/corepack/releases/tag/v0.31.0 ) to
include the new integrity check keys. But we seldom control what's going
on with the CI, also, updating this across our scripts is going to be a
painful task. Besides Heroku has [made some
fixes](https://github.com/heroku/buildpacks-nodejs/pull/1010 ) around
this
2. Disabling integrity checks 🔥 #YOLO
3. Pinning `pnpm` to older versions, or pinning it to a newer version
with the checksum in place.
Doing the third one here, running `corepack use pnpm@9.15 .5` fixes this,
[ref](https://github.com/pnpm/pnpm/issues/9014#issuecomment-2623761494 )
We can get rid of this over time as CDN caches used by build systems are
refreshed. But the change in this PR is not disruptive in anyway, only
rigidly secure.
Fixes: https://github.com/chatwoot/chatwoot/issues/10832
---
Here are the threads to follow
- https://github.com/pnpm/pnpm/issues/9014
- https://github.com/pnpm/pnpm/issues/9029
- https://github.com/nodejs/corepack/issues/612
- https://github.com/nodejs/corepack/issues/616
- https://github.com/heroku/buildpacks-nodejs/pull/1010
---------
Co-authored-by: Vishnu Narayanan <vishnu@chatwoot.com >
2025-02-05 10:12:29 -08:00
Vishnu Narayanan
91dd92e318
feat: switch to postgres docker images with pgvector support (v4.0) ( #10658 )
...
Starting v4.0, pgvector support is mandatory. This PR adds pgvector
support for new docker installations.
- Switch to postgres images with pgvector support
- Change the default postgres version from `12` to `16`
2025-01-14 19:45:42 +05:30
Sojan Jose
31bcdaa3dd
chore: Upgrade ruby to 3.3.3 ( #9664 )
...
- Upgrade the ruby version to 3.3.3
---------
Co-authored-by: Vishnu Narayanan <iamwishnu@gmail.com >
2024-07-05 12:20:07 +05:30
Liam
4958b3e7b6
chore: Fix codespaces not booting up ( #8264 )
...
Fixed an issue where the codespace was not correctly booting up.
Fixes #7609
Co-authored-by: Liam Ashdown <liam.ashdown@debbiesvillas.co.uk >
Co-authored-by: Sojan <sojan@pepalo.com >
2024-01-16 14:34:23 +04:00
Sojan Jose
022383d942
chore: Upgrade to Rails 7 ( #6719 )
...
fixes : #6736
2023-05-06 10:44:52 +05:30
Sojan Jose
7cbf1857e4
chore: Set statement timeout for Postgres ( #6641 )
...
By default, Rails does not set a timeout on database statements. For example, this will run for a full day, even if your ruby process goes away. But it's configurable in the database.yml with the statement_timeout variable.
Hence we are enforcing a 14s timeout by default. Migration commands inside chatwoot will run with a 10 minutes timeout. For specific cases like migrations, we can override this timeout using the environment variable POSTGRES_STATEMENT_TIMEOUT while starting a new rails console.
Test the timeouts from the rails console using.
```
ActiveRecord::Base.connection.execute("SELECT pg_sleep(15);")
```
ref: https://github.com/ankane/the-ultimate-guide-to-ruby-timeouts#postgresql
ref: https://til.hashrocket.com/posts/b44baf657d-railspg-statement-timeout-
2023-03-13 18:34:18 +05:30
Afonso Lage
e3d9a0441d
chore: Bumped Ruby version on codespace image to 3.1.3 ( #6490 )
...
- Bumped Ruby version on codespace docker image to match the new Ruby version 3.1.3, which is required since from 2.14.
2023-02-21 17:05:46 +05:30
Sojan Jose
6c6df8661b
chore: Codespace webpacker fix ( #4887 )
...
- fixes the webpacker error when running overmind start -f Procfile.dev
2022-06-17 19:12:56 +05:30
Sojan Jose
db86263353
chore: Codespace Improvements ( #4867 )
...
- switch to ubuntu base image
- use rbenv to manage ruby
- add gh to base image
2022-06-17 03:07:07 +05:30
Sojan Jose
ab54d9c629
chore: Upgrade rails and ruby versions ( #2400 )
...
ruby version: 3.0.2
rails version: 6.1.4
2021-08-03 20:11:52 +05:30
Sojan Jose
a5bc81b304
chore: Suppress the unnecessary CSRF warning ( #2606 )
...
Suppress the unnecessary CSRF warning
2021-07-14 18:40:24 +05:30
Sojan Jose
dfddf9cacc
chore: one off SMS campaign APIs ( #2589 )
2021-07-14 12:24:09 +05:30
Sojan Jose
bbc47971d7
chore: Reduce steps to spin up Codespaces ( #2576 )
2021-07-06 21:21:40 +05:30
Sojan Jose
fa37f8e185
chore: Support Github Codespaces ( #2510 )
...
Note: Update the ruby version 2.7.3. For production Linux VM, install 2.7.3 and follow the upgrade steps as shown in https://www.chatwoot.com/docs/self-hosted/deployment/linux-vm#upgrading-to-a-newer-version-of-chatwoot
2021-06-29 19:18:10 +05:30
Sojan Jose
1f02c09a41
chore: Setup dev env with Github Codespaces [alpha] ( #1282 )
...
Easily spin up a Chatwoot development environment with Github Codespaces.
2020-12-09 17:01:28 +05:30
