[NocoDB] Working on a guide

[qimmiq]

Hi there, working on a guide for NocoDB, that i hacked together ... anybody wants to check or confirm if it works?

[noave]

Would you like to provide a PR? Then we can review and check it

[s-fischbach]

I'd like to read the guide as I don't get NocoDB to work so far. Would provide some feedback on whether it worked. Thumbs up for providing a PR (although the original post was a while ago...)

[qimmiq]

I will try my best to provide a guide soon. Need to recap what i did back than to get it working

s-fischbach @.***> schrieb am Fr., 20. Jan. 2023, 22:42:

I'd like to read the guide as I don't get NocoDB to work so far. Would provide some feedback on whether it worked. Thumbs up for providing a PR (although the original post was a while ago...)

— Reply to this email directly, view it on GitHub https://github.com/Uberspace/lab/issues/1336#issuecomment-1398986001, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIBU6JLQSHJU7IAN442CULWTMBFHANCNFSM6AAAAAARR7T2WA . You are receiving this because you authored the thread.Message ID: @.***>

[N-Coder]

For anybody who doesn't want to wait for the complete guide, here is what I did: It seems that nocodb doesn't run out of the box on uberspace because the available version of libstdc++ is too old for prebuilt version of the used sqlite3 module. Fortunately, said module can be built locally to circumvent this issue. Using the installation as node application, the following worked for me:

git clone https://github.com/nocodb/nocodb-seed
cd nocodb-seed
npm install
npm install sqlite3 --build-from-source # this is new
npm start

Things that probably need doing afterwards:

• correctly set up the webserver / proxy and NC_BASEURL_INTERNAL / NC_PUBLIC_URL / NUXT_PUBLIC_NC_BACKEND_URL
• switch to postgreSQL backend instead of SQLite (see DATABASE_URL)
• configure SMTP server for sending mail (NC_SMTP_HOST et al)

[N-Coder]

Regarding the web backend setup, I tried putting nocodb in its own subpath, unfortunately this doesn't seem to work at the moment:

export PORT=1234
uberspace web backend set /nocodb --http --port $PORT --remove
# unfortunately, none of the following options really help
export NOCO_URL=https://mydomain.tld/nocodb
export NC_PUBLIC_URL=$NOCO_URL
export NC_BACKEND_URL=$NOCO_URL
export NUXT_PUBLIC_NC_BACKEND_URL=$NOCO_URL
export NC_BASEURL_INTERNAL=$NOCO_URL
export NC_DASHBOARD_URL=/nocodb/dashboard

env | grep NC_
npm start

Possible work-arounds until this nocodb bug is fixed:

• forward everything to nocodb, although this will make your uberspace unusable for other web projects

uberspace web backend set / --http --port $PORT

• forward only the directories which noco needs, which seem to be only /dashboard and /api (the nocodb doc is also reaaally thin here)

uberspace web backend set /dashboard --http --port $PORT
uberspace web backend set /api --http --port $PORT

• move nocodb to its own subdomain, e.g. nocodb.mydomain.tld, set-up as described here

uberspace web backend set nocodb.mydomain.tld --http --port $PORT

[rxlxnd]

Any news on this guide? Would like to play around with Nocodb on Uberspace.