Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Afshin Mortazavi-Nia
@amortaza
I try running para-cli new-app "myapp" --name "My App" and get the Connection failed. Run "para cli-setup" or check the configuration file... message.
So I fiddle around with the config.json file and append / to the endpoint (ie http://localhost:8080/).
Now when I run the new-app command, it tells me the app already exists. So I try the new-app again with an app name I have never used before random33 and it tells me the app already exists. What!??
Is the endpoint supposed to end with / ?
and if so, why does it tell me an app already exists whenever I try to create it?
Afshin Mortazavi-Nia
@amortaza
After restarting the para jar server, now I get Only root app can create and initialize other apps when I use an endpoint in the config.json file that doesn't end in /.
I hope that isn't too confusing.
I appreciate any help
Alex Bogdanovski
@albogdano
@amortaza I think the Para CLI fails to connect because your Para server is not allowing clients to connect to the root app. Can you check that you have para.clients_can_access_root_app = true?
Afshin Mortazavi-Nia
@amortaza

@albogdano Yes, that property is set to true

para.app_name = "Para"
para.env = "embedded"
para.security.allow_unverified_emails = true
para.clients_can_access_root_app = true
para.cache_enabled = true
para.app_secret_key = "b8db69a24a43f2ce134909f164a45263"
para.security.api_security = false
para.worker_id = 1

Here is the content of ~/.config/para-cli-nodejs/config.json
{
"accessKey": "app:para",
"secretKey": "mMEzD6pTGhqbt8n4n3UMTBl1dH9dWTsK6KDThiDFyeLJLzrnRKXCug==",
"endpoint": "http://localhost:8080",
"jwt": "eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE1OTUwNTA4OTUsImlhdCI6MTU5NDQ0NjA5NSwibmJmIjox>
}

Afshin Mortazavi-Nia
@amortaza

@albogdano

Here is the output of para jar on startup (notice it says 0 existing child apps)

2020-07-11 09:25:19 [INFO ] --- Para.initialize() [embedded] ---
2020-07-11 09:25:19 [INFO ] Loaded new DAO, Search and Cache implementations - H2DAO, LuceneSearch and CaffeineCache.
2020-07-11 09:25:19 [INFO ] Server is healthy.
2020-07-11 09:25:19 [INFO ] Found root app 'para' and 0 existing child app(s).
2020-07-11 09:25:19 [INFO ] Instance #1 initialized.
2020-07-11 09:25:20 [INFO ] Starting ParaServer on ace-ubuntu with PID 4805 (/home/ace/projects/java/para/para-jar-1.37.0.jar started by ace in /home/ace/projects/java/para)
2020-07-11 09:25:20 [INFO ] The following profiles are active: embedded
2020-07-11 09:25:20 [INFO ] Listening on port 8080...
2020-07-11 09:25:21 [INFO ] Started ParaServer in 1.443 seconds (JVM running for 3.222)

Alex Bogdanovski
@albogdano
@amortaza the issue here is caused by para.security.api_security = false. set this back to true while I fix this inconsistent behavior, when API security is disabled
Afshin Mortazavi-Nia
@amortaza
@albogdano Thank you, sir. Lesson learned - don't fudge with parameters you don't understand!
Aryan Khandal
@aryankhandal0
In self hosting para as your backend for scoold, does para have it's own database (if yes then how to access) or do we need to create a database like in MongoDB and connect them.
Alex Bogdanovski
@albogdano
@aryankhandal0 Para connects to a database of your choice. MongoDB is supported and you have to run and deploy MongoDB yourself then connect Para to it. By default Para stores data locally to H2 DB
Aryan Khandal
@aryankhandal0
While deploying para with mongodb, I am getting these errors, the collection is created in mongo db.

PS D:\Project-Scoold\project-so-mongo> docker run -ti -p 8880:8080 --rm -v para-data:/para/data -v "$(pwd)/application.conf:/para/application.conf" -e JAVA_OPTS="-Dconfig.f
ile=/para/application.conf -Dloader.path=lib" para-mongo

  ____  ___ _ ____ ___ _
 / __ \/ __` / ___/ __` /
/ /_/ / /_/ / /  / /_/ /

/ ._/\,// _,/ v1.37.1
/_/

2020-08-28 06:08:45 [INFO ] --- Para.initialize() [embedded] ---
2020-08-28 06:08:45 [INFO ] Loaded new DAO, Search and Cache implementations - MongoDBDAO, MockSearch and CaffeineCache.
2020-08-28 06:08:45 [INFO ] MongoDB host: host.docker.internal:27017, database: scoold
2020-08-28 06:08:45 [INFO ] Cluster created with settings {hosts=[host.docker.internal:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms',
maxWaitQueueSize=500}
2020-08-28 06:08:45 [INFO ] Cluster description not yet available. Waiting for 30000 ms before timing out
2020-08-28 06:08:45 [INFO ] Opened connection [connectionId{localValue:1, serverValue:20}] to host.docker.internal:27017
2020-08-28 06:08:45 [INFO ] Monitor thread successfully connected to server with description ServerDescription{address=host.docker.internal:27017, type=STANDALONE, state=CO
NNECTED, ok=true, version=ServerVersion{versionList=[4, 4, 0]}, minWireVersion=0, maxWireVersion=9, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTime
Nanos=3481794}
2020-08-28 06:08:45 [INFO ] Opened connection [connectionId{localValue:2, serverValue:21}] to host.docker.internal:27017
2020-08-28 06:08:45 [INFO ] Created MongoDB table 'para'.
2020-08-28 06:08:45 [WARN ] Server is unhealthy - root app not found. Open http://localhost:8080/v1/_setup in the browser to initialize Para.
2020-08-28 06:08:45 [INFO ] Instance #1 initialized.
2020-08-28 06:08:46 [INFO ] Starting ParaServer on f5678efc70ec with PID 1 (/para/para-1.37.1.jar started by para in /para)
2020-08-28 06:08:46 [INFO ] The following profiles are active: embedded
2020-08-28 06:08:46 [INFO ] Listening on port 8080...
2020-08-28 06:08:48 [INFO ] Started ParaServer in 2.503 seconds (JVM running for 4.87)
2020-08-28 06:09:41 [ERROR] API request error: Not implemented.
^C2020-08-28 06:21:10 [INFO ] --- Para.destroy() ---
2020-08-28 06:21:10 [INFO ] Closed connection [connectionId{localValue:2, serverValue:21}] to host.docker.internal:27017 because the pool has been closed.
PS D:\Project-Scoold\project-so-mongo> docker run -ti -p 8880:8080 --rm -v para-data:/para/data -v "$(pwd)/application.conf:/para/application.conf" -e JAVA_OPTS="-Dconfig.f
ile=/para/application.conf -Dloader.path=lib" para-mongo

  ____  ___ _ ____ ___ _
 / __ \/ __` / ___/ __` /
/ /_/ / /_/ / /  / /_/ /

/ ._/\,// _,/ v1.37.1
/_/

2020-08-28 06:21:14 [INFO ] --- Para.initialize() [embedded] ---
2020-08-28 06:21:14 [INFO ] Loaded new DAO, Search and Cache implementations - MongoDBDAO, MockSearch and CaffeineCache.
2020-08-28 06:21:14 [INFO ] MongoDB host: host.docker.internal:27017, database: scoold
2020-08-28 06:21:14 [INFO ] Cluster created with settings {hosts=[host.docker.internal:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=500}
2020-08-28 06:21:14 [INFO ] Cluster description not yet available. Waiting for 30000 ms before timing out
2020-08-28 06:21:14 [INFO ] Opened connection [connectionId{localValue:1, serverValue:22}] to host.docker.internal:27017
2020-08-28 06:21:14 [INFO ] Monitor thread successfully connected to server with description ServerDescription{address=host.docker.internal:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[4, 4, 0]}, minWireVersion=0, maxWireVersion=9, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=4191892}
2020-08-28 06:21:14 [INFO ] Opened connection [connectionId{localValue:2, serverValue:23}] to host.docker.internal:27017
2020-08-28 06:21:14 [ERROR] Failed to initialize Para.
java.lang.UnsupportedOperationException: Not implemented.
at com.erudika.para.search.MockSearch

Thank you for your help, I haven't seen such a helpful author
Alex Bogdanovski
@albogdano
@aryankhandal0 you shouldn't be using MockSearch - I don't know how this happened but your configuration is most likely wrong. By default Para uses LuceneSearch and you should have a ./data volume mounted in docker so that the search index is persisted to disk.
Suhail Ansari
@suhail-ansari
Hi! Are there any YouTube videos I can watch?
Alex Bogdanovski
@albogdano
@suhail-ansari not yet. what kind of videos are you looking for?
Aryan Khandal
@aryankhandal0
Which is the best config for production while deploying own para, NoSQL/SQL, LuceneSearch/ElasticSearch, CaffeineCache/HazelCast. Thank you!
Alex Bogdanovski
@albogdano
@aryankhandal0 I don't have an example to give you but I would suggest you include as little configuration as possible for your needs. It's best that you don't modify security defaults like para.security.api_security, para.security.allow_unverified_emails and para.clients_can_access_root_app
ak1542
@ak1542
Hy.. I'm new to scoold and para can someone help to understand it what it is how I can build Q&A website with it
Alex Bogdanovski
@albogdano
@ak1542 Please start by going through the Scoold README
ak1542
@ak1542
Is there any video lecture to follow
?
Alex Bogdanovski
@albogdano
no, not yet