Erudika/para

The back-end framework for busy developers.

Alex Bogdanovski

@albogdano

@sujai1009 try mvn spring-boot:run -Dconfig.file=./application.conf

sujai1009

@sujai1009

thank you @albogdano still the same.

for test purpose i changed para.env = "2" in my custom file. but para server starts in Para.initialize() [production]

Alex Bogdanovski

@albogdano

well, try para.env = "embedded" instead of 2

sujai1009

@sujai1009

ok sure. Still the same

Alex Bogdanovski

@albogdano

mvn spring-boot:run -Dspring-boot.run.jvmArguments="-Dconfig.file=./application.conf"

sujai1009

@sujai1009

bingo. it worked . Thank you so much @albogdano

Alex Bogdanovski

@albogdano

:thumbsup:

sujai1009

@sujai1009

i was struggling with this for past 2 hours

Alex Bogdanovski

@albogdano

@sujai1009 https://stackoverflow.com/questions/34297666/pass-system-property-to-spring-boot

sujai1009

@sujai1009

Thanks again @albogdano

prog20901

@prog20901

How to generate java doc as PDF file ? Open source software and tools ???

Alex Bogdanovski

@albogdano

@prog20901 https://stackoverflow.com/questions/2322048/how-to-generate-a-pdf-from-javadoc-including-overview-and-package-summaries

Danilo Souza

@danxsouza_twitter

Hi Alex
Can you help me, I can't figure out the reason for this error?

[ERROR] 400 - User belongs to an app that does not exist.

Alex Bogdanovski

@albogdano

@danxsouza_twitter did you initialize Para with GET /v1/_setup

1 reply

Alex Bogdanovski

@albogdano

@danxsouza_twitter Are you sure you created the new app kaffa or you just used the secret key of the root app app:para and changed its name to app:kaffa? Also remove the app_secret_key value fro your Para configuration. That should be a random secret not equal to the secret for app:kaffa.

1 reply

Also check if data is actually saved to disk. What happens if you open GET /v1/_setup again? does it say "all set!"?

Alex Horn

@HorncaAlex_twitter

Hi Alex

Alex Horn

@HorncaAlex_twitter

Thanks for posting "Building a full stack application from scratch with Angular" on your blog. While following your directions I have successfully built the application using Para as the back-end. The issue I'm running into is that although both the para console and angular say my application is running the browser isn't rendering the site. All I'm seeing is;

{
"totalHits" : 0,
"page" : 0,
"items" : [ ]
}

Alex Bogdanovski

@albogdano

@HorncaAlex_twitter I can't really tell what the actual problem is in your case. Check your Angular controller code and the model data in particular

Afshin Mortazavi-Nia

@amortaza

Hi. Just installed para and following the "Quick Start" steps. But I am seeing some unexpected behavior.

I am on Ubuntu 20.04, I ran curl localhost:8080/v1/_setup

The para jar is running so everything is good so far.

I ran para-cli setup and entered the access key and secret key and http://localhost:8080 is set as the endpoint.

The output of para-cli setup is that New JWT generated... however Connection failed. Run "para cli-setup" or check the configuration file...

I check the configuration file and everything looks good.

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

Where communities thrive

People

Repo info

Activity