mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
There is a procedure or instructions for installing the DEV technology stack #268
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Arturo-Penas-Rial on GitHub (Jan 5, 2023).
There is a procedure or instructions for installing the technology stack ? to create the development environment, with:
@RARgames commented on GitHub (Jan 5, 2023):
Check this: https://github.com/plankanban/planka#development
If you encounter any issues and you are working on Windows - see my PR, for line endings issues with prettier make sure you set
git config --global core.autocrlf falsebefore pulling.@Arturo-Penas-Rial commented on GitHub (Jan 5, 2023):
Thanks for your help. I willl follow this guidelines. I am working on CentoOS :-)
@Arturo-Penas-Rial commented on GitHub (Jan 5, 2023):
I found this information en french https://wiki.bruno-tatu.com/informatique/install-planka The information from https://github.com/plankanban/planka#development is not updated.
@RARgames commented on GitHub (Jan 5, 2023):
I used that instruction a day ago and it works. (Tested on Windows and Ubuntu)
1st link is 404.
Here is a step by step guide:
@Arturo-Penas-Rial commented on GitHub (Jan 5, 2023):
I appreciate the indications but it is not working.
First when initializing the database with "npm run server:db:init", it gives the error that you can see in the attached file "log_npm_run_server_db_init".
If I launch "docker compose logs postgres" it shows in the attached file "log_docker_compose_logs_postgres".
When I run "npm run build" it gives the error shown in the attached file "log_npm_run_build" and the corresponding log "log_npm".
Given the previous failures I can't continue with the next steps.
Could you give me some hint or what information can I provide you to guide me?
[Upload
log_npm_run_server_db_init.txt
log_npm.txt
log_npm_run_build.txt
ing log_docker_compose_logs_postgres.txt…]()
@meltyshev commented on GitHub (Jan 9, 2023):
Hm, for development I just run
npm iandnpm run server:db:init. But before doing this, you need to rename the fileserver/.env.sampletoserver/.envand change the database connection string there. After thatnpm startshould start the server and the client in development mode. All commands have to be executed in the root folder.You may have a problem connecting to the database. Please try everything I wrote above and show the output of
npm start.@Arturo-Penas-Rial commented on GitHub (Jan 9, 2023):
Hi @meltyshev :-) Perhaps the problem is the preparation of the environment and dependencies, since I suppose a specific NodeJS version is required, what I have executed is...
curl -sL https://rpm.nodesource.com/setup_14.x | sudo bash -
yum install -y nodejs postgresql libexif-dev libpng-dev libwebp-dev
Or maybe a problem of the components or dependencies, what I have executed is...
npm install npm@latest nodemon
npm install --prod --prefix server
npm install --prefix client
npm run build --prefix client
npm install react-app-rewired --save-dev
Maybe you have a documentation or script to verify that the tones are correct?!
For example, one of the errors is https://stackoverflow.com/questions/65397827/failed-to-load-plugin-prettier-declared-in-eslintrc-json-cannot-find-modul
@meltyshev commented on GitHub (Jan 10, 2023):
Do you get this error during
npm run build --prefix client?Please try it this way:
DISABLE_ESLINT_PLUGIN=true npm run build --prefix client, I've already encountered this error somewhere...@Arturo-Penas-Rial commented on GitHub (Jan 11, 2023):
Hi @meltyshev
Thanks for your support. i need it urgently, as i would like to use your application, but i need to be able to extend, build and test.
I just ran the command, with the following results:
➜ client pwd
/var/www/planka/client
➜ client DISABLE_ESLINT_PLUGIN=true npm run build --prefix client
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /var/www/planka/client/client/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/var/www/planka/client/client/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-01-11T14_45_11_916Z-debug-0.log
But, without "--prefix client", it seems to work fine, except for the following error :
➜ client DISABLE_ESLINT_PLUGIN=true npm run build
Creating an optimized production build...
/var/www/planka/client/config-overrides.js:11
const res = data.replaceAll(search, replace);
^
TypeError: data.replaceAll is not a function
at /var/www/planka/client/config-overrides.js:11:22
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:71:3)
@Arturo-Penas-Rial commented on GitHub (Jan 11, 2023):
@meltyshev I am currently using ...
➜ server npm version
{
npm: '9.2.0',
node: '14.21.1',
v8: '8.4.371.23-node.87',
uv: '1.42.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.18.1',
modules: '83',
nghttp2: '1.42.0',
napi: '8',
llhttp: '2.1.6',
openssl: '1.1.1q',
cldr: '40.0',
icu: '70.1',
tz: '2022e',
unicode: '14.0'
}
And my scrit is ...
cd /var/www
sudo git clone https://github.com/plankanban/planka.git
cd planka
npm i prepare
npm audit fix
npm i
cd client
DISABLE_ESLINT_PLUGIN=true npm run build --prefix client (opcional)
cp -r build ../server/public
cp build/index.html ../server/views/index.ejs
cd ../server
npm install
cp .env.sample .env
add to .env
"BASE_URL=http://localhost:1337
DATABASE_URL=postgresql://www-data:planka@localhost/planka
SECRET_KEY=7bf85ef1e9f447baa922da6f8efe9c80ceb07e0169f62a0aa44ff0a1667111e1ec624490946665aaed77613f2dfc534523b4e8927143cf28434cddbeb4dd2550
DISABLE_ESLINT_PLUGIN=true"
cd /var/www/planka
npm run server:db:init
npm start
Perhaps (I hope anxiously) you can identify what I'm doing wrong or missing dependencies.
Is it correct? Do I need to make changes? Many thanks! :-)
@meltyshev commented on GitHub (Jan 11, 2023):
Sorry, we seem to have an incompatibility with the version of Node 14 in the
client/config-overrides.js🙈How you can solve it now before we fix it:
Replace
const res = data.replaceAll(search, replace);withconst res = data.replace(new RegExp(search, 'g'), replace);in theclient/config-overrides.js. Or update Node to version 18 and it should work withreplaceAll.@Arturo-Penas-Rial commented on GitHub (Jan 11, 2023):
Many thanks! :-) I will try your guidelines! Have a nice day
@Arturo-Penas-Rial commented on GitHub (Jan 11, 2023):
Hi @meltyshev, I share the results, base on Node:18
Well, I try with ...
[centos@centosstream9 ~]$ sudo su -
➜ ~ node --version
v18.12.1
npm --version
9.2.0
**The reached results are ...
From planka HOME**
planka npm i
up to date in 800ms
89 packages are looking for funding
run
npm fundfor detailsup to date, audited 2021 packages in 6s
310 packages are looking for funding
run
npm fundfor details23 vulnerabilities (17 low, 6 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run
npm auditfor details.fatal: detected dubious ownership in repository at '/var/www/planka'
To add an exception for this directory, call:
up to date, audited 441 packages in 9s
66 packages are looking for funding
run
npm fundfor detailsfound 0 vulnerabilities
And from client directory ...
➜ planka cd client
➜ client DISABLE_ESLINT_PLUGIN=true npm run build
Creating an optimized production build...
Failed to compile.
Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (108)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v7.0.3
"[node-sass]" is not supported by node:19
HOW CAN I SOLVE IT? IF I DOWNGRADE TO VERSION 17 the previous error would not appear but the one I mentioned in the previous message "TypeError: data.replaceAll is not a function".
@meltyshev commented on GitHub (Jan 11, 2023):
To fix the
"[node-sass]" is not supported by node:19error you need to delete the node_modules folders and try to install again. I faced this too, apparently already installed library is incompatible and it helped me to delete and re-install after changing the Node version.@Arturo-Penas-Rial commented on GitHub (Jan 16, 2023):
Good news!, @meltyshev I finally managed to implement the development environment. In return for the help received, I make myself available to update the documentation so that it will be easier for possible interested parties.