From 7ad86f6dbb65941f9c7aa49a1938e1a0a5bb7d50 Mon Sep 17 00:00:00 2001 From: Jules Laplace Date: Thu, 10 May 2018 18:30:55 +0200 Subject: dont hardcode s3 path --- README | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'README') diff --git a/README b/README index 66cf52a..d1d5fdf 100644 --- a/README +++ b/README @@ -21,6 +21,8 @@ GRANT ALL PRIVILEGES ON bucky.* TO 'carbon'@'localhost'; Copy .env-sample to .env and edit the values accordingly. +PLEASE change the value of S3_PATH to if you reuse S3 buckets. + #### Loading an old bucky db dump ``` @@ -51,7 +53,7 @@ You may have to include the .so files for bdb: `export LD_LIBRARY_PATH=/var/www/ npm start ``` -Server will be running at http://lvh.me:5000/ (or whatever port you set in the .env) +Server will be running at http://localhost:5000/ aka http://lvh.me:5000/ (or whatever port you set in the .env) -In production I use something to daemonize the node server, such as pm2 (provides nice dashboard with uptime, restarts, saves logs, etc). Run the web server on a high port and then put it behind NGINX. +In production I use something to daemonize the node server, such as pm2 (provides nice dashboard with uptime, restarts, saves logs, etc). -- cgit v1.2.3-70-g09d2