Using Tidepool on Linux

[sonocculture]

I want to install the Tidepool Uploader on Ubuntu 22.04 following the instructions helpfully provided here. After a few hours of sleuthing, I still don't understand how Docker works and how to follow these instructions:

• Build the image docker-compose build
• Run it docker-compose up -d

1. Do I just run docker-compose build from the path of where I cloned the repository, and then Docker takes care of the rest?
2. If I'm using Docker, do I still have to install/configure nvm, npm, and yarn (as per https://github.com/tidepool-org/uploader?tab=readme-ov-file#how-to-set-it-up), or is that for something else?

Would it be possible to expand on these instructions for less experienced linux users?

Feel free to delete if this is not the right place for questions like these.

[gniezen]

Hi @sonocculture ! There are some issues with the Docker setup at the moment, so I would recommend using the approach you mentioned in (2). While we don't officially support Linux at the moment, I use Linux to develop Uploader, so may be able to help you with any issues that you run into.

[m1st0]

Using Kubuntu 24.10, I wanted to share some of the setbacks I found and fixes.

gh repo clone tidepool-org/uploader tidepool_uploader
cd tidepool_uploader
git checkout tags/v2.60.0 -b v2.60.0 # Current release tag at this moment.
yarn
yarn build

Which resulted in errors about "--profile --colors" being unknown options, so I removed them manually from package.json using vim and the command :%s/ --profile --colors//g . (If you fix this since I am limited on timing today, please add me in credit.)

Onward then...

yarn build
yarn start --no-sandbox # Don't want to fix sandbox permissions and security for this test.

Resulted in

yarn start --no-sandbox                                 
yarn run v1.22.19
warning ../../package.json: No license field
$ cross-env NODE_ENV=production electron ./app/main.prod.js --no-sandbox
Using browser-only version of superagent in non-browser environment
Crash logs can be found in: $HOME/.config/Electron/Crashpad
Last crash report: { date: 1970-01-01T00:00:00.000Z, id: '' }
Uploading only new records
Render process gone: crashed

This comes up in later versions of Node. So I installed nvm and swtiched to the version needed and found success.

wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
nvm install v18.17.1 # So long as you setup NVM correctly or restarted your terminal
nvm use v18.17.1
yarn start --no-sandbox # Don't want to fix sandbox permissions and security for this test.

Success.

[gniezen]

Glad you got it working @m1st0 ! Indeed, you do need to use the version of Node.js we specify in .nvmrc for everything to work correctly. If you already have nvm installed, you can just type nvm use in the uploader directory and it will automatically use the version specified in .nvmrc.

To be honest, I haven't used yarn start in a long time and always use yarn dev, which does use no-sandbox. I'll add no-sandbox to yarn start and remove the deprecated options (and credit you in the git comment 😉 ) Thank you!