[Support] xthursdayx - UNRAID Docker Templates


Recommended Posts

Hi tying to set up standardnotes. I did copy the file to appdata and set up the file as described. docker is created but when I start it logs only show

text  error  warn  system  array  login  

lerna-lite notice cli v1.6.0
lerna-lite info versioning independent
lerna-lite notice filter including "@standardnotes/web-server"
lerna-lite info filter ["@standardnotes/web-server"]
lerna-lite info Executing command in 1 package: "yarn run start"
lerna-lite notice cli v1.6.0
lerna-lite info versioning independent
lerna-lite notice filter including "@standardnotes/web-server"
lerna-lite info filter ["@standardnotes/web-server"]
lerna-lite info Executing command in 1 package: "yarn run start"
lerna-lite notice cli v1.6.0
lerna-lite info versioning independent
lerna-lite notice filter including "@standardnotes/web-server"
lerna-lite info filter ["@standardnotes/web-server"]
lerna-lite info Executing command in 1 package: "yarn run start"
Prestart Step 1/1 - Removing server lock
Starting Server...
Prestart Step 1/1 - Removing server lock
Starting Server...
Prestart Step 1/1 - Removing server lock
Starting Server...

 

 

You write "Update the container ExtraParams accordingly." Do i need to add all content of the env file to the extra parameters?

 

br,

distel

Link to comment
  • 1 month later...
On 9/18/2022 at 8:15 AM, distel said:

You write "Update the container ExtraParams accordingly." Do i need to add all content of the env file to the extra parameters?

 

 

Sorry for the delay. No, your .env file should just be in your appdata directory and the Extra Parameters section of the container template in Unraid should be used to point to this file, as it does in my template. If you turn on "Advanced View" when editing the template, you should see a section called "Extra Parameters". It should point to your .env file with a command like this "--env-file=/mnt/cache/appdata/standardnotes-web/.env". You do not need to copy the contents of the file into the Extra Parameters.

 

Outside of this, I'm not sure what is causing the problem. My container is running fine with these same settings.

 

For reference, the contents of my .env file are as follows:

RAILS_ENV=development
PORT=3001
WEB_CONCURRENCY=0
RAILS_LOG_TO_STDOUT=true
# Log Level options: "INFO" | "DEBUG" | "INFO" | "WARN" | "ERROR" | "FATAL"
RAILS_LOG_LEVEL=INFO
RAILS_SERVE_STATIC_FILES=true
SECRET_KEY_BASE=************************************************************
APP_HOST=https://notes.my.domain
PURCHASE_URL=https://standardnotes.com/purchase
PLANS_URL=https://standardnotes.com/plans
DASHBOARD_URL=http://standardnotes.com/dashboard

DEFAULT_SYNC_SERVER=https://sync.my.domain

# Development options
DEV_DEFAULT_SYNC_SERVER=https://api.standardnotes.com
ENABLE_UNFINISHED_FEATURES=false
DEV_WEBSOCKET_URL=wss://sockets-dev.standardnotes.com

# NewRelic (Optional)
NEW_RELIC_ENABLED=false
NEW_RELIC_THREAD_PROFILER_ENABLED=false
NEW_RELIC_LICENSE_KEY=
NEW_RELIC_APP_NAME=Web
NEW_RELIC_BROWSER_MONITORING_AUTO_INSTRUMENT=false

**Note - I also run Standard Notes standalone sync server locally, if you do not, then your DEFAULT_SYNC_SERVER should be the default Standard Notes Server.

Edited by xthursdayx
Link to comment
On 6/14/2022 at 11:29 AM, plantsandbinary said:

Why am I getting this in standard notes when I try to register an account?

 

Puma starting in single mode...
* Puma version: 5.6.2 (ruby 2.7.4-p191) ("Birdie's Version")
*  Min threads: 5
*  Max threads: 5
*  Environment: development
*          PID: 8
* Listening on http://0.0.0.0:3001
Use Ctrl-C to stop
{"level":"INFO","time":"2022-06-14T14:19:38.325+03:00","message":"Cannot render console from 141.101.104.52! Allowed networks: 127.0.0.1, ::1, 127.0.0.0/127.255.255.255","ddsource":["ruby"]}
{"level":"INFO","time":"2022-06-14T14:19:38.364+03:00","message":"{\"method\":\"GET\",\"path\":\"/\",\"format\":\"html\",\"controller\":\"ApplicationController\",\"action\":\"app\",\"status\":200,\"duration\":34.26,\"view\":31.62}","ddsource":["ruby"]}

 

I have it running at https://mynotes.mysite.com

It's using an HTTPS cert from cloudfare.

 

I'm using NGinx Proxy Manager. Set up with websockets support also.

It's forwarding 192.168.1.55:3001 > https://mynotes.mysite.com

 

Whenever I try and register an account I get the above error though.

I'm using the following .env file:

 

RAILS_ENV=development
PORT=3001
WEB_CONCURRENCY=0
RAILS_LOG_TO_STDOUT=true

# Log Level options: "INFO" | "DEBUG" | "INFO" | "WARN" | "ERROR" | "FATAL"
RAILS_LOG_LEVEL=INFO

RAILS_SERVE_STATIC_FILES=true
SECRET_KEY_BASE=[redacted]

APP_HOST=https://[redacted]
PURCHASE_URL=https://standardnotes.com/purchase
PLANS_URL=https://standardnotes.com/plans
DASHBOARD_URL=http://standardnotes.com/dashboard
DEFAULT_SYNC_SERVER=https:/[redacted]
WEBSOCKET_URL=wss://sockets-dev.standardnotes.com

ENABLE_UNFINISHED_FEATURES=false

# NewRelic (Optional)
NEW_RELIC_ENABLED=false
NEW_RELIC_THREAD_PROFILER_ENABLED=false
NEW_RELIC_LICENSE_KEY=
NEW_RELIC_APP_NAME=Web
NEW_RELIC_BROWSER_MONITORING_AUTO_INSTRUMENT=false

DEV_ACCOUNT_EMAIL=
DEV_ACCOUNT_PASSWORD=
DEV_ACCOUNT_SERVER=

 

What else am I missing?

Sorry @studentgrant I accidentally missed your question. If you are still having this problem let me know and I can help you troubleshoot.

Link to comment

i'm getting constant error messages from the SearXNG docker that all of the search providers I want to use are banning me.

 

Basically I keep getting:

 

BRAVE - Timeout (error)

Qwant - Banned (error)

Startpage - Timeout (error)

 

etc. etc.

 

If I re-run the search or mash the enter button a few times the search usually completes. However, it's really unreliable.

 

I am the ONLY one using this docker container, and I have it secured pretty heavily. It's not showing any other people connecting to it.

 

Why do I keep getting timeout or bans or captcha failure errors from this container?

Link to comment

Ok so it seems that Startpage just sucks and makes the searches take over 6 seconds. So I disabled it.

I also disabled Brave because it has an average completion time of 3 seconds... which is too slow.

 

With Google, Bing and Duckduckgo, the searches are much, much faster.

 

Qwant has disappeared though after I disabled the others. Now I get this error which says the config isn't set correctly for some reason.

 

Also the container is complaining that I am missing a line in my uwsgi.ini which is not true. That line does exist at the bottom.

 

spawned uWSGI worker 11 (pid: 133, cores: 4)
spawned 12 offload threads for uWSGI worker 10
spawned uWSGI worker 12 (pid: 143, cores: 4)
cache sweeper thread enabled
spawned 12 offload threads for uWSGI worker 11
spawned 12 offload threads for uWSGI worker 12
2022-10-21 22:02:52,630 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,631 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,633 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,646 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,648 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,653 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,654 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,655 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,657 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,672 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,691 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:52,694 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
2022-10-21 22:02:53,370 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,372 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,373 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,374 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,375 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,377 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,378 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,378 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,379 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,381 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,382 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,383 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,384 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,386 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,387 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,387 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,387 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,389 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,389 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,390 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,390 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,391 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,392 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,392 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,393 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,394 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,394 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,395 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,398 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,401 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,402 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,402 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,407 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,410 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,411 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,411 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,415 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,417 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,418 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,418 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,424 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,424 ERROR:searx.engines: Missing engine config attribute: "qwant.qwant_categ"
2022-10-21 22:02:53,426 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,426 ERROR:searx.engines: Missing engine config attribute: "qwant news.qwant_categ"
2022-10-21 22:02:53,427 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,427 ERROR:searx.engines: Missing engine config attribute: "qwant images.qwant_categ"
2022-10-21 22:02:53,428 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
2022-10-21 22:02:53,428 ERROR:searx.engines: Missing engine config attribute: "qwant videos.qwant_categ"
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 72 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 59 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 143 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 47 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 104 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 22 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 89 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 10 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 34 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 116 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 133 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x155493bcfb50 pid: 12 (default app)

 

Edited by plantsandbinary
Link to comment

So randomly this QWANT error has gone away, and now it's been replaced with an error regarding Soundcloud...

 

raise httpx.TimeoutException('Timeout', request=None) from e
httpx.TimeoutException: Timeout
2022-10-26 11:39:45,726 ERROR:searx.engines.soundcloud: Fail to initialize
Traceback (most recent call last):
  File "/usr/local/searxng/searx/network/__init__.py", line 96, in request
    return future.result(timeout)
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 448, in result
    raise TimeoutError()
concurrent.futures._base.TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/searxng/searx/search/processors/abstract.py", line 75, in initialize
    self.engine.init(get_engine_from_settings(self.engine_name))
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 69, in init
    guest_client_id = get_client_id()
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 57, in get_client_id
    response = http_get(app_js_url)
  File "/usr/local/searxng/searx/network/__init__.py", line 165, in get
    return request('get', url, **kwargs)
  File "/usr/local/searxng/searx/network/__init__.py", line 98, in request
    raise httpx.TimeoutException('Timeout', request=None) from e
httpx.TimeoutException: Timeout
2022-10-26 11:39:45,738 ERROR:searx.engines.soundcloud: Fail to initialize
Traceback (most recent call last):
  File "/usr/local/searxng/searx/network/__init__.py", line 96, in request
    return future.result(timeout)
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 448, in result
    raise TimeoutError()
concurrent.futures._base.TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/searxng/searx/search/processors/abstract.py", line 75, in initialize
    self.engine.init(get_engine_from_settings(self.engine_name))
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 69, in init
    guest_client_id = get_client_id()
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 45, in get_client_id
    response = http_get("https://soundcloud.com")
  File "/usr/local/searxng/searx/network/__init__.py", line 165, in get
    return request('get', url, **kwargs)
  File "/usr/local/searxng/searx/network/__init__.py", line 98, in request
    raise httpx.TimeoutException('Timeout', request=None) from e
httpx.TimeoutException: Timeout
2022-10-26 11:39:45,740 ERROR:searx.engines.soundcloud: Fail to initialize
Traceback (most recent call last):
  File "/usr/local/searxng/searx/network/__init__.py", line 96, in request
    return future.result(timeout)
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 448, in result
    raise TimeoutError()
concurrent.futures._base.TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/searxng/searx/search/processors/abstract.py", line 75, in initialize
    self.engine.init(get_engine_from_settings(self.engine_name))
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 69, in init
    guest_client_id = get_client_id()
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 57, in get_client_id
    response = http_get(app_js_url)
  File "/usr/local/searxng/searx/network/__init__.py", line 165, in get
    return request('get', url, **kwargs)
  File "/usr/local/searxng/searx/network/__init__.py", line 98, in request
    raise httpx.TimeoutException('Timeout', request=None) from e
httpx.TimeoutException: Timeout
2022-10-26 11:39:45,741 ERROR:searx.engines.soundcloud: Fail to initialize
Traceback (most recent call last):
  File "/usr/local/searxng/searx/network/__init__.py", line 96, in request
    return future.result(timeout)
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 448, in result
    raise TimeoutError()
concurrent.futures._base.TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/searxng/searx/search/processors/abstract.py", line 75, in initialize
    self.engine.init(get_engine_from_settings(self.engine_name))
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 69, in init
    guest_client_id = get_client_id()
  File "/usr/local/searxng/searx/engines/soundcloud.py", line 57, in get_client_id
    response = http_get(app_js_url)
  File "/usr/local/searxng/searx/network/__init__.py", line 165, in get
    return request('get', url, **kwargs)
  File "/usr/local/searxng/searx/network/__init__.py", line 98, in request
    raise httpx.TimeoutException('Timeout', request=None) from e
httpx.TimeoutException: Timeout

 

Link to comment
  • 2 weeks later...
  • 4 weeks later...

Sorry @hundsboog, I've stopped supporting the SearXNG container because there were too many changes for me to keep up with and I'm not longer using it on my UNRAID machine. 

 

Other than that, you can try deleting the container and rebuilding it with your same settings in order to decrease the amount of space it's taking up, but this is not a long term solution.

Edited by xthursdayx
  • Like 1
Link to comment
On 12/1/2022 at 8:44 PM, xthursdayx said:

Sorry @hundsboog, I've stopped supporting the SearXNG container because there were too many changes for me to keep up with and I'm not longer using it on  UNRAID machine. 

 

Other than can try deleting the container and rebuilding it with your same settings in order to decrease the amount of space it's taking up, but this is not a long term solution.

Thank you guys, I appreciate you help! Never mind, I just thought, maybe it is a known issue and there is a simple and short trick to fix it. I will try to sort it out and let you know if I have success! 

I wish you a nice and happy pre-Christmas time, stay all healthy and well!

 

 

- hundsboog

Link to comment
On 10/19/2022 at 12:34 PM, xthursdayx said:

Sorry for the delay. No, your .env file should just be in your appdata directory and the Extra Parameters section of the container template in Unraid should be used to point to this file, as it does in my template. If you turn on "Advanced View" when editing the template, you should see a section called "Extra Parameters". It should point to your .env file with a command like this "--env-file=/mnt/cache/appdata/standardnotes-web/.env". You do not need to copy the contents of the file into the Extra Parameters.

 

Outside of this, I'm not sure what is causing the problem. My container is running fine with these same settings.

 

For reference, the contents of my .env file are as follows:

RAILS_ENV=development
PORT=3001
WEB_CONCURRENCY=0
RAILS_LOG_TO_STDOUT=true
# Log Level options: "INFO" | "DEBUG" | "INFO" | "WARN" | "ERROR" | "FATAL"
RAILS_LOG_LEVEL=INFO
RAILS_SERVE_STATIC_FILES=true
SECRET_KEY_BASE=************************************************************
APP_HOST=https://notes.my.domain
PURCHASE_URL=https://standardnotes.com/purchase
PLANS_URL=https://standardnotes.com/plans
DASHBOARD_URL=http://standardnotes.com/dashboard

DEFAULT_SYNC_SERVER=https://sync.my.domain

# Development options
DEV_DEFAULT_SYNC_SERVER=https://api.standardnotes.com
ENABLE_UNFINISHED_FEATURES=false
DEV_WEBSOCKET_URL=wss://sockets-dev.standardnotes.com

# NewRelic (Optional)
NEW_RELIC_ENABLED=false
NEW_RELIC_THREAD_PROFILER_ENABLED=false
NEW_RELIC_LICENSE_KEY=
NEW_RELIC_APP_NAME=Web
NEW_RELIC_BROWSER_MONITORING_AUTO_INSTRUMENT=false

**Note - I also run Standard Notes standalone sync server locally, if you do not, then your DEFAULT_SYNC_SERVER should be the default Standard Notes Server.

How do you run the sync server? unraid?

Link to comment
  • 3 weeks later...

Hi,

 

i've installed YACReaderLibraryServer Docker successfully but i have an issue to see contents of my library.
I can connect to my library by WEB or by yacreader but when i click on the link (library's name), nothing happens...

On the application, folders remain empty...
I checked inside the container. i can browse every folder of my library (included files).

Anyway, i'm stuck.

Any suggestions please ?

Link to comment
  • 5 months later...

What is the status of the StandardNotes unRaid docker app? 

 

There are a couple forum entries related to Standard Notes but I don't see anything conclusive. I was hoping to be able to run StandardNotes on my unRaid server and use it as the sync server with standard notes on all my devices. 

 

Are there any detail instructions for installing the StandardNotes docker and getting this to work on unRaid?  For example I believe a different person mentioned needing to install a DB like MariaDB to get StandardNotes running as the server, but I don't see that mentioned on the StandardNotes app description.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.